The FieSta Framework: Fine-grained Derivation and Configuration - Model-Driven and Software Product Line Engineering - page 141

feature models and only components models can be bound to
the architecture feature models.
- Model elements that conform to any metaconcept are
bound to any feature. For example, for a requirement of
the product line (R1) specifying that only windows can be
automatic, a constraint must exclude Door elements from the
Automatic Windows feature.
- Any number of model elements that conform to a
metaconcept is bound to any number of features. For example,
since the installation of automatic windows could be expensive
in a product line for economical Smart-Homes, a product line
architect may deal with a requirement (R2) that specifies
that only (maximum) one window can be automatic. Thus, a
constraint must prevent more than one Window element from
being bound to the Automatic Windows feature.
- Model elements and features are bound without taking
into account constraints between functional requirements.
For example, for a requirement of the product line (R3) ,
which specifies that automatic windows must have sensors,
a constraint must prevent Window elements without an
associated Sensor element from being configured as
Automatic Windows .
- Model elements and features are bound without taking
into account the prerequisites of the configuration. For
example, a requirement of the product line (R4) specifies that
automatic windows can only be selected from rooms, which
are not configured to have air conditioning. A constraint must
prevent Window elements with their rooms associated to the
Air Conditioning feature being configured as Automatic
Windows .
Therefore, for our case study, with respect to the
requirement (R1) , a product line architect could define
a constraint between the Window metaconcept and
the Automatic Windows feature, constraint1 =[ Window ,
Automatic Windows ,A,D] . The constraint describes that