Proceedings of the 1st International Workshop on Variability and Complexity in Software Design 2016
DOI: 10.1145/2897045.2897048
|View full text |Cite
|
Sign up to set email alerts
|

Variability mechanisms and lessons learned in practice

Abstract: In the design of complex and variable software systems, one of the key steps is to select the variability mechanism that defines how variable features are realized on the design and code level. Although different variability mechanisms were invented and applied in practice for decades, there are not many studies that compare these mechanisms based on practical experiences. This paper characterizes and compares seven variability mechanisms in terms of their techniques, binding time, granularity, and further asp… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 16 publications
(3 citation statements)
references
References 42 publications
0
3
0
Order By: Relevance
“…However, in our research work, we propose an approach that identifies not only the similarities, but also the differences among customized cloned variants. Seven variability mechanisms are characterized and compared in [13]. As a variability mechanism, authors in [14] present a novel feature-oriented programming approach to migrate multiple cloned variants into an SPL.…”
Section: State Of the Artementioning
confidence: 99%
See 1 more Smart Citation
“…However, in our research work, we propose an approach that identifies not only the similarities, but also the differences among customized cloned variants. Seven variability mechanisms are characterized and compared in [13]. As a variability mechanism, authors in [14] present a novel feature-oriented programming approach to migrate multiple cloned variants into an SPL.…”
Section: State Of the Artementioning
confidence: 99%
“…A novel approach named SPLEVO for supporting the consolidation of customized product copies into a Software Product Line is presented in [6]. Several researchers tackle the problem of extracting FMs or variability of existing customized variants [7,12,13,[15][16][17][18]. Several kinds of artifacts can be considered, including variants descriptions [9,10,[19][20][21], models [22,23], and code bases [8,[24][25][26] or the combination of them.…”
Section: State Of the Artementioning
confidence: 99%
“…To make this possible in an ordered way, each module presented in the Section III-A was implemented as a distinct (physically separated) code unit. This strategy, called compositional approach [12], provides us a direct link between each feature and its implementation, giving us a high degree of feature traceability and therefore easier maintenance over time [13].…”
Section: B Core Assets Design and Implementationmentioning
confidence: 99%