2 July 2013, Montpellier, France

Please note that the workshop starts at 8:30 a.m. Thank you!

In Model-Driven Engineering, the functionality of complex systems lies beyond the representative capabilities of a single model. Therefore, an increasing variety of heterogeneous models and languages are used in the various phases of software development. Information about a system is consequently spread across these various models with possible overlaps, redundancies, and inconsistencies. To cope with this complexity, which normally exceeds the cognitive capacity of a single individual, various approaches have been developed to re-organize information during systems development.
Aspect-Oriented Modelling (AOM) restructures software along cross-cutting concerns, which transgress the borders of modelling formalisms, and integrates them in a weaving or composition process. View-based modelling approaches address the problem with partial views that show only relevant parts of a system and offer direct editing and re-integration rather than weaving or composing. The Orthographic Software Modeling (OSM) approach is a view-centric development process that generates all representations of a system, from diagrams down to source code, from a single underlying model using transformations.

The goal of this workshop is to bring together researchers and practitioners with an interest in model-driven software development processes to foster a fruitful cross-pollination of ideas between the aspect-oriented community and the emerging view-based community. The workshop will comprise discussion and break-out sessions to identify commonalities and differences of the different approaches. In order to provide a foundation for these discussions, we encourage submissions on new modelling concepts as well as technical papers describing implementation approaches and formalisms.

The workshop is interested in submissions on all topics related to model-driven development processes, view-based, aspect-oriented and orthographic software modelling. More specifically, this includes:

• bridging the gap between different metamodels or MDE views
• generating, defining and evolving different views of metamodels
• round-trip engineering and co-evolution of different metamodels
• composition of different models and metamodels
• (bidirectional) transformations of metamodels
• avoiding inconsistencies, overlap and redundancies in different metamodels
• generating a single metamodel for multiple views or formalisms
• separating and re-integrating cross-cutting concerns or model weaving
• dynamic information hiding for partial views