Reconfigurable service-based architecture based on variability description

Abstract

Self-adaptive systems evolve during system's execution against changes in operating environment. Such evolution and reconfiguration can be specified at architecture level using a syntactical expressive language such as Architecture Description Languages (ADLs). Variability modeling is an excellent instrument to model variations of software artifacts and their behavior within a self-adaptive system. However, existing ADLs that support dynamic reconfiguration do not explicitly model variation points on which the reconfiguration is based. This constitutes a barrier for a flexible management of reconfiguration at architecture level as well as traceability issues between a dynamic description given at architectural level and its counterpart at other abstraction levels. In this paper, we propose a variant-rich service-oriented ADL that enables system to reconfigure itself at runtime in response to a context change. To this end, our modular ADL, called Dynamic Service-Oriented Product Lines Architecture Description Language (DSOPL-ADL), specifies dynamic reconfigurations at architecture level besides specifying structural, variability and context information. Among several specified variable configurations at architecture level, one concrete configuration is generated at runtime triggered by a context value. Furthermore, an implementation code can be automatically generated from the architectural description.

Data interoperability between DDS and HLA through a dynamically reconfigurable gateway

“…These systems configure themselves without human interaction by monitoring changes in their operating environment. 29 One of our previous work is about the runtime adaptability of AmI systems. We describe how a component-oriented AmI system reacts to changing conditions at runtime in Reference 30.…”

“…Dynamically adaptable systems are usually self‐adaptive. These systems configure themselves without human interaction by monitoring changes in their operating environment 29 …”

Architectural Views to the Representation of Dynamic Software Architectures

“…• Reconfiguration Triggers: Conditions or triggers are stimuli, situations, or events that trigger an adaptation at run-time (OQUENDO, 2016;LING, 2013;ZHANG et al, 2016) and enable the Reconfiguration Manager to identify a reconfiguration to be proceeded, requesting the addition/removal of components, for example (BRAD-BURY et al, 2004). In general, such conditions refer to system failures, changes in requirements, changes in the environment, among other events (DING, 2016;AD-JOYAN;SERIAI, 2017;CIMATTI et al, 2018). Triggers can be classified into two main categories:…”

“…According to the SMS, architectures must be reconfigured when static solutions are not able to achieve the quality attributes required (BRADBURY, 2004;CÎMPAN et al, 2005;CIMATTI et al, 2018;ADJOYAN;SERIAI, 2017). This element is textual and should express the quality attributes that require those dynamic solutions.…”