From aspect-oriented design to aspect-oriented programs

Hanenberg, Stefan; Stein, Dominik; Unland, Rainer

doi:10.1145/1218563.1218570

Cited by 26 publications

(34 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Composition of interaction diagrams is not defined in the UML. The suggestions for "mechanical" composition (Roubtsova and Kuiper, 2003;Greenyer et al, 2008;Hanenberg et al, 2007) do not guarantee the specification of complete behaviour.…”

Section: Modelling Approaches In the Umlmentioning

confidence: 99%

A Test Generator for Model-Based Testing

Roubtsova¹,

Roubtsov

2014

Proceedings of the Fourth International Symposium on Business Modeling and Software Design

View full text Add to dashboard Cite

Abstract:The idea of software testing by software itself drives the attempts of creation of model based testing approaches. Model based testing relies on models, that encode the desired behaviour of a system, the relevant behaviour of its environment; however, both the static and the behaviour models are not directly applicable for model based testing. The models should be different from implementation and possess the observational consistency allowing preservation behaviour of parts in the behaviour of the whole. The models need to be built into a tool for preparation of the model and data for test generation. This paper proposes to use protocol models for model based testing. A protocol model presents the external behaviour. Unlike other modelling approaches, the Protocol Modelling semantics incorporates data into the model. This property gives us advantages for the choice of the strategy of test generation. The main contribution of the paper is a combination of algorithms for test generating from a protocol model. The preparation of a protocol model for test generation and the results of test generation are illustrated with an example.

show abstract

Section: Modelling Approaches In the Umlmentioning

confidence: 99%

A Test Generator for Model-Based Testing

Roubtsova¹,

Roubtsov

2014

Proceedings of the Fourth International Symposium on Business Modeling and Software Design

View full text Add to dashboard Cite

show abstract

“…Structural and behavioral modeling is achieved by employing for instance class diagrams, state charts, and sequence diagrams. In contrast to our approach, their objective is not to perform the weaving at the modeling level, but rather to generate code for aspect-oriented programs from an aspect-oriented design as shown in [13]. Again, it would be possible to change the notation used in our approach and express pointcuts using JPDDs, if modelers find them more intuitive.…”

Section: Related Workmentioning

confidence: 99%

Aspect-oriented multi-view modeling

Kienzle

Abed

Klein

2009

Proceedings of the 8th ACM International Conference on Aspect-Oriented Software Development

102

View full text Add to dashboard Cite

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.

show abstract

“…describe a UML-based notation for AspectJ called the Aspect-Oriented Design Model (AODM). That work was succeeded by more focused work on expressing pointcuts in UML in the work on Join Point Designation Diagrams (JPDD) [75,158,159]. JPDD provides a notation, semantics, and a tool implementation for specifying queries graphically using extensions to UML.…”

Section: Separation Of Concerns In Modellingmentioning

confidence: 99%

“…This shortcoming was addressed in the work on Join Point Designation Diagrams (JPDD) [75], which generated complex pointcut expressions based on JPDD sequence diagrams. This simplifies the specification of complex pointcut expressions that cap- Vanderperren et.al.…”

Section: Separation Of Concerns In Modellingmentioning

confidence: 99%