Projects per year
Feature diagrams are a popular means for documenting variability in software product line engineering. When examining feature diagrams in the literature and from industry, we observed that the same modeling concepts are used for documenting two different kinds of variability: (1) product line variability, which reflects decisions of product management on how the systems that belong to the product line should vary, and (2) software variability, which reflects the ability of the reusable product line artifacts to be customized or configured. To disambiguate the documentation of variability, we follow previous suggestions to relate orthogonal variability models (OVMs) to feature diagrams. This paper reuses an existing formalization of feature diagrams, but introduces a formalization of OVMs. Then, the relationships between the two kinds of models are formalized as well. Besides a precise definition of the languages and the links, the important benefit of this formalization is that it serves as a foundation for a tool supporting automated reasoning on variability. This tool can, e.g., analyse whether the product line artifacts are flexible enough to build all the systems that should belong to the product line.
|Title of host publication||Proceedings of 15th IEEE International Requirements Engineering Conference (RE'07)|
|Editors||Alistair Sutcliffe, Pankaj Jalote|
|Publisher||IEEE Computer Society Press|
|Publication status||Published - 2007|