2009 IEEE 31st International Conference on Software Engineering 2009
DOI: 10.1109/icse.2009.5070514
|View full text |Cite
|
Sign up to set email alerts
|

Taming Dynamically Adaptive Systems using models and aspects

Abstract: Since software systems need to be continuously available under varying conditions, their ability to evolve at runtime is increasingly seen as one key issue. Modern programming frameworks already provide support for dynamic adaptations. However the high-variability of features in Dynamic Adaptive Systems (DAS) introduces an explosion of possible runtime system configurations (often called modes) and mode transitions. Designing these configurations and their transitions is tedious and error-prone, making the sys… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
111
0

Year Published

2012
2012
2021
2021

Publication Types

Select...
5
3

Relationship

3
5

Authors

Journals

citations
Cited by 135 publications
(111 citation statements)
references
References 34 publications
0
111
0
Order By: Relevance
“…First, this new architecture model is validated using invariant checking [22]. This valid architectural model actually represents the new system state the runtime must reach to enforce the new security policy of the system.…”
Section: Adaptation and Evolution Strategiesmentioning
confidence: 99%
See 1 more Smart Citation
“…First, this new architecture model is validated using invariant checking [22]. This valid architectural model actually represents the new system state the runtime must reach to enforce the new security policy of the system.…”
Section: Adaptation and Evolution Strategiesmentioning
confidence: 99%
“…According to the classical MAPE control loop of self-adaptive applications, our reasoning process performs a comparison (using EMFCommpare) between the new architecture model (target configuration) and the current architecture model (kept synchronized with the running system) [23]. This process triggers a code generation/compilation process, and also generates a safe sequence of reconfiguration commands [22]. Actually, the code generation/-compilation process is only triggered if there are new proxy components, e.g.…”
Section: Adaptation and Evolution Strategiesmentioning
confidence: 99%
“…To address the problems of heterogeneity and dynamicity encountered in such an ubiquitous system, we proposed an Aspect-Oriented and Model-Based approach to tame the complexity of Dynamically Adaptive Systems (DAS) [8,9]. The overall approach is illustrated in Figure 1.…”
Section: Introductionmentioning
confidence: 99%
“…In previous work [9] using Aspect-Oriented Modeling (AOM) techniques, we can explicitly build a model of the configuration which is suitable for the current context, with no need for the designers to specify the whole set of configurations in extension. Using Model-Driven Engineering (MDE) techniques (model comparison) we were able to infer safe but sub-optimal migration plans to dynamically adapt the system.…”
Section: Introductionmentioning
confidence: 99%
“…Then, Models@Runtime [2] denotes model-driven approaches aiming at taming the complexity of software and system dynamic adaptation. It basically pushes the idea of reflection [11] one step further by considering the reflection layer as a real model: "something simpler, safer or cheaper than reality to avoid the complexity, danger and irreversibility of reality" [14], which enables the continuous design of complex, adaptive systems.…”
Section: Introductionmentioning
confidence: 99%