Domänenübergreifende Simulation basierend auf BPMN und dem prozessgesteuerten Ansatz

Simulation tools are currently facing two significant challenges: On the one hand, common applications are often focussed on a specific domain, which leads to a high synchronisation and integration effort in the investigation of cross-domain issues. On the other hand, the transition from simulated models to operations monitoring and continuous improvement requires a high further development effort or even a completely new implementation with other technologies. This paper aims to present a novel one-size-fits-all approach based on the Business Process Model and Notation (BPMN) standard and the Process-Driven Approach (PDA) for creating and executing process models for discrete event simulation. It combines the BPMN’s potential to graphically represent any processes in arbitrary precision with those of PDA to sustainably integrate services, databases and tools via low-code. By means of two exemplary case studies, we would like to illustrate its practical implementation and potentials and challenge the scientific discourse

Data in Business Process Models. A Preliminary Empirical Study

Traditional activity-centric process modeling languages treat data as simple black boxes acting as input or output for activities. Many alternate and emerging process modeling paradigms, such as case handling and artifact-centric process modeling, give data a more central role. This is achieved by introducing lifecycles and states for data objects, which is beneficial when modeling data-or knowledge-intensive processes. We assume that traditional activity-centric process modeling languages lack the capabilities to adequately capture the complexity of such processes. To verify this assumption we conducted an online interview among BPM experts. The results not only allow us to identify various profiles of persons modeling business processes, but also the problems that exist in contemporary modeling languages w.r.t. The modeling of business data. Overall, this preliminary empirical study confirms the necessity of data-awareness in process modeling notations in general

Animation-Based Service Specification, Verification and Validation

[Context] With the expansion of services and service science, service systems have become an important abstraction for the service revolution. Service is defined as the application of resources (including competences, skills, and knowledge) to make changes that have value for another (system). The service system is a configuration of people, technologies, and other resources that interact with other service systems to create mutual value. Many systems can be viewed as service systems, including families, cities, and companies, among many others. Therefore, services became very important for unifying concepts from various disciplines. Service specifications are used to represent service systems on different levels of abstraction: from business down to IT. [Motivation and Problem] Traditionally, high-level service specifications are used only for communication among different participants, to catalyze the discussions between them; but only the specifications modeling IT systems have enough details to be simulated and executed. As a consequence, it becomes difficult to create precise high-level specifications and make sure that the implemented services are those that correspond to the business needs, potentially leading to severe project problems. Therefore, the challenge is to create abstract, yet precise service specifications, while keeping the relation between specifications at different levels of abstraction. [Idea and Results] In this work, we use formal methods and code generation techniques to create service-prototypes from service specifications at any level of abstraction, keeping the relations between different specifications. Stakeholders can try out the prototypes and give feedback regarding services that are being provided. This way, prototypes are used to validate the specifications and detect inconsistencies and unexpected behavior. [Contribution] The contributions of our work are threefold. First, we provide the visual formalism for service specification and simulation, by adding the necessary concepts to the existing method SEAM. Second, we define two design spirals: for service specification and for service validation and verification. The service specification spiral enables us to keep the relation between several service specifications. It includes steps with explicit design decisions on how to refine high-level specifications in order to include all the details necessary for providing the identified services. The validation and verification spiral is used to validate and verify specifications at any level of abstraction. Finally, it provides an environment that enables the simulation and prototyping of service specifications that are then used for their validation and verification. [Relevance] In addition to the theoretical contribution to the knowledge base of service design, we also provide the tools and guidelines that help business and IT analysts create and validate the service model, as confirmed by a survey conducted with practitioners. We illustrate the application of this work with a case study based on a consulting project we conducted at EPFL

A new paradigm for the continuous alignment of business and IT : combining enterprise architecture modelling and enterprise ontology

The paper deals with Next Generation Enterprise Information Systems in the context of Enterprise Engineering. The continuous alignment of business and IT in a rapidly changing environment is a grand challenge for today’s enterprises. The ability to react timeously to continuous and unexpected change is called agility and is an essential quality of the modern enterprise. Being agile has consequences for the engineering of enterprises and enterprise information systems. In this paper a new paradigm for next generation enterprise information systems is proposed, which shifts the development approach of model-driven engineering to continuous alignment of business and IT for the agile enterprise. It is based on a metamodelling approach, which supports both human-interpretable graphical enterprise architecture and machine-interpretable enterprise ontologies. Furthermore, next generation enterprise information systems are described, which embed modelling tools and algorithms for model analysis.http://www.elsevier.com/locate/compind2017-06-30hb201

A Model-driven Method to Design SoaML Services from BPMN Models: Principles, Proof-of-concept, and Validation

Today's business processes are increasingly complex as they cross organizational boundaries. To execute their business processes, organizations develop software applications called Process-Aware Information System (PAIS). PAIS designers must consider complex scenarios involving multiple partners. Consequently, the architectural design of high quality PAIS is complex and requires vast amounts of knowledge and skills both in software architecture and in the business domain. This paper proposes a model-driven method to design the architecture of PAIS using the service-oriented architecture (SOA) style. The proposed method generates SOA-based design models expressed in SoaML from the specifications of collaborative business processes expressed in BPMN. We developed a prototype tool using the Eclipse Modeling Framework (EMF) ecosystem. We tested the method on a set of processes from the Enterprise Resource Planning literature to assess its effectiveness. Our results show that 80.95\% of the identified services were relevant and corresponded to what architecture specialists expected

Automated Injection of Curated Knowledge Into Real-Time Clinical Systems: CDS Architecture for the 21st Century

abstract: Clinical Decision Support (CDS) is primarily associated with alerts, reminders, order entry, rule-based invocation, diagnostic aids, and on-demand information retrieval. While valuable, these foci have been in production use for decades, and do not provide a broader, interoperable means of plugging structured clinical knowledge into live electronic health record (EHR) ecosystems for purposes of orchestrating the user experiences of patients and clinicians. To date, the gap between knowledge representation and user-facing EHR integration has been considered an “implementation concern” requiring unscalable manual human efforts and governance coordination. Drafting a questionnaire engineered to meet the specifications of the HL7 CDS Knowledge Artifact specification, for example, carries no reasonable expectation that it may be imported and deployed into a live system without significant burdens. Dramatic reduction of the time and effort gap in the research and application cycle could be revolutionary. Doing so, however, requires both a floor-to-ceiling precoordination of functional boundaries in the knowledge management lifecycle, as well as formalization of the human processes by which this occurs. This research introduces ARTAKA: Architecture for Real-Time Application of Knowledge Artifacts, as a concrete floor-to-ceiling technological blueprint for both provider heath IT (HIT) and vendor organizations to incrementally introduce value into existing systems dynamically. This is made possible by service-ization of curated knowledge artifacts, then injected into a highly scalable backend infrastructure by automated orchestration through public marketplaces. Supplementary examples of client app integration are also provided. Compilation of knowledge into platform-specific form has been left flexible, in so far as implementations comply with ARTAKA’s Context Event Service (CES) communication and Health Services Platform (HSP) Marketplace service packaging standards. Towards the goal of interoperable human processes, ARTAKA’s treatment of knowledge artifacts as a specialized form of software allows knowledge engineers to operate as a type of software engineering practice. Thus, nearly a century of software development processes, tools, policies, and lessons offer immediate benefit: in some cases, with remarkable parity. Analyses of experimentation is provided with guidelines in how choice aspects of software development life cycles (SDLCs) apply to knowledge artifact development in an ARTAKA environment. Portions of this culminating document have been further initiated with Standards Developing Organizations (SDOs) intended to ultimately produce normative standards, as have active relationships with other bodies.Dissertation/ThesisDoctoral Dissertation Biomedical Informatics 201

A Methodological Framework for the Integrated Design of Decision-Intensive Care Pathways\u2014an Application to the Management of COPD Patients

Healthcare processes are by nature complex, mostly due to their multi-disciplinary character that requires continuous coordination between care providers. They encompass both organizational and clinical tasks, the latter ones driven by med- ical knowledge, which is inherently incomplete and distributed among people having different expertise and roles. Care pathways refer to planning and coordination of care processes related to specific groups of patients in a given setting. The goal in defining and following care pathways is to improve the quality of care in terms of patient satisfaction, costs reduction, and medical outcome. Thus, care pathways are a promising methodological tool for standardizing care and decision-making. Business process management techniques can successfully be used for representing organiza- tional aspects of care pathways in a standard, readable, and accessible way, while supporting process development, analysis, and re-engineering. In this paper, we intro- duce a methodological framework that fosters the integrated design, implementation, and enactment of care processes and related decisions, while considering proper rep- resentation and management of organizational and clinical information. We focus here and discuss in detail the design phase, which encompasses the simulation of care pathways. We show how business process model and notation (BPMN) and decision model and notation (DMN) can be combined for supporting intertwined aspects of decision-intensive care pathways. As a proof-of-concept, the proposed methodology has been applied to design care pathways related to chronic obstructive pulmonary disease (COPD) in the region of Veneto, in Italy