Aspect-oriented multi-view modeling

Abstract

Multi-view modeling allows a developer to describe a software system from multiple points of view, e.g. structural and behavioral, using different modeling notations. Aspectoriented modeling techniques have been proposed to address the scalability problem within individual modeling notations. This paper presents RAM, an aspect-oriented modeling approach that provides scalable multi-view modeling. RAM allows the modeler to define stand-alone reusable aspect models using 3 modeling notations. The aspect models support the modeling of structure (using UML class diagrams) and behavior (using UML state and sequence diagrams). RAM supports aspect dependency chains, which allows an aspect providing complex functionality to reuse the functionality provided by other aspects. The RAM weaver can create woven views of the composed model for debugging, simulation or code generation purpose, as well as perform consistency checks during the weaving and on the woven model to detect inconsistencies of the composition.

Aspect-Oriented Model Development at Different Levels of Abstraction

“…Reusable Aspect Models (RAM) [7] describes the structure and behaviour of a concern using class, state and sequence diagrams. Fig.…”

Report of the 15th International Workshop on Aspect-Oriented Modeling

“…Wisam Al Abed from McGill University in Montreal, Canada, presented how the Reusable Aspect Models approach, previously published in [1,2] can be extended to support information hiding principles. In object-orientation, the class construct allows a modeler to encapsulates state and behavior.…”

Aspect-Oriented Development Using Protocol Modeling

“…In the Reusable Aspect Models (RAM) [19] approach a model of a concern or functionality "contains up to three different kinds of views: a structural view, state views and message views -which are grouped together in an aspect model, a special UML package" [19].…”

“…entities that are not directly or indirectly bound to model elements of some other aspect models, and methods whose name and signature are yet to be determined". These incomplete classes are called "mandatory instantiation parameters" and they are recognized by | character attached to their name and as UML template parameters on the right hand side of the structural view compartment [19].…”

“…In UML terms, the state view compartment describes the usage protocol of the entity. To be complete, the state diagram must contain each method defined in the structural view for the entity at least once [19]".…”