Proceedings of the 13th International Workshop on Variability Modelling of Software-Intensive Systems 2019
DOI: 10.1145/3302333.3302346
|View full text |Cite
|
Sign up to set email alerts
|

Characterizing safe and partially safe evolution scenarios in product lines

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
4
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
3
2
2

Relationship

2
5

Authors

Journals

citations
Cited by 10 publications
(4 citation statements)
references
References 17 publications
0
4
0
Order By: Relevance
“…The tools we used for the quantitative evaluation may affect internal validity as they may contain defects. With KConfigReader and FEVER, we rely on tools that have been used in prior studies [13,22,31,33,41]. In particular, FEVER may detect all or may wrongly detect commits matching the templates in the history of the Linux kernel.…”
Section: Threats To Validitymentioning
confidence: 99%
See 1 more Smart Citation
“…The tools we used for the quantitative evaluation may affect internal validity as they may contain defects. With KConfigReader and FEVER, we rely on tools that have been used in prior studies [13,22,31,33,41]. In particular, FEVER may detect all or may wrongly detect commits matching the templates in the history of the Linux kernel.…”
Section: Threats To Validitymentioning
confidence: 99%
“…In the process of product-line evolution, domain engineers may change the feature model, artifacts, and the feature-artifact mapping [12]. This can lead to unintended changes to product behavior [13]. For instance, if a feature A is merged into another feature B, configurations selecting only B and not A represent different product behavior before and after evolution.…”
mentioning
confidence: 99%
“…The potential is amplified by several factors. First, a feature model is typically changed less frequently than implementation artifacts [42,54,69]. As a consequence, a new BDD only needs to be created when the feature model changes.…”
Section: Motivationmentioning
confidence: 99%
“…In the process of product-line evolution, domain engineers may change the set of features, artifacts, and the mapping [11]. This can lead to unintended changes to product behavior [9]. For instance, if a feature A is merged into another feature B, configurations selecting only B and not A represent different product behavior before and after evolution.…”
Section: Introductionmentioning
confidence: 99%