Design-Level Detection of Interactions in Aspect-UML Models Using Alloy.

Mostefaoui, Farida; Vachon, Julie

doi:10.5381/jot.2007.6.7.a6

Cited by 21 publications

(13 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Instead, with FeatureAlloy, we concentrate on semantic interactions. Mostefaoui and Vachon translate UML models into Alloy models to detect design-level interactions in Aspect-UML models [31]. Our aim has been to bridge the gap between domain analysis and implementation in FOSD, which goes beyond their work.…”

Section: Implementation and Case Studiesmentioning

confidence: 99%

Detecting Dependences and Interactions in Feature-Oriented Design

Apel

Scholz

Lengauer

et al. 2010

2010 IEEE 21st International Symposium on Software Reliability Engineering

View full text Add to dashboard Cite

Abstract-Feature-oriented software development (FOSD) aims at the construction, customization, and synthesis of large-scale software systems. We propose a novel software design paradigm, called feature-oriented design, that takes the distinguishing characteristics of FOSD into account, especially the clean and consistent mapping between features and their implementations as well as the tendency of features to interact inadvertently. We extend the lightweight modeling language Alloy with support for featureoriented design and call the extension FeatureAlloy. By means of an implementation and four case studies, we demonstrate how feature-oriented design with FeatureAlloy facilitates separation of concerns, variability, and reuse of models of individual features and helps defining and detecting semantic dependences and interactions between features.

show abstract

Section: Implementation and Case Studiesmentioning

confidence: 99%

Detecting Dependences and Interactions in Feature-Oriented Design

Apel

Scholz

Lengauer

et al. 2010

2010 IEEE 21st International Symposium on Software Reliability Engineering

View full text Add to dashboard Cite

show abstract

“…In this paper we did not focus on addressing problems related to fragile pointcuts; we do however discuss this issue (at the program level) in other work [34,19]. The authors of [33,32] aim at detecting the possible semantic interferences that can manifest in models expressed using the Aspect-UML language. To this aim, the static language elements of Aspect-UML are mapped to the specification language of Alloy.…”

Section: Related Workmentioning

confidence: 99%

“…Most of them either require an abstract semantic model of the overall system that has to be defined specifically for each new system [33,32]; or they work at the implementation level and assume a particular aspect-oriented programming language [4,24]. Only a few aspect-interference detection approaches have been proposed that work at the modeling level [33,32].…”

Section: Introductionmentioning

confidence: 99%

A Graph-Based Aspect Interference Detection Approach for UML-Based Aspect-Oriented Models

Ciraci

Havinga

Akşit

et al. 2010

Transactions on Aspect-Oriented Software Development VII

View full text Add to dashboard Cite

Abstract. Aspect Oriented Modeling (AOM) techniques facilitate separate modeling of concerns and allow for a more flexible composition of these than traditional modeling technique. 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. Current techniques for conflict detection among aspects generally have at least one of the following weaknesses. They require to manually model the abstract semantics for each system; or they derive the system semantics from code assuming one specific aspect-oriented language. Defining an extra semantics model for verification bears the risk of inconsistencies between the actual and the verified design; verifying only at implementation level hinders fixing errors in earlier phases. We propose a technique for fully automatic detection of conflicts between aspects at the model level; more specifically, our approach works on UML models 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 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" 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 two simulated aspects, the state space contains 623 different states and 9 different execution paths. Nevertheless, in case the right pruning methods are used, the state-space only grows linearly with the number of aspects; therefore, the automatic analysis scales.

show abstract

“…Mostefaoui and Vachon [38] also use Alloy to analyze behavioral interactions of aspect-oriented models. Base behavior is transformed into an Alloy model along with joint points, point cut specifications, and aspect behavioral advice.…”

Section: Related Workmentioning

confidence: 99%