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

compilation or runtime execution. MAPLE does not require
such an advanced programming language and relies only
on traditional programming language. Variability is often
managed by successive model transformations before source
code generation. We have to mention that the approach we
present in this topic was developed also in the context of the
AMPLE project.
8.7. Feature modeling notations
Feature modeling is a method and notation for capturing
commonalities and variabilities in product lines [KAN 90,
KAN 98, RIE 02, CZA 05, VÖL 07b]. Features describe the
common and variable functionality of a system under
development. Feature modeling was first introduced by Kang
et al . as FODA [KAN 90]. FODA is described as a domain
analysis method for identifying prominent and distinctive
features of a set of systems in a specific domain. In FODA,
the features are used to define a specific domain in terms of its
mandatory , optional ,or alternative characteristics. After Kang
et al ., other authors extended the concepts regarding feature
modeling. Among these extensions are the concepts of feature
cardinality [CZA 00], groups and group cardinality [RIE 02],
andattributesforfeatures[CZA02]amongothers.Thepurpose
of these extensions is to restrict the set of variants that
can be selected from feature models to create particular
configurations.Oneofthemostcitedworksonfeaturemodeling
is presented by Czarnecki et al . [CZA 04], where the authors
propose a cardinality-based notation for feature modeling
including solitary , group , and grouped features. This approach
integratesanumberofexistingextensions;thuswesuggestthe
use of this notation.
8.8. Decision models
Decision models were introduced to capture variability and
to help in deriving products [ATK 00, BAY 00]. Product line