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

one FacilitiesMetamodel::WindowsController element
in the source model.
- The rule to create the AirConditioningController
component, its ports, and interfaces, is only executed
if there exists at least one Facilities Metamodel::
AirConditioning element in the source model.
The GUI component corresponds to the graphical
user interface (GUI) of the Smart-Home systems. This
component requires services of all the other components. In
Figure 4.15, we only include one of its Required interfaces,
IDoorController .
Third stage: Components-to-architecture transformation
rules. The purpose of these transformation rules is the adding
to component models information about the type of the
components, periodic or service , and their instantiation mode,
on invocation or on deployment . These are horizontal model-
to-model transformations given that models are transformed
inside the same abstraction level.
In this stage, we create base and specific transformation
rules. For instance, we create a base transformation rule to
transform ComponentMetamodel::Interface elementsinto
ArchitectureMetamodel::Interface elements.
We create specific transformation rules taking into account
the possible features that can affect the transformation
process. In this case, those are features from the architecture
featuremodel.Forinstance,wecreatetwotransformationrules
to transform ComponentMetamodel::Component elements.
The first one, taking into account the Service feature, creates
ArchitectureMetamodel::Service (Component)elements.
The second one, taking into account the Periodic feature,
creates ArchitectureMetamodel::Periodic (Component)
elements from ComponentMetamodel::Periodic elements.
Therefore, if the feature Service is selected, the first