Executable UML: A Foundation for Model-Driven Architectures
Executable UML: A Foundation for Model-Driven Architectures
The Pragmatics of Model-Driven Development
IEEE Software
Model-Driven Software Development
Model-Driven Software Development
Adding trace matching with free variables to AspectJ
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Expressing different conceptual models of join point selections in aspect-oriented design
Proceedings of the 5th international conference on Aspect-oriented software development
Model-Driven Software Development: Technology, Engineering, Management
Model-Driven Software Development: Technology, Engineering, Management
Proceedings of the 6th international conference on Aspect-oriented software development
Execution and simulation of (profiled) UML models using pópulo
Proceedings of the 2008 international workshop on Models in software engineering
A graphical notation to specify model queries for MDA transformations on UML models
MDAFA'03 Proceedings of the 2003 European conference on Model Driven Architecture: foundations and Applications
Model-Driven engineering in a large industrial context — motorola case study
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
On relationships between query models
ECMDA-FA'05 Proceedings of the First European conference on Model Driven Architecture: foundations and Applications
| Hi-index | 0.00 |
Join Point Designation Diagrams (JPDDs) give developers the ability to model their join point selections in the UML, independent of any existing aspect-oriented programming language. In order to apply JPDDs in real software projects, it is necessary to have an executable representation of them -- either in terms of generated code for the desired aspect-oriented programming language or directly as executable diagrams in an environment that permits to execute UML diagrams. While principles for translating JPDDs into a target language are already known, it turns out that developers who follow those principles still face a large number of problems due to the complex selection semantics for dynamic join point: developers need to collect all data that is necessary to detect dynamic join points, and they need to maintain that data in appropriate data structures. In order to ease this step, it is desirable to translate JPDDs into an intermediate representation that equips the developers with a more concrete understanding about what information is needed, and when it needs to be stored or updated. This paper mainly addresses the motivation for such an intermediate representation and gives a first step into that direction -- the translation of JPDDs based on sequence diagrams into executable state charts.