Model-Driven and Software Product Line Engineering - Model-Driven and Software Product Line Engineering - page 128

transformation rule must be executed;if the feature Periodic
is selected the second transformation rule must be executed.
Similarly, we create two different specific transformation
rules to transform Domain metamodel::Door elements. The
first one creates FacilitiesMetamodel::Door elements;
each one containing a Domain metamodel::Fingerprint
element; the second one creates Facilities
Metamodel::Door elements; each one containing a Domain
metamodel::Keypad element.
Fourth stage: Model-to-text transformation rules. The model-
to-text transformation rules produce the source code of product
line members. These transformation rules have as input an
architecture model and a facilities model. On the one hand,
the architecture model is transformed into the source code
of OSGi components (Bundles) as presented in Figure 4.15.
For this transformation, it is also possible to re-use pieces
of code previously written by product line architects. Thus,
the transformation rules are only in charge of connecting the
already created pieces of code representing components.
On the other hand, the facilities model is transformed into
an extra OSGi component, HouseStructure , which manages
the structural design of the configured Smart-Home. Thus,
if the Smart-Home has been configured to have one floor
and two rooms, the HouseStructure component maintains this
structure to provide the required services to the configured
structural element. These model-to-text transformation rules
are available along with the model-to-model transformation
rules on the Website [ARB 12].
Figure4.16presentsanexampleoftheGUIcorrespondingto
one configured Smart-Home System. The Smart-Home system
wasconfiguredtohaveonefloorwithoneroom,the Main Room .
This room has Automatic Windows as Environmental
Control . The only door in the Main Room has Fingerprint
as Door Lock Control .