Managing variability in software architectures

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.

REFERENCES

• 1: Jan Bosch, Design & Use of Software Architectures, Addison Wesley, 2000.
• 2: Paul Clements and Linda Northrop, A Framework for Software Product Line Practice - Version 3.0. http://www.sei.cmu.edu/plp/framework.html.
• 3: Michael Coriat, Jean Jourdan, Fabien Boisbourdin, The SPLIT Method, Software Product Lines, Kluwer Academic Publishers, August 2000 147-166.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

General Terms:
Design, Documentation, Performance, Theory

Keywords:
product lines, requirement analysis, software architecture, strategic reuse, variability, variation points