Information Technology Reference
In-Depth Information
iterative refinement, and the integration of models. We
define an MD-SPL as a set of products developed from
application domain models,and derived from a set of re-usable
model transformation rules. There is a general agreement
on the fact that model transformations may require several
stages, e.g. [VÖL 07b, ARB 09b, ARB 09a]. At each stage,
application domain models are automatically transformed
to include more implementation details. Models with only
problem space concerns are incrementally transformed to
include the solution space, i.e. concerns of software design
and/or technological platforms, as well as performance issues.
At the end of a staged model transformation process, models
including all the implementation details are transformed into
source code of software systems.
Most of the current MD-SPL approaches [VÖL 07b,WAG 05,
LOU 08, SAN 08] create application domain metamodels
and variability models to capture and express variability
separately . For configuring a particular product, the product
designers create configurations that consist of (1) application
domain models and (2) instances of variability models.
An instance of a variability model includes a selection of
variants from the variability model. The MD-SPL approaches
using multi-staged model transformations also facilitate
the configuration of products by creating specific instances
of variability models. For example, product designers can
select software architectural details before executing model
transformations in charge of adding architectural information.
Therefore, the staged transformation of an application
domain model may derive products with different software
architectures or products to run on different technological
platforms.
During the product derivation process, the instances of
variability models are used to decide what transformation
rules must apply. Thus, from different instances of variability
Search WWH ::




Custom Search