AO-ADL: An ADL for Describing Aspect-Oriented Architectures

Generating CAM aspect-oriented architectures using Model-Driven Development

“…In this sense, DAOP-ADL [31,36] (part of CAM/DAOP) and Fractal [30,37] extend traditional components with a new kind of aspectual interfaces. However, other approaches such as AO-ADL [34], AspectualACME [9] and Navasa's language [33] use the same building block (e.g., the component) to represent both non-crosscutting and crosscutting concerns. Finally, in PRISMA [32] aspects are a new abstraction used to define the internal structure of both components and connectors.…”

“…As a result, several aspect-oriented (AO) architecture description languages (ADLs), have been defined [9,[30][31][32][33][34]. These languages have to deal with two main issues: (1) the architectural blocks used to model crosscutting concerns, and (2) the composition between the architectural blocks modelling crosscutting and non-crosscutting concerns.…”

Using Aspects for Enforcing Formal Architectural Invariants

“…ADL, UML [7], etc.). For instance, AO-ADL [27] is an aspect-oriented architecture description language, which models crosscutting concerns using components and provides a mechanism for defining aspect-oriented connector templates. In our current work, we are not interested in defining aspects at such a high level; we just use aspects to enforce formal architectural constraints at the implementation level.…”

Study on Weaving Process at Software Architectural level

“…In AspectualACME, configuration describes the players of both base role and crosscutting role, and then connector along with configuration realizes the weaving between aspect and component. AO-ADL [9] is the extension of the semantic of traditional connectors in order to represent the crosscutting effect of "aspectual" components. Some information about weaving is localized in connectors by introducing aspectual role and aspectual binding.…”