Further Reading - Model-Driven and Software Product Line Engineering - page 218

8.9.1. The Czarnecki and Antkiewicz's approach
8.9.1.1. Problem space: expressing variability and configuring
products
To express variability, Czarnecki and Antkiewicz [CZA 05]
propose an approach where variation points and variants are
captured by means of feature models. They extend the FODA
approach by adding cardinality and attributes for features.
Products are configured by creating feature configurations.
8.9.1.2. Solution space: core assets development and products
derivation
The main core assets built by product line architects to
derive products in Czarnecki and Antkiewicz's approach are
template models and model transformations.
TemplatemodelsareexpressedusingUMLandrepresentall
the possible elements required to create product line members.
For example, to represent a family of UML 2.0 activity models,
both the model template and the template instances are
expressed using the UML 2.0 activity modeling notation. A
template model is a superimposition of all the possible model
elements required to derive diverse products according to
feature configurations.
Template models are annotated by product line architects
using presence conditions and meta-expressions . The
annotations are defined in terms of features from a feature
model, which capture the variability of the product line
under development. Presence conditions indicate whether
an element should remain in or be removed from a template
instance because of the presence of a particular feature in
feature configurations. Meta-expressions indicate how to
compute attributes of model elements, such as the name of an
element or the return type of an operation, based on values
assigned to feature attributes in feature configurations.