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: 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.

Keywords:
Astract: The exchange of models among different modeling tools ever more becomes an important prerequisite for effective software development processes. Due to a lack of interoperability, however, it is often difficult to use tools in combination, thus the potential of model-driven software development cannot be fully exploited. This paper proposes ModelCVS, a system which enables tool integration through transparent transformation of models between different tools´ modeling languages expressed as MOF-based metamodels. ModelCVS provides versioning capabilities exploiting the rich syntax and semantics of models. Concurrent development is enabled by storing and versioning software artifacts that clients can access by a check-in/check-out mechanism, similar to a traditional CVS server. Semantic technologies in terms of ontologies are used together with a knowledge base to store machine- readable, tool integration relevant information, thus allowing to minimize repetitive effort and partly automate the integration process.