Interaction Analysis in Aspect-Oriented Models

Mehner, Katharina; Monga, Mattia; Taentzer, Gabriele

doi:10.1109/re.2006.35

Cited by 28 publications

(16 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For such detection, typically the UML models are transformed into graphs which are then analyzed to look for interactions. This approach is also advocated by Ciraci et al [9] and Mehner et al [25].…”

Section: Related Workmentioning

confidence: 92%

Expressing aspectual interactions in design: evaluating three AOM approaches in the slot machine domain

2014

View full text Add to dashboard Cite

In the context of an industrial project, we evaluated the implementation of the software of a casino slot machine. This software has a significant amount of crosscutting concerns that depend on and interact with each other as well as with the modular concerns. We therefore wished to express our design using an appropriate aspect-oriented modeling approach. We therefore evaluated three candidate methodologies: Theme/UML, WEAVR, and RAM to establish their suitability. Remarkably, only the last of the three has shown to allow an adequate expression of the interactions, albeit not fully explicit. The first two fall short because half of the interaction types cannot be expressed at all while the other half need to be expressed using a work-around that hides the intention of the design. Neither does RAM allow a fully explicit expression of interactions, but it would be the most adequate approach for the slot machine case.FONDECYT 113025

show abstract

Section: Related Workmentioning

confidence: 92%

Expressing aspectual interactions in design: evaluating three AOM approaches in the slot machine domain

2014

View full text Add to dashboard Cite

show abstract

“…In addition, other approaches employ technologies such as program slicing [14], graph transformation [15,16] and semantics annotation [17] to detect the aspect interactions in AOSD. The approach in [14] uses programming slicing to detect the influences between aspects.…”

Section: B Implementing the Examplementioning

confidence: 99%

“…The approach in [14] uses programming slicing to detect the influences between aspects. The graph transformation based approach in [15] is to analyze potential inconsistencies caused by aspect composition. The graph transformation based approach in [16] can detect aspect interference at shared join points.…”

Section: B Implementing the Examplementioning

confidence: 99%

Detecting and Evaluating Semantic Influences of Aspect Weaving in Aspect Oriented Models

Yang¹

2013

JSW

View full text Add to dashboard Cite

Weaving an aspect may introduce undesired impacts on behavior of the base model or other afore-woven aspects. An approach to detect and evaluate the semantic influences of an aspect weaving on a pattern is presented. The pattern specifies a desired behavior that should stay unaltered or occur in the woven model. The detection and evaluation are based on the semantic relationship between a pattern and its projection that represents its actual semantics in the woven model. Five types of aspect weaving influences are identified. The approach has the Process Algebras (PA) as the underlying formalisms and has been implemented by mapping to the Concurrency Workbench (CWB) tool. An example shows the effectiveness.Index Terms-aspect weaving, influences, aspect interaction, aspect interference, aspect-oriented software development Chunhua Yang received her Ph.D., M.S. and B.S. degrees in

show abstract

“…In the current version of Theme/UML, sequence diagrams are used to specify when and how the templates interact with the base themes. However, composition relationships could equally be visualized using any of UML's standard behavioral diagrams including collaboration [Mehner et al 2006], activity [Cui et al 2009], and state [Cottenier et al 2007a] diagrams. The choice of behavioral diagram to capture theme composition relationships depends largely on how behavior is modeled within individual themes.…”

Section: Theme/umlmentioning

confidence: 99%

Managing embedded systems complexity with aspect-oriented model-driven engineering

Driver

Reilly

Linehan

et al. 2010

ACM Trans. Embed. Comput. Syst.

View full text Add to dashboard Cite

Model-driven engineering addresses issues of platform heterogeneity and code quality through the use of high-level system models and subsequent automatic transformations. Adoption of the model-driven software engineering paradigm for embedded systems necessitates specification of appropriate models of often complex systems. Modern embedded systems are typically composed of multiple functional and nonfunctional concerns, with the nonfunctional concerns (e.g., timing and performance) typically affecting the design and implementation of the functional concerns. The presence of crosscutting concerns makes specification of adequate platform-independent models a significant challenge. Aspect-oriented software development is a separation of concerns technique that decomposes systems into distinct features with minimal overlap. In this article, we illustrate how Theme/UML, an aspect-oriented modeling approach, can be used to separate embedded systems concerns and reduce complexity in design. We also present Model-Driven Theme/UML, a toolset for model-driven engineering of embedded systems that supports modularised design with Theme/UML and automatic transformations to composed models and source code.

show abstract

Interaction Analysis in Aspect-Oriented Models

Abstract: Abstract

Cited by 28 publications

References 18 publications

Expressing aspectual interactions in design: evaluating three AOM approaches in the slot machine domain

Expressing aspectual interactions in design: evaluating three AOM approaches in the slot machine domain

Detecting and Evaluating Semantic Influences of Aspect Weaving in Aspect Oriented Models

Managing embedded systems complexity with aspect-oriented model-driven engineering

Contact Info

Product

Resources

About