Aspect Oriented Modeling (AOM) techniques facilitate separate modeling of concerns and allow for a more flexible composition of the resulting models than traditional techniques. While this improves the understandability of each submodel, in order to reason about the behavior of the composed system and to detect conflicts among submodels, automated tool support is required.
We propose a technique and tool support for fully automatic detection of conflicts between aspects at the model level; more specifically, our approach works on models defined in UML with an extension for modeling pointcuts and advice. As back-end we use a graph-based model checker, for which we have defined an operational semantics of UML diagrams, pointcuts and advice. In order to simulate the system, we automatically derive a graph model from the diagrams. The simulation result is another graph, which represents all possible program executions, and which can be verified against a declarative specification of invariants.
To demonstrate our approach, we discuss a UML-based AOM model of the "Crisis Management System" (CMS) and a possible design and evolution scenario. The complexity of the system makes conflicts among composed aspects hard to detect: already in the case of five simulated aspects, the state space contains 9991 different states and 99 different execution paths. Nevertheless, by using appropriate pruning methods the state space only grows polynomially with the number of aspects. In practical cases, the order of the polynomial is very small, e.g., 2 in the case of the simulated CMS; therefore, the automatic analysis scales.
|Title of host publication||Transactions on Aspect-Oriented Software Development VII|
|Subtitle of host publication||A Common Case Study for Aspect-Oriented Modeling|
|Editors||Shmuel Katz, Mira Mezini, Jörg Kienzle|
|Place of Publication||Berlin, Heidelberg|
|Number of pages||56|
|Publication status||Published - 20 Sep 2010|
|Name||Lecture Notes in Computer Science|
- Aspect interference detection
- Aspect-oriented UML
- Graph-based Model Checking