Towards a standard design language for AOSD
AOSD '02 Proceedings of the 1st international conference on Aspect-oriented software development
The Java Language Specification
The Java Language Specification
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
Theme: An Approach for Aspect-Oriented Analysis and Design
Proceedings of the 26th International Conference on Software Engineering
Aspect-Oriented Analysis and Design
Aspect-Oriented Analysis and Design
Aspect-oriented multi-view modeling
Proceedings of the 8th ACM international conference on Aspect-oriented software development
From aspect-oriented models to aspect-oriented code?: the maintenance perspective
Proceedings of the 9th International Conference on Aspect-Oriented Software Development
Comparing six modeling approaches
MODELS'11 Proceedings of the 2011th international conference on Models in Software Engineering
Aspect-oriented model-driven code generation: A systematic mapping study
Information and Software Technology
Integrating protocol modelling into reusable aspect models
Proceedings of the 5th ACM SIGCHI Annual International Workshop on Behaviour Modelling - Foundations and Applications
Hi-index | 0.00 |
When aspect-oriented modeling techniques are used in the context of Model-Driven Engineering, a possible way of obtaining an executable from an aspect-oriented model is to map it to code written in an aspect-oriented programming language. This paper outlines the most important challenges that arise when defining such a mapping: mapping structure and behavior of a single aspect, mapping instantiation of structure and behavior in target models, mapping conflict resolution between aspects, and mapping aspect dependencies and variability. To explain these mapping issues, our paper presents details on how to map Reusable Aspect Models (RAM) to AspectJ source code. The ideas are illustrated by presenting example models and corresponding mapped code from the AspectOPTIMA case study.