Keywords: Ruby, EMF Profiles, UML Profiles, Transformations
Astract: Model Engineering gets more important in software development because of the increasing use of models. At the same it is important the adapt and extend existing models. But this is sometimes not possible. For example the model was developed from somebody else or the model is used in another project and it is necessary to keep the compatibility. Therefore several lightweight extension mechanism have been developed. For example UML profile for UML diagrams or EMF profiles for standard diagrams of the Eclipse Modeling Framework (EMF). They allow to extend an already existing model without changing the original one. But unfortunately they have some drawbacks. Only a few transformation languages have a support for lightweight extensions and if they do only very basic. ATL can only access the profile with the underlying Java API. With RubyTL it is not possible to process profiles at all. This thesis covers the development of an extension which enables RubyTL to process EMF and UML profiles. Thereby should the extension be not integrated into the RubyTL code. This will be done with model processors. They integrate the profile into the existing model. Due to the circumstance that the profile is now a complete part of the diagram it is possible that the transformation language can access the stereotypes. Furthermore should it be possible to use the model processors for other transformation languages, like ATL. The goal is to enable the use of UML and EMF profiles also for other transformation languages. But they do not get integrated into the language. The model processors are used from a command line interface (CLI). The feasibility of the approach is demonstrated by using transformations to apply and read profile information in RubyTL and ATL. The resulting ATL transformations are also compared with ATL transformations using the basic ATL support based on the Java API for UML.

Keywords:
Astract: OPC Unified Architecture (UA) is a powerful and versatile platform for hosting information from a large variety of domains. In some cases, the domain-specific information models provide overlapping information, such as (i) different views on a specific entity or (ii) different levels of detail of a single entity. Emerging from a multi-disciplinary engineering process, these different views can stem from various tools that have been used to deal with that entity, or from different stages in an engineering process, e.g., from requirements engineering over system design and implementation to operations. In this work, we provide a small but expressive set of OPC UA reference types that unobtrusively allow the persistent instantiation of additional knowledge with respect to relations between OPC UA nodes. We will show the application of these reference types on the basis of a rendezvous of AutomationML and ISA-95 in an OPC UA server.

Keywords:
Astract: IEC 62264-2 and AutomationML can co-exist as separate views on the same production system, but there is some overlap with respect to the definitions of the entities in IEC 62264-2 and AutomationML. Therefore, a semantic alignment of entities as well as two methods for integration are proposed: (i) tagging AutomationML elements with IEC 622664-2 roles and (ii) referencing external IEC 62264-2 data.

Keywords:

Keywords: