Proceedings of the 7th International Workshop on Feature-Oriented Software Development 2016
DOI: 10.1145/3001867.3001870
|View full text |Cite
|
Sign up to set email alerts
|

Implicit constraints in partial feature models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
9
0

Year Published

2017
2017
2020
2020

Publication Types

Select...
5
3

Relationship

2
6

Authors

Journals

citations
Cited by 41 publications
(9 citation statements)
references
References 27 publications
0
9
0
Order By: Relevance
“…These include automated analyses of feature models [9,38] and analyses also incorporating other domain artifacts [86,92]. In particular, a logical representation has been used for feature-model evolution [67,87], feature-model interfaces and slicing [1,74], computation of implicit constraints [3], product configuration [44,72] including staged configuration [28], parsing [50], dead-code analysis [83], code simplification [93], type checking [85], consistency checking [29], dataflow analyses [56], model checking [19], testing [16] including variability-aware execution [66] and sampling [58,89], optimization of non-functional properties [78], and variant-preserving refactoring [35]. Each of these analyses may profit from knowledge compilation.…”
Section: State-of-the-artmentioning
confidence: 99%
See 1 more Smart Citation
“…These include automated analyses of feature models [9,38] and analyses also incorporating other domain artifacts [86,92]. In particular, a logical representation has been used for feature-model evolution [67,87], feature-model interfaces and slicing [1,74], computation of implicit constraints [3], product configuration [44,72] including staged configuration [28], parsing [50], dead-code analysis [83], code simplification [93], type checking [85], consistency checking [29], dataflow analyses [56], model checking [19], testing [16] including variability-aware execution [66] and sampling [58,89], optimization of non-functional properties [78], and variant-preserving refactoring [35]. Each of these analyses may profit from knowledge compilation.…”
Section: State-of-the-artmentioning
confidence: 99%
“…2 These models have been translated with an extension of the Linux Variability Analysis Tools (LVAT) [11]. 3 The advantage over the previous benchmark is that the hierarchy of features is available and that models are available in a version without newly introduced variables. While the benchmark also contains Linux, the feature model represents version 2.6.33.3, which has been released in April 2010 and used for illustration in Figure 1.…”
Section: Call For Contributionsmentioning
confidence: 99%
“…Satisfiability solving is a ubiquitous technology in software product lines for a diverse set of analyses ranging from anomaly detection [2,38,46], dead code analysis [62], sampling [47,65], and automated analysis of feature models [10,32,64]. The general pattern is to represent parts of the system or feature model as a propositional formula [9,25,48], and reduce the analysis to a satisfiability (SAT) problem.…”
Section: Introductionmentioning
confidence: 99%
“…FM 0 contains no spectre/meltdown-related features; FM 1 contains a set of new features named spectre_v2, nospec_store_bypass_disable, l1tf, and pti; and FM 2 contains a single feature mitigations that combines all of the exploit prevention features from FM 1 . 2 We introduce some notation to track particular features and propositional formulas across multiple feature models. For features we use f i.j to refer to the th feature in the th feature model.…”
Section: Introductionmentioning
confidence: 99%
“…A CPPS can interact with its environment, make context-aware decisions, and self-adapt to uncertain conditions [19,32], supporting the envisioned flexibility. Recent research shows growing interest in applying SPL engineering concepts to CPPS engineering [1,7,24,30].…”
Section: Introductionmentioning
confidence: 99%