An Architectural Approach to Support Online Updates of Software Product Lines

Weyns, Danny; Michalik, Bartosz; Helleboogh, Alexander; Boucké, Nelis

doi:10.1109/wicsa.2011.34

Cited by 9 publications

(6 citation statements)

References 17 publications

(17 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Context changes not anticipated during design-time are addressed by learning new adaptation rules dynamically, or by modifying and improving existing rules. On the other hand, evolution [4] has been proposed as a way to modify the DSPL configu-ration space [3,24,33]. The variability of the DSPL (in terms of features and their constraints) is changed based on insights gathered during system operation, while derived configurations are running.…”

Section: Learning and Evolutionmentioning

confidence: 99%

Learning and evolution in dynamic software product lines

Sharifloo

Metzger

Quinton

et al. 2016

Proceedings of the 11th International Symposium on Software Engineering for Adaptive and Self-Managing Systems

View full text Add to dashboard Cite

A Dynamic Software Product Line (DSPL) aims at managing run-time adaptations of a software system. It is built on the assumption that context changes that require these adaptations at run-time can be anticipated at design-time. Therefore, the set of adaptation rules and the space of configurations in a DSPL are predefined and fixed at design-time. Yet, for large-scale and highly distributed systems, anticipating all relevant context changes during design-time is often not possible due to the uncertainty of how the context may change. Such design-time uncertainty therefore may mean that a DSPL lacks adaptation rules or configurations to properly reconfigure itself at run-time. We propose an adaptive system model to cope with design-time uncertainty in DSPLs. This model combines learning of adaptation rules with evolution of the DSPL configuration space. It takes particular account of the mutual dependencies between evolution and learning, such as using feedback from unsuccessful learning to trigger evolution. We describe concrete steps for learning and evolution to show how such feedback can be exploited. We illustrate the use of such a model with a running example from the cloud computing domain

show abstract

Section: Learning and Evolutionmentioning

confidence: 99%

Learning and evolution in dynamic software product lines

Sharifloo

Metzger

Quinton

et al. 2016

Proceedings of the 11th International Symposium on Software Engineering for Adaptive and Self-Managing Systems

View full text Add to dashboard Cite

show abstract

“…The runtime models of the self-adaptive system can support integrators with performing online updates of the system. In [25], we have demonstrated that accurate models of the running system are essential to understand dependencies among components and as such to perform correct online updates. The results of diagnosis may also be used for strategic decision making.…”

Section: Figure 8: Overview Runtime Diagnosismentioning

confidence: 99%

Towards an integrated approach for validating qualities of self-adaptive systems

Weyns

2012

Proceedings of the Ninth International Workshop on Dynamic Analysis

Self Cite

View full text Add to dashboard Cite

Self-adaptation has been widely recognized as an effective approach to deal with the increasing complexity and dynamicity of modern software systems. One major challenge in self-adaptive systems is to provide guarantees about the required runtime qualities, such as performance and reliability. Existing research employs formal methods either to provide guarantees about the design of a self-adaptive systems, or to perform runtime analysis supporting adaptations for particular quality goals. Yet, work products of formalization are not exploited over different phases of the software life cycle. In this position paper, we argue for an integrated formally founded approach to validate the required software qualities of self-adaptive systems. This approach integrates three activities: (1) model checking of the behavior of a self-adaptive system during design, (2) model-based testing of the concrete implementation during development, and (3) runtime diagnosis after system deployment. We illustrate the approach with excerpts of an initial study and discuss for each activity research challenges ahead.

show abstract

“…Moreover, the integrated meta-model offers the basis for an architectural repository that we use to harvest the relevant information from which the models are derived (we further discuss this in following subsection). The detailed description of the update viewpoint is presented in our previous work [20].…”

Section: Architecture-centric Approachmentioning

confidence: 99%

“…The repository is populated with the data collected by the harvesters. The repository stores architecture knowledge that complies to the integrated meta-model defined by the update viewpoint [20]. We used the Eclipse Modeling Framework 2 as a basis for the repository.…”

Section: Architecture-centric Approachmentioning

confidence: 99%

See 1 more Smart Citation

Supporting Online Updates of Software Product Lines: A Controlled Experiment

Michalik

Weyns

Boucké

et al. 2011

2011 International Symposium on Empirical Software Engineering and Measurement

Self Cite

View full text Add to dashboard Cite

Abstract-The evolution of Software Product Lines (SPL) is challenging because stakeholders have to deal with both regular evolution and the co-existence of different products. Our focus of product evolution is on the tasks integrators have to perform to update deployed SPL products with minimal interruption of services. In case of Egemin, our industrial partner, the updates of SPL products is further hampered as a consequence of outdated and imprecise architectural knowledge of deployed products. To facilitate the updates of products, we have developed the architecture-centric approach which comprises two complementary parts: an update viewpoint and a supporting tool.In this paper we present an evaluation of the architecturecentric approach. The approach is compared with the Egemin's current update approach in a controlled experiment. In the experiment 17 professionals were asked to perform 68 updates of logistic systems. The results obtained from the experiment show that the architecture-centric approach significantly improves the correctness of updates and reduces the interruption of services during updates of Egemin's SPL products.

show abstract

An Architectural Approach to Support Online Updates of Software Product Lines

Cited by 9 publications

References 17 publications

Learning and evolution in dynamic software product lines

Learning and evolution in dynamic software product lines

Towards an integrated approach for validating qualities of self-adaptive systems

Supporting Online Updates of Software Product Lines: A Controlled Experiment

Contact Info

Product

Resources

About