Keywords:
Astract: The capability of UML profiles to serve as annotation mechanism has been recognized in both industry and research. Today's modeling tools offer profiles specific to platforms, such as Java, as they facilitate model-based engineering approaches. However, at the modeling level, the set of available profiles is considerably smaller compared to the number of existing Java libraries using annotations at the programming level. This is because an effective mapping between Java and UML to generate profiles from annotation-based libraries is missing. In this paper, we present JUMP to overcome this limitation, thereby continuing existing mapping efforts by emphasizing on annotations and profiles. We demonstrate the practical value of JUMP by contributing profiles that facilitate reverse-engineering and forward-engineering scenarios for the Java platform. The evaluation of JUMP shows that profiles can be automatically generated from Java libraries exhibiting equal or even improved quality compared to profiles currently used in practice.

Keywords:

Keywords:
Astract: Modeling and analyzing inter-organizational business processes (IOPs) is complicated substantially by heterogeneous process-modeling languages (e.g., surface vs. analysis languages) as well as by their inherent properties of loose coupling and local control (views). On top, multiple concerns must be addressed when modeling and analyzing IOPs, such as process data, behavior, distribution, and resource management. Whereas significant advances have been accomplished by the research community to model and analyze IOPs within the boundaries of a subset of these concerns, a holistic approach that enables a unified view across the strongly intermingled IOP concerns is missing. We believe that more research effort is needed towards establishing such a holistic, unified view based on a common language-oriented foundation for modeling and analyzing IOPs. This paper lays out one direction of language engineering towards this goal, collects generic and specific requirements on a language framework for inter-organizational business processes, and discusses them tentatively.

Keywords:

Keywords:
Astract: UML profiles support annotations at the modeling level. However, current modeling tools lack the capabilities to generate such annotations required for the programming level, which is desirable for reverse engineering and forward engineering scenarios. To overcome this shortcoming, we defined an effective conceptual mapping between Java annotations and UML profiles as a basis for implementing the JUMP tool. It automates the generation of profiles from annotation-based libraries and their application to generate profiled UML models. In this demonstration, we (i) compare our mapping with the different representational capabilities of current UML modeling tools, (ii) apply our tool to a model-based software modernization scenario, and (iii) evaluate its scalability with real-world libraries and applications.

Keywords:

Keywords:

Keywords:

Keywords:
Astract: Enterprise Resource Planning (ERP) systems are nowadays adapted to the company-specific requirements by customization. Whereas smaller and general feature changes are performed quickly by parameterization, changes of a company's business activities may lead to enormous changes in the system's code. To overcome this problem, we introduce an approach of a flexible ERP system which can be adapted by specific business models for each individual company/tenant by using model engineering techniques. Our approach REAlist is built on top of a generic data structure based on the Resource Event Agent (REA) business modeling ontology and provided as a cloud based service. Business models for each company are described by a domain specific language called the REA-DSL. REAlist enables companies to incorporate business activity changes quickly and without extensive code changes.

Keywords:
Astract: The implementation of a domain agnostic software system (such as an enterprise resource planning system or a trading information system) based on the REA model requires a generic, yet highly adaptable software architecture. Building on top of well established academic findings and proposals regarding the REA model we are proposing a software model building on two main concepts: fragments and declarations. Together they establish a single, exible, extendible class hierarchy implemented purely on a database layer. Fragments and declarations are implemented as associative arrays that are enriched with metadata, providing clear access to attributes and their meta information. The system's exibility is drastically increased by enabling the multi-typification of REA entities.