Tools Support - Model-Driven and Software Product Line Engineering - page 175

Metaconcept Feature Cardinality Description

[0..1] Components classified as

Periodic can be
either Service or
Periodic Components
in the final software
architecture

Periodic Component Type

[1..2]

Components can be
instantiated either
On Deployment or
On Invocation

Component Instantiation Mode

Table 6.6. (continued) Constraints between the components'
metamodel and the architecture feature model

6.4.4. Domain models and binding models creation

The fine-grained approach of FieSta requires the definition
of several domain models and binding models to link the
former with feature models describing variations. This section
presents the process of creating domain and binding models
and applies it to the Smart-Home case study.

6.4.4.1. Domain models creation
We built an Eclipse plug-in to create domain models using
the facility provided by Eclipse to generate model editors
from Ecore models. We named this plug-in the Smart-Homes
Domain Models Creator . Product line architects have to create
new domain metamodels and new domain model editors for
producing new MD-SPLs.

Figure 6.9 presents a domain model created with our
Smart-Homes Domain Models Creator. The model created by
a building architect defines firstFloor and secondFloor .
In the firstFloor there are two rooms, livingRoom ,
and kitchen . In the secondFloor , there is another
room, mainRoom , which has two windows, mainRoomW1 and
mainRoomW2 . There are also two doors. The first door,
livingRoomD1 , isinthe livingRoom . The second door,
mainRoomD2 , isinthe mainRoom .