Based on the increasing complexity of modern avionics, the associated system design processes moved towards Model Driven Architecture (MDA) based processes. Additionally, the demand for higher system autonomy features requires means to further modularise mission systems and to define and establish interactions among the systems’ individual components. Therefore, the ideas of service-oriented computing are currently adapted to established, model driven design processes. With respect to modelling interactions for service components, current approaches are limited to only a fixed set of communication primitives, restricting a service designer’s expressiveness to specify service interaction. In consequence, interaction patterns not included in this basic set have to be reflected in application code, mangling application and communication logic. Furthermore, when service functionality relies on communication semantics which are not provided by the underlying set of primitives, additional emulation behaviour has to be added to the service which makes this mangling even worse. Platform independence is reduced as services can not easily be ported to platforms not natively supporting the selected primitives which contradicts the ideas of model-driven development. Addressing these limitations, this thesis proposes a new model-driven service development process based on Interaction Templates (ITs), promoting interactions among service participants to first class modelling entities. The process focuses on modelling the interactions among service participants. Interaction semantics are explicitly specified in models, beyond pure stereotyping, and gain increased platform independence for services with respect to communication. The process exploits automated Model-to-Model (M2M) and Model-to-Text (M2T) transformations to assist service implementation and to automatically derive interaction realisations on concrete target platforms. This allows for easy replacement and inter-mixing of communication middleware to realise a service’s interactions. This way, services become independent of the underlying communication primitives by only relying on ITs and not platform primitives which are hidden behind ITs. In turn, realising ITs on concrete platforms is not affected by their utilisation for service interaction. Beside the novel modelling process itself, the presented work defines a Unified Modeling Language (UML) profile, referred to as UML Profile for Interaction-centric Services (UP4IS), which directly supports the adaptation of standard UML language constructs and tools for the proposed modelling approach. The whole development process is demonstrated via the specification of a simple video recording systems consisting of two services. The services themselves are based on a representative IT library which forms an essential part of the presented case study. Using these service and IT models, the thesis emphasises the necessary model transformation and code generation steps to derive service implementations based on the abstract models.

Universiẗat, Diss., 2006--Saarbrücken.

University (TH), Diss.--Karlsruhe, 2007. / Print on demand.

Zugl.: Basel, Univ., Diss., 2007

Zugl.: Ilmenau, Techn. Univ., Diss., 2008

Der wirtschaftliche Erfolg von Unternehmen wird heute von der Fähigkeit beeinflusst, die Geschäftsstrategie schneller umsetzen zu können als die Konkurrenz. Wichtige Ziele sind die Erschließung neuer Märkte, die Reduzierung von Kosten sowie die Steigerung der Effizienz. Eine Voraussetzung besteht darin, vorhandene Geschäftsprozesse flexibel anpassen und zügig neue Prozesse einführen zu können. Das bedingt wandlungsfähige und innovationsfördernde Systemlandschaften. An dieser Stelle setzen die durch Geschäftsprozesse getriebenen serviceorientierten Architekturen für ERP-Systeme an. Mit SOA-ERP-Systemen wird es möglich, selektiv und am Bedarf ausgerichtet neue Prozesse zu gestalten und das Prozess-Design mit der Einbindung von Lieferanten, Kunden und Partnern über Unternehmensgrenzen hinweg zu gestalten. SAP Enterprise-SOA bezeichnet die serviceorientierte ERP-Architektur der SAP AG. Die darauf basierenden Anwendungen entstehen – unter Einsatz der Enterprise-SOA Roadmap-Methodik – durch die gezielte Kombination von Plattform-, Ex-tension- und Composite-Applikationen. Letztere stellen hochflexible, aus Enterprise-Services/Services von Drittanbietern erstellte, Anwendungen dar. Deren Design durch SOA-Experten liegt ein hohes Maß an Erfahrungswissen zu Grunde. Dieses stellt den zentralen Aspekt der Speicherung und Wiederverwendung durch fallbasiertes Schließen dar. Im Gegensatz zum bestehenden Ansatz zur Beschreibung von Best-Practice Implementierungen im „SAP Community Network“ ermöglicht der hier dargestellte Vorschlag die strukturierte, prozessbezogene Speicherung sowie die ähnlichkeitsbasierte Wiederverwendung von Composite-Applikationen innerhalb des Roadmap-Prozesses. Schwerpunktmäßig werden dazu Indizes zum Aufbau von Zugriffsstrukturen in der Fallbasis sowie wie ein allgemeingültiges globales und ein beispielhaftes, kontextspezifisches lokales Indexvokabular erarbeitet. Weiterhin erfolgt die Angabe entsprechender Ähnlichkeitsmaße für die ausgeprägten Indizes sowie das Aufzeigen der Ähnlichkeitsbestimmung zwischen zwei Fällen durch einen Nearest-Neighbor Matching Algorithmus.

Based on the increasing complexity of modern avionics, the associated system design processes moved towards Model Driven Architecture (MDA) based processes. Additionally, the demand for higher system autonomy features requires means to further modularise mission systems and to define and establish interactions among the systems’ individual components. Therefore, the ideas of service-oriented computing are currently adapted to established, model driven design processes. With respect to modelling interactions for service components, current approaches are limited to only a fixed set of communication primitives, restricting a service designer’s expressiveness to specify service interaction. In consequence, interaction patterns not included in this basic set have to be reflected in application code, mangling application and communication logic. Furthermore, when service functionality relies on communication semantics which are not provided by the underlying set of primitives, additional emulation behaviour has to be added to the service which makes this mangling even worse. Platform independence is reduced as services can not easily be ported to platforms not natively supporting the selected primitives which contradicts the ideas of model-driven development. Addressing these limitations, this thesis proposes a new model-driven service development process based on Interaction Templates (ITs), promoting interactions among service participants to first class modelling entities. The process focuses on modelling the interactions among service participants. Interaction semantics are explicitly specified in models, beyond pure stereotyping, and gain increased platform independence for services with respect to communication. The process exploits automated Model-to-Model (M2M) and Model-to-Text (M2T) transformations to assist service implementation and to automatically derive interaction realisations on concrete target platforms. This allows for easy replacement and inter-mixing of communication middleware to realise a service’s interactions. This way, services become independent of the underlying communication primitives by only relying on ITs and not platform primitives which are hidden behind ITs. In turn, realising ITs on concrete platforms is not affected by their utilisation for service interaction. Beside the novel modelling process itself, the presented work defines a Unified Modeling Language (UML) profile, referred to as UML Profile for Interaction-centric Services (UP4IS), which directly supports the adaptation of standard UML language constructs and tools for the proposed modelling approach. The whole development process is demonstrated via the specification of a simple video recording systems consisting of two services. The services themselves are based on a representative IT library which forms an essential part of the presented case study. Using these service and IT models, the thesis emphasises the necessary model transformation and code generation steps to derive service implementations based on the abstract models.

Die Konzepte zur Erstellung von Software-Produktlinien dienen der ingenieurmäßigen, unternehmensinternen Wiederverwendung existierender Software-Artefakte. Existierende Ansätze nutzen von Hand erstellte und gewartete Kompositionsprogramme zum Assemblieren der Produkte entsprechend einer Variantenauswahl. Der Einsatz einer automatischen Planungskomponente sowie eines einfachen, erweiterbaren Komponenten-Meta-Modells hilft dabei, die dabei anfallenden Daten computergestützt zu verarbeiten. Die Integration beider Konzepte zu einem hybriden Ansatz ermöglicht die Neuerstellung von Produkten, die nicht von Anfang an als Produktlinie konzipiert sind, ohne eine spätere Umarbeitung unter Nutzung der automatischen Planungskomponente unnötig zu erschweren.

Die Konzepte zur Erstellung von Software-Produktlinien dienen der ingenieurmäßigen, unternehmensinternen Wiederverwendung existierender Software-Artefakte. Existierende Ansätze nutzen von Hand erstellte und gewartete Kompositionsprogramme zum Assemblieren der Produkte entsprechend einer Variantenauswahl. Der Einsatz einer automatischen Planungskomponente sowie eines einfachen, erweiterbaren Komponenten-Meta-Modells hilft dabei, die dabei anfallenden Daten computergestützt zu verarbeiten. Die Integration beider Konzepte zu einem hybriden Ansatz ermöglicht die Neuerstellung von Produkten, die nicht von Anfang an als Produktlinie konzipiert sind, ohne eine spätere Umarbeitung unter Nutzung der automatischen Planungskomponente unnötig zu erschweren.

Commissioning of a machine is still representing a very challenging operation and most steps are still executed manually by commissioning engineers. A future goal is to support the commissioning engineers and further automate the entire integration process of a newly installed system with a minimum of manual effort. This use case is known as plug-and-produce (PnP). In this contribution a concept of the Industrial Internet of Things is presented to improve the commissioning task for a pneumatic handling system. The system is based on a service-oriented architecture. Within this context, information models are developed to meet the requirements of PnP to provide relevant information via virtual representations, e.g. the asset administration shell, of the components to the commissioning process. Finally, a draft of the entire PnP process is shown, providing a general understanding of Industrial Internet of Things fluid power systems.