Tools Support - Model-Driven and Software Product Line Engineering - page 185

binding model between the architecture metamodel and the
component model derived from the domain model.
In section 4.6, we introduced part of the decision model we
created for deriving configured Smart-Home systems. Similar
to Figure 5.5, we defined an Aspect element related to each
constraint in the two constraint models. As a result, we can
guarantee that any binding satisfying a constraint will be
taken into account during the derivation process. The model
element involved in the binding will be transformed using
a specific transformation rule in charge of transforming it
according to the feature involved in the binding.
For instance, Figure 6.16 presents another part of the
decisionmodelforderivingconfiguredSmart-Homesystems.In
this case, we present the Aspect we created for the constraint
between the Door metaconcept and the Fingerprint feature.
This Aspect specifies that any Door element in a binding
model will be transformed using the specific transformation
rule doorToDoorWithFingerprint . As a result, we can
guarantee that any binding satisfying the constraint between
the Door metaconcept and the Fingerprint feature will be
taken into account to derive a Smart-Home system. The doors
involved in the bindings will have fingerprint as lock door
control mechanism.
6.5.3. Generation and execution of model transformation
workflows
AsweexplainedinChapter5,toexecuteourdecisionmodels,
we need to transform them into executable oAW workflows by
using a model-to-text transformation. This transformation is
achieved using a model-to-text transformation,which is part of
the Website [ARB]. As a result, we can execute the generated
model transformation workflows on the model transformation
engine of oAW. Thus, we derive any (fine-grained) configured
product.