2018
DOI: 10.1016/j.scico.2018.05.002
|View full text |Cite
|
Sign up to set email alerts
|

Context-aware reconfiguration in evolving software product lines

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
32
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 19 publications
(32 citation statements)
references
References 36 publications
(78 reference statements)
0
32
0
Order By: Relevance
“…• Mauro et al [18] present a framework for the modeling and evolving reconfiguration of context-aware SPL instances. They consider the environmental impact on updated features and new contextual information on the SPL evolution.…”
Section: Related Workmentioning
confidence: 99%
“…• Mauro et al [18] present a framework for the modeling and evolving reconfiguration of context-aware SPL instances. They consider the environmental impact on updated features and new contextual information on the SPL evolution.…”
Section: Related Workmentioning
confidence: 99%
“…In this section, we formalize the notion of Context-aware Feature Model (CaFM). Following [24], a context can be considered as a variable that someone externally (e.g., the user of the software or the environment) can set. These new variables impose constraints over features and therefore on the products that can be obtained.…”
Section: Context-aware Feature Modelsmentioning
confidence: 99%
“…To the best of our knowledge, this is the first paper to formally define CaFMs and their anomaly analysis. CaFMs were originally introduced in [24] and the idea that QBF solvers can be used to check the voidness was first presented in [23] without providing, however, any comparison w.r.t. the iterative approach.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
See 1 more Smart Citation
“…Although the identified issues are motivated by a press line domain, we notice that the ICPS evolution is something known in the literature [13,14], and considering the domain analysis performed in our previous work [5], we realized that ICPS evolution besides the different ICPS topologies are not specific problems for press lines. In the literature, many authors consider software evolution [14][15][16][17], but very few of them consider software and hardware evolution [18,19] even though those who consider runtime variability do not consider uncertainties; hence, as far as we know, no one in the literature has give the response to detecting ICPS evolution in order (1) to have the traceability of what has happened in an ICPS over time; (2) to classify the occurred evolution in order to communicate immediately to the users to avoid any bad decisions; and (3) to give a solution which considers different ICPS topologies.…”
Section: Introductionmentioning
confidence: 99%