Support for evolving software architectures in the ArchWare ADL

Morrison, Ronald; Kirby, Graham N. C.; Balasubramaniam, Dharini; Mickan, Kath; Oquendo, Flávio; Cimpan, Sorana; Warboys, Brian; Snowdon, Bob; Greenwood, R. Mark

doi:10.1109/wicsa.2004.1310691

Cited by 38 publications

(28 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A framework uses the standardized component model to generate an appropriate adaptation behavior. From a system engineering perspective, Morrison et al [139] propose the ArchWare ADL for the offline specification of an evolving system architecture. The ADL description is used to generate an adapted system implementation according to the modeled evolution step.…”

Section: State Of the Artmentioning

confidence: 99%

Modeling Collaborations in Adaptive Systems of Systems

Wätzoldt

Giese

2015

Proceedings of the 2015 European Conference on Software Architecture Workshops

View full text Add to dashboard Cite

Recently, due to an increasing demand on functionality and flexibility, beforehand isolated systems have become interconnected to gain powerful adaptive System of Systems (SoS) solutions with an overall robust, flexible and emergent behavior. The adaptive SoS comprises a variety of different system types ranging from small embedded to adaptive cyber-physical systems. On the one hand, each system is independent, follows a local strategy and optimizes its behavior to reach its goals. On the other hand, systems must cooperate with each other to enrich the overall functionality to jointly perform on the SoS level reaching global goals, which cannot be satisfied by one system alone. Due to difficulties of local and global behavior optimizations conflicts may arise between systems that have to be solved by the adaptive SoS.This thesis proposes a modeling language that facilitates the description of an adaptive SoS by considering the adaptation capabilities in form of feedback loops as first class entities. Moreover, this thesis adopts the Models@runtime approach to integrate the available knowledge in the systems as runtime models into the modeled adaptation logic. Furthermore, the modeling language focuses on the description of system interactions within the adaptive SoS to reason about individual system functionality and how it emerges via collaborations to an overall joint SoS behavior. Therefore, the modeling language approach enables the specification of local adaptive system behavior, the integration of knowledge in form of runtime models and the joint interactions via collaboration to place the available adaptive behavior in an overall layered, adaptive SoS architecture.Beside the modeling language, this thesis proposes analysis rules to investigate the modeled adaptive SoS, which enables the detection of architectural patterns as well as design flaws and pinpoints to possible system threats. Moreover, a simulation framework is presented, which allows the direct execution of the modeled SoS architecture. Therefore, the analysis rules and the simulation framework can be used to verify the interplay between systems as well as the modeled adaptation effects within the SoS. This thesis realizes the proposed concepts of the modeling language by mapping them to a state of the art standard from the automotive domain and thus, showing their applicability to actual systems. Finally, the modeling language approach is evaluated by remodeling up to date research scenarios from different domains, which demonstrates that the modeling language concepts are powerful enough to cope with a broad range of existing research problems.-I - Zusammenfassung

show abstract

Section: State Of the Artmentioning

confidence: 99%

Modeling Collaborations in Adaptive Systems of Systems

Wätzoldt

Giese

2015

Proceedings of the 2015 European Conference on Software Architecture Workshops

View full text Add to dashboard Cite

show abstract

“…Apart from the Seq and Done constructors, the remaining operation constructors are handled analogously. Seq is composed by two operations (line 11), the leftmost operation is fully evaluated, and the resulting state is used for evaluating the rightmost operation (lines [12][13][14][15]. Done means that the end of the operation was reached, and it simply returns the current state (line 16).…”

Section: Computing States From Operationsmentioning

confidence: 99%

“…The function suffix returns a path with the second parameter suffixed to the first one. Moreover, we use other library functionschange interfaces path and change bindings path -to adjust the interfaces and bindings paths (lines [13][14]. Another useful function concerns the making of components in a specific path.…”

Section: Painless Standard Librarymentioning

confidence: 99%

“…This definition should be seen as a template, as its instances are the ones dynamically added/removed. Next, we define the Light Collector component (lines 21-23) and its two interfaces (lines [13][14][15][16][17][18][19]. The first interface is parametrized by its path as we shall use it later when specifying the Lights Control component (see Listing 1.11).…”

Section: N O R M a L B I N D I N G S P " L I G H T C O L L E C T O R mentioning

confidence: 99%

See 1 more Smart Citation

Painless Support for Static and Runtime Verification of Component-Based Applications

Gaspar

Henrio

Madelaine

2015

Fundamentals of Software Engineering

View full text Add to dashboard Cite

Architecture Description Languages (ADL) provide descriptions of a software system in terms of its structure. Such descriptions give a high-level overview and come from the need to cope with arbitrarily complex dependencies arising from software components. In this paper we present Painless, a novel ADL with a declarative trait supporting parametrized specifications and architectural reconfigurations. Moreover, we exhibit its reliable facet on its integration with ProActive -a middleware for distributed programming. This is achieved by building on top of Mefresa, a Coq framework for the reasoning on software architectures. We inherit its strong guarantees by extracting certified code, and subsequently integrating it in our toolchain.

show abstract

“…The ArchWare project proposes a metamodel, defined by an abstract syntax and formal semantic . Several concrete syntaxes are proposed (Verjus & Oquendo, 2003;, ArchWare -ADL Morrison et al, 2004) being the textual one. The core language is a well-formed extension of the high-order typed -calculus (Milner, 1999) that defines a calculus of communicating and mobile architectural elements.…”

Section: Archware Architecture Description Languages Foundations Andmentioning

confidence: 99%