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

- Software architecture metamodel. Each Smart-Home
system has a technology platform integrating their devices
under different software architectures.
It is possible to create other metamodels such as a
programming language grammar, or its representation as a
metamodel, to capture the final source code of the product
line members. In our case study, however, we do not create
it; instead, we generate the final representation of a product
directly as source code.
Thefirststagetoconfigureaproductstartswiththecreation
of a domain model; i.e. the model that represents a particular
building. Figure 4.3 presents the transformation steps of a
domain model from its creation until the production of the
source code application. The model transformation rules are
used in four stages, each one with a dedicated set of rules.
The first set of rules is defined from the domain metamodel
to the facilities metamodel. The second set is defined from
the facilities metamodel to the components metamodel.
The third set is defined from the components metamodel
to the architecture metamodel. Finally, the fourth set of
transformation rules includes model-to-text transformations
thatproducethesourcecodeofproductlinemembers.Wecreate
model-to-text transformation rules from the facilities and the
architecture metamodel to Java source code. The following
sections present the details about the model transformations
and the possible variations these model transformations can
have according to the SPL variability.
We present our four metamodels in detail:
Domain metamodel. The first metamodel is the domain
metamodel, which includes application domain concepts that
facilitate the creation of models representing the structure of
houses. Figure 4.4 presents the domain metamodel. Using this
metamodel we can create houses with several architectural