Methodical support for model-driven software engineering with enterprise models

A central research goal in information systems science is to achieve a close alignment between business processes, structures of organizations, and the functionality offered by enterprise information systems (EISs), which are used to support the work of organizations. Traditionally, there is a methodical gap between describing organizational incidents and software functionality, because organizations and software systems are understood and constructed with different terminology and on different levels of abstractions, typically also by differently educated groups of people. In enterprise models (EMs), dedicated modeling language elements are used to express knowledge about processes in organizations, e. g., about who is responsible for performing actions, what resources are involved, and what strategic goals are intended to be realized by organizational means. The work at hand shows, how EISs can be created based on this knowledge, which serve as supporting software for performing these tasks. Software development traditionally has to face a distinction between people who work with software, and people who create software. With the use of EMs, a chance opens up to closer involve the users of software systems into the process of developing and configuring the software. Building software from enterprise models is desirable, because once a dedicated relationship between enterprise models and software functionality has been established by a development method, involved users and responsible stakeholders can adapt the software according to their business needs, without having to deal with programming or technical details. This increases efficiency both in developing and operating the software, because software functionality is derived from requirements implicitly stated in EMs. Such a development procedure also promises to more efficiently adapt EIS to dynamic changes in organizations and their environment. Trust in the developed software system is also increased by involving users and responsible stakeholders into specifying the resulting software functionality. The following research work elaborates a software development method to create EISs from EMs. The method is designed as a generic framework to work with any enterprise modeling language, and to generate software for any target system platforms, after appropriate configuration. Fundamental challenges in methodically transforming conceptual models to implementation artifacts, are faced by involving auxiliary models into the software creation process, and splitting up the transformation procedure into multiple dedicated phases. Using this approach, the abstraction gap between conceptual enterprise models and technical implementation artifacts gets systematically bridged by introduced methodical concepts, in order to perform an ontological turn from the bird’s-eye-view description perspective of enterprise models, to an internal system perspective describing technical details of a software system. The elaborated method provides means for efficiently guiding modelers and software developers through the software engineering process. It can be configured at multiple points, to choose the degree of automation on a continuum between a manually supervised development process with methodically scheduled manual development steps, and a zero-coding 100% code generation approach. To clarify the theoretically introduced concepts, prototypical implementation examples are included in the present work. They demonstrate how to configure the method with model-transformations, validity checks, and domain-specific modeling languages, and serve as initial example cases for enterprise model driven software development using the Software Engineering with Enterprise Models (SEEM) method.Ein zentrales Forschungsziel der Wirtschaftsinformatik ist es, einen Abgleich zwischen den Geschäftsprozessen und Strukturen von Organisationen, und der Funktionalität von Unternehmensinformationssystemen (Enterprise Information Systems, EIS), zu erreichen, mit denen die Arbeit von Organisationen unterstützt wird. Traditionell besteht eine methodische Kluft zwischen der Beschreibung organisationaler Gegebenheiten und der Funktionalität von Software, denn Organisationen und Softwaresysteme werden mit verschiedener Terminologie und auf verschiedenen Abstraktionsebenen beschrieben und konstruiert, und dies typischerweise von verschieden ausgebildeten Personengruppen. In Unternehmensmodellen werden dedizierte Sprachmittel genutzt, um Wissen über Prozesse in Organisationen zu modellieren, zum Beispiel über handelnde und verantwortliche Akteure, eingesetzte Ressourcen, oder strategische Ziele, die durch organisatorische Mittel erreicht werden sollen. Die vorliegende Arbeit zeigt, wie basierend auf diesem Wissen EIS entwickelt werden können, die als unterstützende Software zur Ausführung dieser Aufgaben dienen. Softwareentwicklung sieht sich traditionell mit einer Trennung zwischen Personen, die mit Software arbeiten, und Personen, die Software erstellen, konfrontiert. Unter Nutzung von Unternehmensmodellen eröffnet sich eine Chance, Benutzer enger in den Prozess der Entwicklung und Konfiguration von Software einzubinden. Es ist wünschenswert, Unternehmensmodelle zur Softwareentwicklung methodisch heranzuziehen, denn sobald eine nachvollziehbare Beziehung zwischen Unternehmensmodellen und Software-Funktionalität mit Hilfe einer Entwicklungsmethode etabliert ist, können beteiligte Nutzer die Software selbst entsprechend ihrer Bedürfnisse mittels Unternehmensmodellierung anpassen, ohne mit Programmierung oder technischen Details umgehen zu müssen. Das erhöht die Effizienz sowohl bei der Entwicklung als auch Anwendung der Software, denn die Software-Funktionalität wird aus Anforderungen abgeleitet, die implizit in Unternehmensmodellen erfasst sind. Eine solche Entwicklungsmethode verspricht außerdem, EIS an dynamische Veränderungen in Organisationen und deren Umgebung effizienter und kostengünstiger anpassen zu können. Außerdem wird das Vertrauen in die entwickelte Software wird durch Einbeziehung von Nutzern in die Anforderungsspezifikaton gestärkt, wenn Anwender und Leitungsverantwortliche in der Lage sind, die Funktionalität der Software in eigener Verantwortung zu gestalten. Die nachfolgend dargestellten Forschungen erarbeiten eine Software-Entwicklungsmethode zur Erstellung von EIS aus Unternehmensmodellen. Die Methode ist als generischer Rahmen entworfen und kann prinzipiell mit jeder Unternehmensmodellierungssprache verwendet werden, und für jede Zielarchitektur Software erstellen, nach entsprechender Konfiguration. Grundsätzliche Herausforderungen, die sich beim methodischen Übergang von konzeptionellen Modellen zu Implementierungsartefakten stellen, werden durch die Einführung von ergänzenden Zusatzmodellen in den Software-Entwicklungsprozess, sowie die Aufteilung des Transformationsverfahrens in mehrere dedizierte Phasen, angegangen. Mit diesem Ansatz wird die Abstraktionslücke zwischen konzeptionellen Unternehmensmodellen und Implementierungsartefakten durch methodische Konzepte systematisch überbrückt, um die Beschreibungsperspektive von der Vogelperspektive der Unternehmensmodellierung hin zur internen Systemsicht auf Details eines Softwaresystems ontologisch zu drehen. Die erarbeitete Methode erlaubt es, Software-Architekten und -Entwickler effizient durch den Entwicklungsprozess zu leiten. Sie kann an verschiedenen Stellen konfiguriert werden, um den Automationsgrad auf einem Kontinuum zwischen einem manuell beaufsichtigten Entwicklungsprozess mit methodisch vorgesehenen manuellen Entwicklungsschritten, oder einem “zero-coding” Entwicklungsansatz mit 100% Code-Generierung, auszuwählen. Zur Veranschaulichung der theoretisch eingeführten Konzepte enthält die vorliegende Arbeit prototypische Implementierungsbeispiele. Sie demonstrieren die Konfiguration der Methode mit Modelltransformationen, Modellvalidierungen und domänenspezifischen Modellierungssprachen, und dienen als erste Anwendungsbeispiele für Unternehmensmodellgetriebenen Softwareentwicklung mit der Software Engineering with Enterprise Models (SEEM) Methode

Exploring Maintainability Assurance Research for Service- and Microservice-Based Systems: Directions and Differences

To ensure sustainable software maintenance and evolution, a diverse set of activities and concepts like metrics, change impact analysis, or antipattern detection can be used. Special maintainability assurance techniques have been proposed for service- and microservice-based systems, but it is difficult to get a comprehensive overview of this publication landscape. We therefore conducted a systematic literature review (SLR) to collect and categorize maintainability assurance approaches for service-oriented architecture (SOA) and microservices. Our search strategy led to the selection of 223 primary studies from 2007 to 2018 which we categorized with a threefold taxonomy: a) architectural (SOA, microservices, both), b) methodical (method or contribution of the study), and c) thematic (maintainability assurance subfield). We discuss the distribution among these categories and present different research directions as well as exemplary studies per thematic category. The primary finding of our SLR is that, while very few approaches have been suggested for microservices so far (24 of 223, ?11%), we identified several thematic categories where existing SOA techniques could be adapted for the maintainability assurance of microservices

Model-driven Enterprise Systems Configuration

Enterprise Systems potentially lead to significant efficiency gains but require a well-conducted configuration process. A promising idea to manage and simplify the configuration process is based on the premise of using reference models for this task. Our paper continues along this idea and delivers a two-fold contribution: first, we present a generic process for the task of model-driven Enterprise Systems configuration including the steps of (a) Specification of configurable reference models, (b) Configuration of configurable reference models, (c) Transformation of configured reference models to regular build time models, (d) Deployment of the generated build time models, (e) Controlling of implementation models to provide input to the configuration, and (f) Consolidation of implementation models to provide input to reference model specification. We discuss inputs and outputs as well as the involvement of different roles and validation mechanisms. Second, we present an instantiation case of this generic process for Enterprise Systems configuration based on Configurable EPCs

Unified Enterprise Knowledge Representation with Conceptual Models - Capturing Corporate Language in Naming Conventions

Conceptual modeling is an established instrument in the knowledge engineering process. However, a precondition for the usability of conceptual models is not only their syntactic correctness but also their semantic comparability. Assuring comparability is quite challenging especially when models are developed by different persons. Empirical studies show that such models can vary heavily, especially in model element naming, even if they are meant to express the same issue. In contrast to most ontology-driven approaches proposing the resolution of these differences ex-post, we introduce an approach that avoids naming differences in conceptual models already during modeling. Therefore we formalize naming conventions combining domain thesauri and phrase structures based on a linguistic grammar. This allows for guiding modelers automatically during the modeling process using standardized labels for model elements, thus assuring unified enterprise knowledge representation. Our approach is generic, making it applicable for any modeling language

Extensibility of Enterprise Modelling Languages

Die Arbeit adressiert insgesamt drei Forschungsschwerpunkte. Der erste Schwerpunkt setzt sich mit zu entwickelnden BPMN-Erweiterungen auseinander und stellt deren methodische Implikationen im Rahmen der bestehenden Sprachstandards dar. Dies umfasst zum einen ganz konkrete Spracherweiterungen wie z. B. BPMN4CP, eine BPMN-Erweiterung zur multi-perspektivischen Modellierung von klinischen Behandlungspfaden. Zum anderen betrifft dieser Teil auch modellierungsmethodische Konsequenzen, um parallel sowohl die zugrunde liegende Sprache (d. h. das BPMN-Metamodell) als auch die Methode zur Erweiterungsentwicklung zu verbessern und somit den festgestellten Unzulänglichkeiten zu begegnen. Der zweite Schwerpunkt adressiert die Untersuchung von sprachunabhängigen Fragen der Erweiterbarkeit, welche sich entweder während der Bearbeitung des ersten Teils ergeben haben oder aus dessen Ergebnissen induktiv geschlossen wurden. Der Forschungsschwerpunkt fokussiert dabei insbesondere eine Konsolidierung bestehender Terminologien, die Beschreibung generisch anwendbarer Erweiterungsmechanismen sowie die nutzerorientierte Analyse eines potentiellen Erweiterungsbedarfs. Dieser Teil bereitet somit die Entwicklung einer generischen Erweiterungsmethode grundlegend vor. Hierzu zählt auch die fundamentale Auseinandersetzung mit Unternehmensmodellierungssprachen generell, da nur eine ganzheitliche, widerspruchsfreie und integrierte Sprachdefinition Erweiterungen überhaupt ermöglichen und gelingen lassen kann. Dies betrifft beispielsweise die Spezifikation der intendierten Semantik einer Sprache

Competences of IT Architects

The field of architecture in the digital world uses a plethora of terms to refer to different kinds of architects, and recognises a confusing variety of competences that these architects are required to have. Different service providers use different terms for similar architects and even if they use the same term, they may mean something different. This makes it hard for customers to know what competences an architect can be expected to have.\ud \ud This book combines competence profiles of the NGI Platform for IT Professionals, The Open Group Architecture Framework (TOGAF), as well as a number of Dutch IT service providers in a comprehensive framework. Using this framework, the book shows that notwithstanding a large variety in terminology, there is convergence towards a common set of competence profiles. In other words, when looking beyond terminological differences by using the framework, one sees that organizations recognize similar types of architects, and that similar architects in different organisations have similar competence profiles. The framework presented in this book thus provides an instrument to position architecture services as offered by IT service providers and as used by their customers.\ud \ud The framework and the competence profiles presented in this book are the main results of the special interest group “Professionalisation” of the Netherlands Architecture Forum for the Digital World (NAF). Members of this group, as well as students of the universities of Twente and Nijmegen have contributed to the research on which this book is based

Integrated Clinical Pathways: A Model-based Holistic Method

Against the background of increasing multidisciplinarity as well as the focus on quality, transparency and economic efficiency of medical services, clinical pathways (CPs) have been established as a promising tool at the organizational level in recent years. They are primarily intended to ensure an adequate description of the care processes and to manage the balance between best treatment practice and economic viability. CPs standardize the internal care services by explicating the institution-specific knowledge with regard to recommendations for action, service portfolio, organizational structures, infrastructure, etc. of a specific service provider. The development of hospital information systems (HIS) has so far been characterized by an evolutionary development of modules in the field of laboratory, radiology, nursing and picture archiving systems as well as in the area of administrative systems. As one result of this development, the HIS usually comprises a heterogeneous network of software systems of different types and manufacturers. However, the actual control of patients by means of evidence-based processes and integration of CPs into HIS was not addressed until the recent years, when HIS manufacturers started developing modules for CP modeling and workflow support. The objective of this thesis is to provide a holistic methodical support for the description of clinical pathways and their integration into a hospital information system to finally improve the compliance of daily care to standard process definitions. Therefore, conceptual models provide an adequate mean to describe and communicate complex matters in a comprehensible form as well as to configure IT systems due to their semi-formal nature. Hence, a first research thread investigates the question, how clinical pathways can be described adequately using conceptual models. This results in an iterative design of adequate modeling languages for clinical pathways. A second research thread further investigates the question, how conceptual models of clinical pathways can be used to configure process-oriented application systems in health care. This thread therefore describes the design of a model-based method, that enables a consecutive transformation of CPs into technical (workflow) specifications, based on the principles of the Model-Driven Architecture.:A. Synopsis of the Doctoral Dissertation B. Agility in Medical Treatment Processes C. Domain Specific Modeling Language - CPmod D. BPMN4CP - Version 1.0 E. BPMN4CP - Version 2.0 F. BPMN4CP - Version 2.1 G. MDA in Health Care IS Development H. Transforming Clinical Pathways into Care Workflows I. CDA Templates - Utilizing the MediCUB

Design and Evaluation of Domain-Specific Platforms and the Special Case of Digital Healthcare

The implementation of digital innovations in the healthcare sector is faced with different barriers and challenges. The complex system of regulations, the lack of interoperability, and highly dynamic interorganisational networks lead to missing widespread adoption of eHealth solutions. Digital platforms can help to overcome these barriers by providing a holistic infrastructure. They create a modularised foundation that innovators can use to create own innovations and provide them to demanders of digital solutions. As intermediaries, they can be accessed both by healthcare professionals and eHealth solution providers. Providers can offer their eHealth services via the platform. Healthcare professionals can use these services to create own interorganisational information systems. In the field of information systems research, effects and strategies for two-sided platforms are well researched and the potentials of eHealth platforms are also discussed. However, the organisational and technological design and methods for the construction of platforms are fewer questioned. Nonetheless, platform owners can benefit from implementation strategies and architectural guidance to create sustainable platforms and surrounding ecosystems. This doctoral thesis questions how domain-specific platforms can be designed systematically. Conducting a design-science research process, it develops both a modelling system and the Dresden Ecosystem Management Method (DREEM) to support the development of platforms in different domains. Furthermore, it describes the design characteristics of two-sided platforms in the healthcare sector and provides an evaluation approach to analyse the platforms’ ability to create a viable innovation ecosystem in the healthcare sector. The doctoral thesis contributes by providing methodical guidance for platform owners and researchers to design and evaluate digital platforms in different domains and improves the understanding of platform theory in the healthcare sector.:A. Synopsis of the Doctoral Thesis 1. Introduction 2. Foundational Considerations 3. Requirements for Design Artefacts and Knowledge 4. Structure of the Doctoral Thesis 5. Conclusion B. Paper 1 - Governance Guidelines for Digital Healthcare Ecosystems C. Paper 2 - Revise your eHealth Platform! D. Paper 3 - Business Model Open ”E-Health-Platform” E. Paper 4 - Modelling Ecosystems in Information Systems F. Paper 5 - Designing Industrial Symbiosis Platforms G. Paper 6 - Management of Digital Ecosystems with DREEM H. Paper 7 - Guiding the Development of Digital Ecosystems I. Paper 8 - Towards Maintenance Analytics Ecosystems J. Paper 9- Sustainability of E-Health-Projects K. Paper 10 - ISO 11354-2 for the Evaluation of eHealth-Platform