Further Reading - Model-Driven and Software Product Line Engineering - page 216

model transformation languages, which provide a mechanism
based on AOP for the composition of transformation rules
(see section 3.6.4). Decision models are the base of our
mechanism to derive products including variability. They
capture the execution ordering of transformation rules to
be performed by the model transformation engine to derive
configured products. We use aspect-oriented programming,
provided by oAW,to build the scheduling of the transformation
rules, i.e. the ordering in which transformation rules are
going to process model elements to accomplish the desired
derivation.
8.9. Model-driven software product lines
MD-SPL are product lines created based on MDE
principles (see Chapter 4). A product line member of an
MD-SPL is created from an application domain model that
(1) conforms to an application domain metamodel and (2) is
transformed until obtaining the application by using model-
to-model and model-to-text transformations. There is no
reference framework for creating MD-SPLs. For many in this
domain (e.g. [VÖL 07b]), including us [ARB 09a, ARB 09b],
these model transformations may require several stages
and may include horizontal and vertical transformations. At
each transformation stage, application domain models are
automatically transformed to include new concerns from a
particular abstraction level or more implementation details
from lower abstraction levels.
Several approaches to create SPLs have emerged that
are based on MDE. In this section, we discuss four of
the most representative works presented in the area. These
approachesareCzarneckiandAntkiewicz'sapproach[CZA05],
Wagelaar's approach [WAG 05,WAG 08a,WAG 08b],Loughran
et al .'s approach [LOU 08, SAN 08], and Voelter and
Groher's approach [VÖL 07b]. We have chosen to present
each work following two aspects, see Figure 8.1. The first