Keywords:
Astract: In this paper, we report our experiences on teaching the Unifi ed Modeling Language in the large. More precisely, about 1000 computer science and business informatics students attend our course Object-Oriented Modeling each year. Requiring a profound understanding of the UML, many advanced courses like Software Engineering or Model Engineering build on the knowledge imparted by our course. In order to achieve our ambitious teaching targets, we establish personal mentoring despite the mass enhanced with e-learning facilities.

Keywords:
Astract: The development of complex software systems requires appropriate abstraction mechanisms in terms of model-driven engineering techniques (MDE) and proper support for allowing developers to work in parallel in terms of version control systems (VCSs). For realizing the vision of MDE, a bundle of standards has been made available recently, whereas the versioning of models has not gained the necessary attention yet, although being of paramount importance for the success of MDE in practice. In this paper, we propose a first vision of AMOR (Adaptable Model Versioning) to leverage version control in the area of MDE. The innovations of AMOR are threefold. Firstly, AMOR supports precise conflict detection, i.e., previously undetected as well as wrongly indicated conflicts shall be avoided. Secondly, AMOR focuses on intelligent conflict resolution by providing techniques for the representation of conflicting modifications as well as suggesting proper resolution strategies. Thirdly, AMOR targets an adaptable versioning framework, empowering modelers to flexibly balance between reasonable adaptation effort and proper versioning support while ensuring generic applicability to various domain-specific modeling languages and associated tools.

Keywords:

Keywords:
Astract: Model transformations are playing a vital role in the field of model engineering. However, for non-trivial transformation issues most approaches require imperative definitions, which are cumbersome and error-prone to create. Therefore, Model Transformation By Example (MTBE) approaches have been proposed as user-friendly alternative that simplifies the definition of model transformations. Up to now, MTBE approaches have been applied to structural models, only. In this work we apply MTBE to the domain of business process modeling languages, i.e., Event-driven Process Chains and UML activity diagrams. Compared to structural languages, business process modeling languages cover static semantic constraints, which are not specified in the metamodel. As a consequence, reasoning on the abstract syntax level is not sufficient. The contribution of this paper is to extend our existing MTBE approach by new alignment operators on the user level, which further improves the transparency of model transformation code. Concrete syntax and the knowledge about mapping operators are to be the only requisite artifacts.

Keywords:
Astract: Aspect-orientation provides a new way of modularization by clearly separating crosscutting concerns from non-crosscutting ones. While aspect-orientation originally has emerged at the programming level, it now stretches also over other development phases. There are, for example, already several proposals to Aspect-Oriented Modeling (AOM), most of them pursuing distinguished goals, providing different concepts as well as notations, and showing various levels of maturity. Consequently, there is an urgent need for both, academia and practice, to provide an in-depth survey, clearly identifying commonalities and differences between current AOM approaches. Existing surveys in this area focus more on comprehensibility with respect to development phases or evaluated approaches rather than on comparability at a fine-grained level. This paper tries to fill this gap. As a prerequisite for an in-depth evaluation, a conceptual reference model is presented, capturing the basic concepts of AOM and their interrelationships in terms of a UML class diagram. Based on this conceptual reference model, an evaluation framework has been designed by deriving a detailed and well-defined catalog of evaluation criteria. The actual evaluation by means of this criteria catalog and by employing a running example is done on the basis of a carefully selected set of eight AOM approaches, each of them having already reached a certain level of maturity. This per approach evaluation is complemented with an extensive report on lessons learned, summarizing the approaches´ strengths and shortcomings.