Software Product Line Engineering Basics - Model-Driven and Software Product Line Engineering - page 46

that gap. A decision model is defined as a model that captures
variability in a product line in terms of open decisions and
possible resolutions [BAY 00].
D EFINITION 2.11.- A decision model is an artifact capturing
product line variability and making the resolution of this
variability effective during product derivation.
Each decision is expressed in terms of a selected variation
point and associated with a set of possible resolutions, which
in turn, refer to variants of selected variation points. A set of
effects is associated with each possible resolution. An effect
indicates how a particular core asset is re-used to create a
product line member.
D EFINITION 2.12.- A resolution model is a decision model
instance, which binds variability and defines how to derive one
product.
In resolution models, all decisions must be resolved. As
resolutions are related to variants and effects on particular
core assets, a resolution model defines a product line member
including (1) a subset of variants, (2) the core assets required
to derive the required product, and (3) the adaptation that
must be performed on the core assets to obtain a product line
member.
Table 2.1 presents a decision model example to create
an SPL, which includes variants of the security profile
from Figure 2.6.This decision model includes only one decision
expressed in terms of the variation point Expiration date,
which has been created as a FeatureGroup . This decision is
associated with two possible resolutions,which in turn,refer to
variants from the Expiration date variation point, inDays
and Never . One effect is associated with each resolution.
Each effect indicates the software components that must
be deployed in case a particular resolution is selected. Thus
for instance, if a resolution model is created including the