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

stages. The first set of rules is defined from the problem space
metamodeltothe Kernel metamodel.Thesecondsetisdefined
from the problem space metamodel to the GUI metamodel.
These are created taking into account our constraint model.
The third set of transformation rules includes model-to-text
transformations,which produce the source code of product line
members.
First Stage: Problem space-to-kernel transformation
rules. The purpose of these transformation rules is
adding information about collection manager facilities to
problem space models. These are horizontal model-to-model
transformations. It means they transform models inside the
same abstraction level, the application domain abstraction
level, but add concerns related to collection manager facilities.
We created two sets of transformation rules: the base
and the specific ones. For instance, we create a base
transformation rule to transform ProblemSpace::Entity
elements into Kernel::Element elements. Similarly,
we created a base transformation rule to transform
ProblemSpace::Characteristic elements into
Kernel::Attribute elements. We created specific
transformation rules taking into account the possible bindings
that can affect the transformation process. For instance,
we created two specific transformation rules to transform
ProblemSpace::Characteristic elements; the first one,
taking into account the constraint1 (see Figure 7.8), creates
Kernel::Filter elements for each Characteristic bound
to the FilteringData feature in the binding model; the
second one, taking into account the constraint3 , creates
Kernel::Sort elements for each Characteristic bound to
one of the Sort Algorithm (grouped) features in the binding
model.
Second Stage: Problem space-to-GUI transformation rules.
The second set of transformation rules is defined from the
problem space metamodel to the GUI metamodel. These are