Although evolution is a critical aspect of software product line engineering, the body of knowledge surrounding it is still inadequate. The contribution of this paper is to show how the practice of feature separation practice addresses the evolution challenges, specifically in a telecommunications software product line case study. The main idea behind feature separation is to achieve a one-to-one relationship between features in the feature model to feature realizations in code, which keeps feature realizations separate in the code. This not only prevents the software product line architecture from deteriorating, but in fact improves it. To apply this in an industrial context, it is necessary to also take into account schedule pressures and legacy artifacts. Application into the telecommunications software product line case study shows significant productivity and architecture improvements.
[1]
Mika Pussinen.
A survey on software product-line evolution
,
2002
.
[2]
Wolfgang Schröder-Preikschat,et al.
Variability in Time - Product Line Variability and Evolution Revisited
,
2010,
VaMoS.
[3]
Lianping Chen,et al.
Variability management in software product lines: a systematic review
,
2009,
SPLC.
[4]
Stefan Kowalewski,et al.
EvoFM: feature-driven planning of product-line evolution
,
2010,
PLEASE '10.
[5]
Klaus Pohl,et al.
Software Product Line Engineering
,
2005
.
[6]
Jan Bosch,et al.
Maturity and Evolution in Software Product Lines: Approaches, Artefacts and Organization
,
2002,
SPLC.