Keywords:
Astract: Abstract. Metamodel evolution and model co-evolution are considered to be essential ingredients for the successful adoption of model-driven engineering in practice. In this respect, on the one hand, dedicated co-evolution languages have been proposed for migrating models conforming to an initial metamodel to models conforming to a revised metamodel with the drawback of requiring to learn a new language. On the other hand, the employment of dedicated model-to-model transformation languages has been proposed demanding for the speci cation of rules for copying unchanged elements. In this paper, we propose to tackle the co-evolution problem from a di erent viewpoint. Instead of describing the co-evolution of models as a transformation between two metamodels, we employ existing inplace transformation languages. For this, the prerequisite is to represent both language versions within one metamodel which is automatically computed by merging the initial and the revised metamodel. This ensures that the initial as well as the revised model conform to the merged metamodel, enabling the employment of inplace transformations for initializing new metamodel elements. Finally, a check-out transformation is used for eliminating model elements which are no longer covered by the revised metamodel.We demonstrate this idea by using ATL for merging the metamodels and realizing the check-out transformation. Furthermore, we discuss the ATL re nement mode for co-evolving the models.

Keywords:
Astract: Software engineering deals with the development of complex software systems which is an inherently team-based task. Therefore, version control support is needed to coordinate the teamwork and to manage parallel modifications. If conflicting modifications occur, in standard approaches the developer who detected the conflict is responsible for the conflict resolution alone and has to resolve the conflict immediately. Especially in early project phases, when software models are typically employed for brainstorming, analysis, and design purposes, such an approach bears the danger of losing important viewpoints of different stakeholders and domain engineers, resulting in a lower quality of the overall system specification. In this paper, we propose conflict-tolerant model versioning to overcome this problem. Conflicts are marked during the merge phase and are tolerated temporarily in order to resolve them later in a collaborative setting. We illustrate the proposed approach for the standardized modeling language UML and discuss how it can be integrated in current modeling tools and version control systems.

Keywords:
Astract: In our project BSopt we have developed a model-driven approach towards inter-organizational systems. During its evaluation phase we recognized that different partner networks operate similar, but still slightly differ in some details. However, our current approach is limited with respect to re-use of models or parts thereof for different partner networks. Thus, we plan to incorporate well established design techniques from reference modeling into our approach leading to inter-organizational reference models. We believe that inter-organizational reference models will speed up the development and will improve the quality of inter-organizational systems. In this position paper we outline our plans of integrating the design techniques of reference modeling into inter-organizational system development even if we do not provide a solution yet.

Keywords:
Astract: The urgent demand for optimistic version control support for software models induced active research within the modeling community. Recently, several approaches have been proposed addressing the task of detecting conflicts when merging two concurrently changed versions of a model. In this context, the holistic representation and supportive visualization of detected merge conflicts pose a challenge. In this paper, we present a modeling language independent conflict model comprising all necessary information to profoundly represent merge conflicts. From this conflict model, we leverage the dynamic extension power of UML profi les by introducing a dedicated conflict pro file to visually assist modelers in resolving merge conflicts of UML models. As a result, modelers may resolve conflicts in the concrete graphical syntax conducting their familiar UML editors without tool extensions.

Keywords:
Astract: A crucial prerequisite for the success of Model Driven Engineering (MDE) is the seamless exchange of models between diff erent modeling tools demanding for mappings between tool-specifi c metamodels. Thereby the resolution of heterogeneities between these tool-specifi c metamodels is a ubiquitous problem representing the key challenge. Nevertheless, there is no comprehensive classification of potential heterogeneities available in the domain of MDE. This hinders the specifi cation of a comprehensive benchmark explicating requirements wrt. expressivity of mapping tools, which provide reusable components for resolving these heterogeneities. Therefore, we propose a feature-based classifi cation of heterogeneities, which accordingly adapts and extends existing classifi cations. This feature-based classifi cation builds the basis for a mapping benchmark, thereby providing a comprehensive set of requirements concerning expressivity of dedicated mapping tools. In this paper a rst set of benchmark examples is presented by means of metamodels and conforming models acting as an evaluation suite for mapping tools.