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

case study. The example includes a binding model between a
component model and the architecture feature model.
Figure 5.1. Binding model example
5.2.2. Constraint models
Product line architects must use constraint models to
restrict the bindings between model elements and features;for
example, to express that only domain models can be bound to
facilities models,or that maximum three Room elements can be
bound to the feature Air Conditioning .
A constraint model is a set of constraints .
D EFINITION 5.2.- A constraint is a quadruple C =[M,F,A, D]
composed of a metaconcept M , a feature F , and two properties:
A and D . A constraint C expresses the fact that model elements
that conform to the metaconcept M can be bound to the
feature F .
The properties A and D are described in sections 5.2.3
and 5.2.4. Each constraint is unique in a constraint model;
this means, only one constraint includes a pair [M, F] .
Our constraints serve to avoid inconsistencies during the
configuration and derivation processes. Constraints must
prevent the following problems:
- Any model is bound to any feature model. For example, in
ourcasestudy,onlydomainmodelscanbeboundtothefacilities