Abstract
This paper presents experience with explicitly managing variability within a software architecture. Software architects normally plan for change and put mechanisms in the architecture to support those changes. Understanding the situations where change has been planned for and recording the options possible within particular situations is usually not done explicitly. This becomes important if the architecture is used for many product versions over a long period or in a product line context where the architecture is used to build a variety of different products. That is, it is important to explicitly represent variation and indicate within the architecture locations for which change has been allowed.
We will describe how the management of variations in an architecture can be made more explicit and how the use of variation points connected to the choices a customer has when ordering a product can help to navigate to the appropriate places in the architecture.
- 1 Jan Bosch, Design & Use of Software Architectures, Addison Wesley, 2000.Google Scholar
- 2 Paul Clements and Linda Northrop, A Framework for Software Product Line Practice - Version 3.0. http://www.sei.cmu.edu/plp/framework.html.Google Scholar
- 3 Michael Coriat, Jean Jourdan, Fabien Boisbourdin, The SPLIT Method, Software Product Lines, Kluwer Academic Publishers, August 2000 147-166.Google Scholar
Index Terms
- Managing variability in software architectures
Recommendations
Managing variability in software architectures
SSR '01: Proceedings of the 2001 symposium on Software reusability: putting software reuse in contextThis paper presents experience with explicitly managing variability within a software architecture. Software architects normally plan for change and put mechanisms in the architecture to support those changes. Understanding the situations where change ...
The notion of variability in software architecture: results from a preliminary exploratory study
VaMoS '11: Proceedings of the 5th International Workshop on Variability Modeling of Software-Intensive SystemsContext: In the software product line domain, the concept of variability is well recognized. However, variability in the context of software architecture still seems to be poorly understood. Objective: In this paper, we aim at contributing to the ...
Workshop on Variability in Software Product Line Architectures (VARI-ARCH 2010)
ECSA '10: Proceedings of the Fourth European Conference on Software Architecture: Companion VolumeThe objective of this workshop is to bring together researchers from the software product line community and software architecture community to identify critical challenges and progress the state-of-the-art on variability in software product line ...
Comments