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

- GUI Metamodel. This metamodel includes only concepts
concerning the user interface. This metamodel represents the
domain concept and its characteristics in terms of graphical
elements.
In the same way as the Smart-Home example, it is
also possible to create other metamodels to represent other
viewpoints involved in the development of product line
members. In this case study, however, we limit the viewpoint
division to the metamodels we described before in order to have
a comprehensive example.
Figure 7.3 presents the transformation steps processed on
a model conforming to the problem space metamodel from its
creation until the production of the source code application.
The model transformation rules are used in three stages, each
one with a dedicated set of rules. The first set of rules is
defined from the problem space metamodel to the Kernel
metamodel. The second set is defined from the problem space
metamodel to the GUI metamodel. Finally, the third set of
transformation rules includes model-to-text transformations,
which produce the source code of product line members. We
create model-to-text transformation rules from the Kernel
and the GUI metamodels to Java source code. The following
sections present details about the model transformations, and
the possible variations these model transformations can have
according to the SPL variability.
Problem Space Metamodel. The first metamodel is the
Problem Space metamodel, which includes the domain
concept and their characteristics. Figure 7.4 presents this
metamodel (left) and an example of a domain model
(right).The model defines a student element,which conforms
to Concept . Every student is characterized by their
characteristics: code , name , address and e-mail , which
conforms to Characteristic .