Model-Driven and Software Product Line Engineering - Model-Driven and Software Product Line Engineering - page 118

givingitsdomainmodelandselectingvariantsfromthesources
of variability. For instance, in our application example, those
are the variants from Smart-Home's facilities and software
architecture. In [POH 05] the authors introduce the idea of an
orthogonal variability model dedicated to collecting variability
in the entire product line,not only at the level of requirements.
This role features models,which address specific aspects of the
variability: Smart-Home and building architecture facilities,
software architectural considerations,implementation choices,
and so on.
Figure 4.9 presents an example of how limited the
configuration and the derivation of Smart-Home systems is
when only product designers configure a product by means
of a specific domain model. In the example, from a building
representingthearchitecturalstructureofaSmart-Home,only
one possible Smart-Home system could be derived, without
including variants from concerns different from the structure
of the building.
Figure 4.9. Example of configuration without variability models
We use feature modeling to allow product designers to
configure products from sources other than the application
domain. Like metamodeling, feature modeling can be used for
capturing not only structural, but also behavioral variations.
Metamodeling facilitates the configuration of products by
creating rich models using a constructive approach that
requires a high level of expertise. Feature modeling facilitates