Implementing Product Line Variabilities

Implementing Product Line Variabilities - Term paper...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Implementing Product Line Variabilities Michalis Anastasopoulos Fraunhofer Institute for Experimental Software Engineering Sauerwiesen 6 D-67661 Kaiserslautern, Germany +49 (0) 6301 707 168 [email protected] ABSTRACT Software product lines have numerous members. Thus, a product line infrastructure must cover various systems. This is the significant difference to usual software systems and the reason for additional requirements on the various assets present during software product line engineering. It is imperative that they support the description of the product line as a whole, as well as its instantiation for the derivation of individual products. Literature has already addressed how to create and instantiate generic product line assets, such as domain models and architectures to generate instance specific ones [1, 2, 3], yet little attention has been given on how to actually deal with this genericity at the code level. This paper addresses the issue of handling product line variability at the code level. To this end various implementation approaches are examined with respect to their use in a product line context. Keywords Software product lines, product line variability, implementation approaches, implementing variabilities, traceability 1. INTRODUCTION Software product lines have numerous members. Thus, a product line infrastructure must cover various systems. This is the significant difference to usual software systems and the reason for additional requirements on the various assets present during software product line engineering. It is imperative that they support the description of the product line as a whole, as well as its instantiation for the derivation of individual products. To reflect a product line, the generic assets have to cover all elements the product family is built from, and their corresponding composition rules. Clarifying how the various parts may be combined is a very challenging task. Generic assets differ from specific ones in the fact that they embrace common and variable product aspects. Generic assets can be instantiated, that is, product-specific assets can be derived from them. Specific assets on the other hand are uniquely mapped to product line members. Products within a product line context consist of constant as well as variable elements. Dependencies between these elements do exist (e.g., elements may exclude each other or one element may make the integration of a second one a necessity). Hence only a subset of all combinations are correct and complete configurations. Therefore we have to restrict the product line infrastructure to cover only the set of valid family members. A decision model structures the variability within a product line as a set of decisions to be resolved. Interrelations between decisions are captured as well. Such a model is also generic, that is, it can be also instantiated. In the instance all decisions are resolved. Every diversity in each generic asset must be connected to an open decision in the decision model. The presence of a decision model is
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 9

Implementing Product Line Variabilities - Term paper...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online