TU München - Fakultät für
Chair IV: Software & Systems Engineering
Variability Models Must Not be Invariant!
|Author:||Elmar Juergens, Markus Pizka|
|Conference:||VaMoS '07: Proc. of the 1st Intl. Workshop on Variability Modelling of Software-intensive Systems|
|Abstract:||Variability modeling techniques are used to specify variable
aspects of members of a family of related software artifacts.
Instances of variability models are then used to efficiently
produce members of such a family. By making variability
explicit, variability models determine implicitly the
common properties among family members as well.
This partitioning of information into variable and invariant
parts predetermines the reuse benefit obtainable from a
variability model. In most current approaches to variability
modeling, the decision between variable and invariant information
has to be done in an up-front manner and is very
difficult to change later on. However, the distinction between
variable and common parts of members of a system
family varies over time. Variability modeling techniques
must thus be able to cope with changes to the variability
Since many variability modeling techniques do not currently
support this, research is required to allow an evolution
of the distinction between what is variable and what is
invariant over time. This paper elaborates on the necessity,
related work and possible approaches to tackle this challenge.