Keywords:
Astract: Wozu UML @ Classroom? . Für erste Einblicke in die Grundlagen der objektorientierten Modellierung. . Für einen raschen und erfolgreichen Einstieg in die Welt der UML. . Für einen verständlichen Überblick über die Konzepte von UML. . Für ein effektives und effizientes Erlernen der grafischen Notation und Regeln von UML. . Für das Kennenlernen der wichtigsten UMLDiagramme: Anwendungsfalldiagramm, Klassendiagramm, Zustandsdiagramm, Sequenzdiagramm und Aktivitätsdiagramm. . Für ein besseres Verständnis des Zusammenspiels der verschiedenen Diagramme. Profitieren Sie von jahrelanger Erfahrung mit der UML in Lehre und Forschung!

Keywords:
Astract: Model-Driven Engineering (MDE) places models as first-class artifacts throughout the software lifecycle. In this context, model transformations are crucial for the success of MDE, being comparable in role and importance to compilers for high-level programming languages. Thus, several model transformation approaches have been developed in the last decade, whereby originally most of them are based on the abstract syntax of modeling languages. However, this implementation specific focus makes it difficult for modelers to develop model transformations, because they are familiar with the concrete syntax but not with its computer internal representation. To tackle this problem, model transformation by-example approaches have been proposed which follow the same fundamental idea as query by-example and programming by-example approaches. Instead of using the computer internal representation of models, examples represented in concrete syntax are used to define transformations. Because different transformation scenarios occur in MDE, different by-example approaches have been developed. This chapter gives an overview on the emerging concepts, techniques, and approaches in this young by-example area.

Keywords:
Astract: Inter-organizational systems span from business models over business process models to their execution on top of a service-oriented architecture. In our project BSopt we have developed an integrated model-driven approach that addresses the different layers and builds up-on well-estabilshed languages on each of these layers. When applying our integrated methodology we recognized that models for the same business case are similar, but still varying for different business partner networks. Accordingly, a systematic approach to derive a model from another model, i.e., from a reference model, is needed. Significant achievements have been made by the reference modeling community in finding ways to leverage the potentials of model reuse in business process modeling. In this paper we outline the potentials of adapting design techniques known from reference modeling to the specific needs of inter-organizational system develpment even if we do not provide a solution yet.

Keywords:
Astract: Current optimistic model versioning systems, which are indispensable to coordinate the collaboration within teams, are able to detect several kinds of conflicts between two concurrently modified versions of one model. These systems support the detection of syntactical problems such as contradicting changes, violations of the underlying metamodel, and violations of OCL constraints. However, violations of the models' semantics remain unreported. In this paper, we suggest to use redundant information inherent in multi-view models to check if the semantics is violated during the merge process. In particular, we exploit the information encoded in state machine diagrams to validate evolving sequence diagrams by means of the model checker SPIN.

Keywords: