A Second Comprehensive Application Example - Model-Driven and Software Product Line Engineering - page 207

baseline scheduling taking into account not only features
from feature configurations, but also bindings from binding
models.
Thus, for instance, if any Characteristic element is
bound to the feature FilteringData in a binding model,
the base sequence to transform problem space models into
kernel models must be modified. This modification implies
the replacement of the rule characteristicToAttribute
by the rule charactericticToFilterAttribute . This rule
must transform only the ProblemSpace::Characteristic
elements that are bound to the FilteringData feature, into
Kernel:Filter elements. For instance, from the binding
model presented in Figure 7.8, given that the code element
in the problem space model is the only characteristic bound
to the FilteringData feature, this is the only characteristic
that must be transformed into a Filter element in the kernel
model.
Figure 7.11 presents a small part of our decision model to
transform problem space models into kernel models taking
into account binding models. We can see in the figure that we
first define a baseline scheduling,which includes the execution
of the transformation rules problemSpaceToSystem ,
entityToElement , and characteristicToAttribute .
Then, we create an aspect indicating that if some bindings
satisfy constraint1 (which describes that product designers
can bind Characteristic elements with the feature
FilteringData ) the execution of the base transformation
rule characteristicToEntity must be intercepted.
After the interception is done, the specific transformation
rule charactericticToFilterAttribute must be then
executed. This rule queries the binding model used to
configure the product, which is derived, and transforms only
the Characteristic elements bound to the FilteringData
feature.