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.

Keywords:

Keywords:
Astract: Ontology and schema matching are well established techniques, which have been applied in various integration scenarios, e.g., web service composition and database integration. Consequently, matching tools enabling automatic matching of various kinds of schemas with various matching techniques are available. In the field of model-driven engineering, in contrast to schema and ontology integration, the in- tegration of modeling languages relies on manual tasks such as writing model trans- formation code, which is tedious and error-prone. Therefore, we propose the applica- tion of ontology and schema matching techniques for automatically exploring seman- tic correspondences between metamodels, which are currently the modeling language definitions of choice. The main focus of this paper is on reporting preliminary results and lessons learned by evaluating currently available ontology matching tools for their metamodel matching potential.

Keywords:
Astract: UN/CEFACT's modeling methodology (UMM) is a UML profile for modeling global B2B choreographies. The current UMM version comprises three main views for describing a computation independent model from a neutral perspective. Currently, the UMM version is missing a platform independent model showing how each partner has to realize the message exchanges to support the agreed choreography. In this paper we derive such a platform independent model from a UMM business transaction - a key artifact of the computation independent model. The resulting model is based on a state machine describing the local view of a participating business partner. This state machine unambiguously defines how a business partner has to react on incoming messages and on message expected but not received.

Keywords:
Astract: In business-to-business e-commerce, traditional electronic data interchange (EDI) approaches such as UN/EDIFACT have been superseded by approaches like web services and ebXML. Nevertheless, a precise and common semantic definition of business documents exchanged is needed. In order to become independent from a transfer syntax, we prefer defining the documents as platform independent models. An approach that follows this idea is the UN/CEFACT's core component standard. Core components are reusable semantic building blocks which can be combined in various ways to create shared libraries of interoperable business documents. In order to use standard UML modeling tools we have developed a UML profile for the core components standard. Furthermore, we adapt the UN/CEFACT naming and design rules for the UML profile in order to derive XML schemas for business document exchanges. The overall approach is demonstrated by using a specific example from the field of eCommerce.

Keywords:
Astract: Not least due to the widespread use of meta modeling concepts, model transformation techniques have reached a certain level of maturity (Czarnecki and Helsen, 2006). Nevertheless, defining transformations in some application areas in our case business process modeling is still a challenge because current transformation languages provide general solutions but do not support issues specific to a distinct area. We aim at providing generic solutions for model transformation problems distinct to the area of horizontal business process model transformations. As a first step in this endeavor, this work reports on the most pressing problems encountered at defining business process model transformations.

Keywords:
Astract: Due to company mergers, acquisition and business to business interoperability, there is a need for model transformations in the area of business process modeling to facilitate scenarios like model translation, integration and synchronization. Thus this paper concentrates on transformations of models between different business process modeling languages. As current transformation languages provide general solutions and do not support the special properties of business process models, it is still a challenge defining such transformations. To tackle this problem we introduce the model morphing approach. Our main idea is to create an integrated metamodel containing all concepts of the languages of a given domain. Based on this integration the model transformation can be defined in terms of morphing steps. Our approach is demonstrated by model transformation in the area of business process modeling but is generally suitable for domains in which a variety of languages is used that express similar concepts.

Keywords:
Astract: Current model-driven Web Engineering approaches (such as OO-H, UWE or WebML) provide a set of methods and supporting tools for a systematic design and development of Web applications. Each method addresses different concerns using separate models (content, navigation, presentation, business logic, etc.), and provide model compilers that produce most of the logic and Web pages of the application from these models. However, these proposals also have some limitations, especially for exchanging models or representing further modeling concerns, such as architectural styles, technology independence, or distribution. A possible solution to these issues is provided by making model-driven Web Engineering proposals interoperate, being able to complement each other, and to exchange models between the different tools. MDWEnet is a recent initiative started by a small group of researchers working on model-driven Web Engineering (MDWE). Its goal is to improve current practices and tools for the model-driven development of Web applications for better interoperability. The proposal is based on the strengths of current model-driven Web Engineering methods, and the existing experience and knowledge in the field. This paper presents the background, motivation, scope, and objectives of MDWEnet. Furthermore, it reports on the MDWEnet results and achievements so far, and its future plan of actions.

Keywords:
Astract: The definition of modeling languages is a key-prerequisite for model-driven engineering (MDE). In this respect, domain-specific languages (DSL) defined in terms of metamodels and UML profiles are often considered as two alternatives. For interoperability reasons, however, the need arises to bridge modeling languages originally defined as DSLs to UML profiles by defining (1) a specific UML profile to represent the domain-specific modeling concepts in UML and (2) model transformations for transforming DSL models to UML models and vice versa. A manual definition of a UML profile typically is a tedious and errorprone task, but contains a high potential for automation. The contribution of this paper is to integrate the so far competing worlds of DSLs and UML. We report on our semi-automatic approach based on the manual mapping of domain-specific metamodels and UML using a dedicated bridging language as well as the automatic generation of UML profiles and model transformations. We present our ideas within a case study for bridging ComputerAssociate´s DSL of the AllFusion Gen CASE tool with IBM´s Rational Software Modeler for UML.