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.

Keywords:
Astract: Service-oriented architectures (SOA) aim at the alignment of business and IT by having a clear business process-centric focus. In order to reach that goal, real-world business processes are captured by business process models. These models serve as the basis for the declarative configuration of a SOA using appropriate deployment artifacts - i.e., XML-based process languages. Consequently, requirements engineering for SOAs must focus on business processes and on their integration into systems using interoperable services, which is not the case for most conventional requirements engineering approaches. In this paper we present a requirements engineering approach specifically designed for the engineering of SOAs. Requirements are captured using a unified process, based on phases and iterations eventually leading to a formalized and unambiguous requirements specification. The final requirements specification can be used in succeeding development phases - i.e. for the model-driven generation of deployment artifacts for SOAs. The presented solution is called [vem:xi:] and is successfully used in the IT department of a Mobile Network Operator (MNO) in Austria. In the highly volatile world of mobile communication the presented approach enables faster application development and faster integration of solutions, thus leading to a competitive advantage over other market participants.

Keywords:
Astract: In the field of business document standardization a multitude of different standardization efforts exist. Unfortunately, most of the developed standards are designed for a specific application domain or industry and do not consider cross-standard interoperability. This results in several incompatible standard definitions. Without the provision of a common semantical basis for business document definitions, cross-domain interoperability cannot be achieved. In this paper we provide a methodology for building a global reference ontology based on the Core Components Technical Specification (CCTS) and Web Ontology Language (OWL). Using our approach a common semantic business document basis is developed. New document definitions may be derived from this basis and existing document definitions may be aligned to it. Using our 'derivation-by-restriction' mechanism, instances derived from a common semantical basis are interoperable to each other. Thus, mapping mechanisms between different standard definitions may be implemented in an easier and semantically correct manner.

Keywords:
Astract: Traditionally, models are considered as pretty pictures supporting merely the documentation of a software development project. With the rise of model-driven engineering (MDE) this viewpoint has to be reconsidered. Models become first-class artifacts which yield the basis for the generation of executable program code. In modern university curricula of computer science and related fields this paradigm shift must not be ignored. At the Business Informatics Group (BIG) of the Vienna University of Technology we offer an advanced modeling course called Model Engineering where we elaborate current trends, development, and state-of-the-art techniques necessary to realize the visions of MDE. In this paper we report which concrete concepts and approaches we teach and how we structure and organize a practical hands-on lab where the students have to build their own model-driven development environment consisting of their own modeling languages, certain types of model transformations, and code generation facilities.

Keywords:
Astract: Approximately 1000 students of computer science and business informatics attend the course Introduction to Object- Oriented Modeling (OOM) offered by the Business Informatics Group (BIG) of the Vienna University of Technology each year in order to learn the basic concepts of the Unified Modeling Language (UML) and to obtain a certificate. For finishing the course successfully, the students must pass three small tests where they have to prove their theoretical knowledge about UML concepts as well as their ability to apply this knowledge in practical exercises. In this paper we report our experiences in assessing the modeling knowledge of our students and we reveal how we design the tests.

Keywords:
Astract: Business documents exchanged in a service-oriented context play a crucial role in the definition of service interfaces. Only if both partners have a common agreement on the data exchanged, automated business interactions are possible. The United Nations Center for Trade Facilitation and Electronic Business (UN/CEFACT) provides a reliable and interoperable solution for conceptual business document definitions with UN/CEFACT's Core Components Technical Specification. However, document definitions aren't available in a centralized manner to all interested business partners. In order to allow for an easy search and retrieval of core component business document definitions, a registry is needed. Business partners may retrieve service interface definitions from the registry and adapt their software accordingly in order to engage in automated business interactions. We specify a registry meta model on top of ebRIM, registering core component artifacts and defining their inter-dependencies.

Keywords:
Astract: The electronic exchange of business documents is an often communicated desire by enterprises and the public sector. Electronic business is currently mainly hindered by unresolved interoperability issues and a lack of tool support. Additionally, computer aided document exchange is cost intensive at the beginning and thus discourages small and medium-sized companies to adapt to new technologies. The contribution of this paper is to present suitable tool support and methods to manage the complexity of business document integration. Our modeling tool is based on UN/CEFACT's (United Nations Centre for Trade Facilitation and Electronic Business) Core Components Technical Specification allowing for platform independent, conceptual business document models. On these models further integration operations can be performed.