Keywords:
Astract: The urgent demand for optimistic version control support for software models induced active research within the modeling community. Recently, several approaches have been proposed addressing the task of detecting conflicts when merging two concurrently changed versions of a model. In this context, the holistic representation and supportive visualization of detected merge conflicts pose a challenge. In this paper, we present a modeling language independent conflict model comprising all necessary information to profoundly represent merge conflicts. From this conflict model, we leverage the dynamic extension power of UML profiles by introducing a dedicated conflict profile to visually assist modelers in resolving merge conflicts of UML models. As a result, modelers may resolve conflicts in the concrete graphical syntax conducting their familiar UML editors without tool extensions.

Keywords:
Astract: Conceptual languages to describe business models - not business process models - become increasingly important. One of the most expressive approaches towards business models is the Resource-Event-Agent (REA) ontology. REA has a substantial back-up in economic and accounting theory, but did lack a dedicated representation language for many years. Recently, we have introduced a domain specific modeling language including a REA meta model and a pertinent graphical notation. In this paper we build upon our previous work, but aim for a representation language that is able to serve as a serialization syntax also for other REA modeling approaches using UML class diagrams or OWL, etc. As a result we come up with REA-XML, an XML schema that allows a precise, tool-independent representation of REA models and that may also serve as an REA model exchange language between different tools.

Keywords:
Astract: One of the key challenges in the development of model transformations is the resolution of recurring semantic and syntactic heterogeneities. Thus, we provide a systematic classification of heterogeneities building upon a feature model that makes the interconnections between them explicit. On the basis of this classification, a set of benchmark examples was derived and used to evaluate current approaches to the specification of model transformations. We found, that approaches on the conceptual level lack expressivity whereas execution level approaches lack support for reuse. Moreover, only few of the approaches evaluated provide key features such as an automatic trace model or the ability to reuse specifications by inheritance.

Keywords:
Astract: Huge classes with more than 800 students pose a major challenge to lecturers as well as to students, especially when a practical part is included. In order to successfully master lectures of this size, novel kinds of teaching media provide a multitude of enhanced opportunities. In this paper, we present our experiences with the application of new media in our undergraduate course Introduction to Object-Oriented Modeling (OOM). In this course, we teach approximately 800-1000 students per year the principles and techniques of UML 2.0. New media, i.e., technologies other than the traditional blackboard presentation like a document camera, web-based self assessments, or lecture recordings, are applied to support both, students and lecturers when learning and teaching, respectively. We empirically underline the acceptance of our concept with the feedback of our students concerning the newly used technologies gained through an extensive survey.

Keywords:

Keywords:
Astract: In the discipline of accounting, the resource-event-agent (REA) ontology is a well accepted conceptual accounting framework to analyze the economic phenomena within and across enterprises. Accordingly, it seems to be appropriate to use REA in the requirements elicitation to develop an information architecture of accounting and enterprise information systems. However, REA has received comparatively less attention in the field of business informatics and computer science. Some of the reasons may be that the REA ontology despite of its well grounded core concepts is (1) sometimes vague in the definition of the relationships between these core concepts, (2) misses a precise language to describe the models, and (3) does not come with an easy to understand graphical notation. Accordingly, we have started developing a domain specific modeling language specifically dedicated to REA models and corresponding tool support to overcome these limitations. In this paper we present our REA DSL which supports the basic set of REA concepts.

Keywords:
Astract: The Resource-Event-Agent (REA) ontology has its roots in the accounting discipline and was originally developed as a reference framework to conceptualize economic phenomena in an enterprise. In its proposal in 1982, McCarthy already had the vision to facilitate the design of data structures of accounting information systems by means of REA. Since this time the REA model has been further extended and evolved into a domain ontology. All REA concepts are based on well established concepts of the literature in economic theory - which is certainly one of the strengths of REA. However, REA has no dedicated representation format and, consequently, no graphical syntax. Thus, users may struggle when describing the REA models leading to the impression that REA is a rather heavy-weight approach. A dedicated graphical syntax - such as it exists for e3-value - may help in overcoming this problem and may lead to a much more significant adoption of REA. Accordingly, we have started the endeavor of developing a domain specific modeling language for REA.

Keywords:

Keywords:
Astract: Standardized business documents are a prerequisite for successful information exchange in electronic business transactions. The United Nations Centre for Trade Facilitation and eBusiness (UN/CEFACT) provides a conceptual modeling approach, called Core Components, used by Business Partners (BPs) for defining business document models (BDMs). These BDMs are essential for defining service interfaces in service-oriented systems. However, in such a highly dynamic environment with ever-changing market demands, BPs are confronted with the need to revise their BDMs resulting in new versions of BDMs. Furthermore, BPs may dictate the use of new versions of BDMs. However, small- and medium-sized enterprises (SMEs) may not always adopt new BDM versions due to the cost and effort involved, inhibiting electronic information exchange. In this paper, we present a framework for dealing with interoperability issues in service-oriented systems through providing BPs with Business Document Interoperability as a Service. Having such a framework at hand provides SMEs with a low-cost and light-weight approach for dealing with evolving market requirements and hence evolving business documents. Furthermore, we present a prototypical implementation as well as an evaluation of the framework proposed.

Keywords:
Astract: Electronic Data Interchange (EDI) is based on the standardization of business document types. Usually, a standard business document type is defined in an all-embracing manner covering all elements needed in any business context, such as geopolitical context, industry context, and others. Before exchanging business documents in a particular business context, business partners have to agree on an implementation guide resulting in a subset of the standard document type. Different subsets of a standard document type may also be considered as variants of the standard document type. Since no agreed methodology for building variants of standard documents types exists, the domain of EDI may learn from Software Engineering. In fact, we are facing the need for managing variants which is typically addressed in Software Configuration Management. In this position paper, we propose utilizing concepts from Product Line Engineering (PLE) for managing variability in business document models. Therefore, we present the challenges encountered in managing variability in business documents. Furthermore, we provide a profound discussion why concepts from PLE are promising for managing business document variants.