Keywords:
Astract: Optimistic version control systems enable globally distributed teams of developers to work together asynchronously. Every developer works on a local copy and consequently, no developer is ever detracted from working by waiting for a resource. The price for this flexibility is payed at the moment when conflicting modifications must be integrated into one consolidated version. In this paper, we discuss conflicts and their need for resolution in the context of model versioning and provide the basic concepts necessary to build a model versioning system which guides modelers through the critical consolidation phase by recommending suitable patterns.

Keywords:

Keywords:
Astract: In the development process of a B2B system, it is crucial that the business experts are able to express and evaluate agreements and commitments between the partners, and that the software engineers get all necessary information to bind the private process interfaces to the public ones. UN/CEFACT's modeling methodology (UMM) is a Unified Modeling Language (UML) profile for developing B2B processes. The formalisms introduced by UMM's stereotypes facilitate the communication with the software engineers. However, business experts-who usually have a very limited understanding of UML-prefer expressing their thoughts and evaluating the results by plain text descriptions. In this paper,we describe an approach that presents an equivalent of theUMMstereotypes and tagged values in text-based templates called worksheets. This strong alignment allows an integration into a UMM modeling tool and ensures consistency. We show how a specially designed XML-based worksheet definition language allows customization to special needs of certain business domains. Furthermore, we demonstrate how information kept in worksheets may be used for the semi-automatic generation of pattern-based UMM artifacts which are later transformed to web service definition language and business process execution language code.

Keywords:
Astract: Model integration is one of the core components for the realization of model-driven engineering. In particular, the seamless exchange of models among different modeling tools is of special importance. This exchange is achieved by the means of model transformations. However, the manual definition of model transformations is an error prone and cumbersome task. So matching techniques, originally intended for database schema integration, have been reused. The result is unsatisfactory as current matching approaches typically produce only one-toone alignments which are inappropriate for many integration problems. As a consequence, a detailed review and a manual post-processing step is often necessary. To tackle these problems, we propose the self-tuning framework SmartMatcher for improving automatically generated transformations. Our approach combines the power of an executable mapping language for bridging structural heterogeneities with the strength of an instance based quality evaluation model. In an iterative, feedback-driven process a mapping between two schemas is constructed and repeatedly enhanced.

Keywords:
Astract: This chapter concentrates on the modeling and analysis of enterprises that collaborate in a service oriented world. According to the idea of model-driven development, modeling of service-oriented enterprises collaborating in a networked configuration must address three different layers. The first layer is concerned with business models that describe the exchange of economic values among the business partners. An appropriate methodology on this level of abstraction is e3-value [1, 2]. The second layer addresses the inter-organizational business processes among business partners. The third layer addresses the businesses processes executed at each partner´s side, i.e., what each partner implements locally to contribute to the business collaboration.

Keywords:
Astract: The vision of Model-Driven Engineering places models as first-class artifacts throughout the software lifecycle. An essential prerequisite is the availability of proper transformation languages allowing not only code generation but also augmentation, migration or translation of models themselves. Current approaches, however, lack convenient facilities for debugging and ensuring the understanding of the transformation process. To tackle these problems, we propose a novel formalism for the development of model transformations which is based on Colored Petri Nets. This allows first, for an explicit, process-oriented execution model of a transformation, thereby overcoming the impedance mismatch between the specification and execution of model transformations, being the prerequisite for convenient debugging. Second, by providing a homogenous representation of all artifacts involved in a transformation, including metamodels, models and the actual transformation logic itself, understandability of model transformations is enhanced.

Keywords:
Astract: Realizing information exchange is a frequently recurring challenge in nearly every domain of computer science. Although languages, formalisms, and storage formats may differ in various engineering areas, the common task is bridging schema heterogeneities in order to transform their instances. Hence, a generic solution for realizing information exchange is needed. Conventional techniques often fail, because alignments found by matching tools cannot be executed automatically by transformation tools. In this paper we present the Smart Matching approach, a successful combination of matching techniques and transformation techniques, extended with self-tuning capabilities. With the Smart Matching approach, complete and correct executable mappings are found in a test-driven manner.

Keywords:
Astract: Predefined composite operations are handy for efficient modeling, e.g., for the automatic execution of refactorings, and for the introduction of patterns in existing models. Some modeling environments provide an initial set of basic refactoring operations, but hardly offer any extension points for the user. Even if extension points exist, the introduction of new composite operations requires programming skills and deep knowledge of the respective metamodel. In this paper, we introduce a method for specifying composite operations within the user´s modeling language and environment of choice. The user models the composite operation by-example, which enables the semi-automatic derivation of a generic composite operation specification. This specification may be used in various modeling scenarios, like model refactoring and model versioning. We implemented the approach in the Operation Recorder and performed an evaluation by defining multiple complex refactorings for UML diagrams.

Keywords:
Astract: The standardized QVT Relations language, one cornerstone of Model-Driven Architecture (MDA), has not yet gained widespread use in practice, not least due to missing tool support in general and inadequate debugging support in particular. Transformation engines interpreting QVT Relations operate on a low level of abstraction, hide the operational semantics of a transformation and scatter metamodels, models, QVT code, and traces across different artifacts. We propose a model-based debugger representing QVT Relations on bases of TROPIC, a model transformation framework which utilizes a variant of Colored Petri Nets (CPNs) providing an explicit runtime model and a homogenous view on all artifacts of a transformation.

Keywords:
Astract: The status of current model-driven engineering technologies has matured over the last years whereas the infrastructure supporting model management is still in its infancy. Infrastructural means include version control systems, which are successfully used for the management of textual artifacts like source code. Unfortunately, they are only limited suitable for models. Consequently, dedicated solutions emerge. These approaches are currently hard to compare, because no common quality measure has been established yet and no structured test cases are available. In this paper, we analyze the challenges coming along with merging different versions of one model and derive a first categorization of typical changes and the therefrom resulting conflicts. On this basis we create a set of test cases on which we apply state-of-the-art versioning systems and report our experiences.