Yet Another Event-driven Process Chain - Modelling Workflow Patterns with yEPCs

The 20 workflow patterns proposed by van der Aalst et al. provide a comprehensive benchmark for comparing process modelling languages. In this article, we discuss workflow pattern support of Event-Driven Process Chains (EPCs). Building on this analysis, we propose three extensions to EPCs in order to provide for workflow pattern support. These are the introduction of the so-called empty connector; inclusion of multiple instantiation concepts; and a cancellation construct. As both the latter are inspired by YAWL, we refer to this new class of EPCs as Yet Another Event-driven Process Chain (yEPC). Furthermore, we sketch how a transformation to YAWL can be used to specify the semantics of yEPCs

A transformation of business process models into software-executable models using MDA

Traditional software development projects for process-oriented organizations are time consuming and do not always guarantee the fulfillment of the functional requirements of the client organization, and thus the quality of the resulting software product. To reduce the time spent for developing software and improve its quality, we adopt the inclusion of automation in some parts of the software development process. Thus, in this paper, we propose a model transformation approach to derive an executable model for the business processes of a given organization. We execute a mapping between processes (described with a business process execution language) and software components. We also propose a supporting software architecture based on an Enterprise Service Bus and on Java Business Integration, and we use an already defined methodology to execute the model transformation project.FEDER, FC

On the relevance of design knowledge for design-oriented business and information systems engineering : supplemental considerations and further application examples

This contribution represents a supplement to the article "On the Relevance of Design Knowledge for Design-Oriented Business and Information Systems Engineering — Conceptual Foundations, Application Example, and Implications" in the special issue on Science of Business and Information Systems Engineering of the journal Business and Information Systems Engineering (BISE) in 2010. It contains further application examples concerning the introduced reference framework for systemizing design knowledge. Besides the comprehensive documentation of design knowledge concerning eventdriven process chains (EPC) with the dedicated literary sources and an evaluation of the evidence of the provided statements, in this report the framework is furthermore applied for the documentation of design knowledge about the Process Grammar Approach, another technique for process design presented by Lee et al. in MIS Quarterly in 2008. Subsequently the results are discussed.Der vorliegende Beitrag dient als Anhang zum Artikel "On the Relevance of Design Knowledge for Design-Oriented Business and Information Systems Engineering — Conceptual Foundations, Application Example, and Implications", der in der Zeitschrift Business and Information Systems Engineering (BISE) zum Schwerpunktheft "Science of Business and Information Systems Engineering" im Jahr 2010 erschienen ist. Er ergänzt das dort aufgeführte Beispiel zur Anwendung des Bezugsrahmens zur Dokumentation von Gestaltungswissen. Der Bezugsrahmen wurde verwendet, um Gestaltungswissen zur Modellierungstechnik "Ereignisgesteuerte Prozesskette" (EPK) zu systematisieren, zu explizieren und hinsichtlich seiner Evidenz zu bewerten. Die dort gegebene Übersicht wird im vorliegenden Beitrag ergänzt. Darüber hinaus findet sich in diesem IWi-Heft ein weiteres Anwendungsbeispiel, das aufgrund von Platzrestriktionen im Journalartikel nicht präsentiert werden konnte. Der Bezugsrahmen dient hier der Systematisierung und Dokumentation von Gestaltungswissen zur Technik des Process Grammar Approach, der von Lee et al. 2008 im Journal MIS Quarterly präsentiert wurde. Weiterhin werden die erhobenen Ergebnisse im vorliegenden Beitrag diskutiert

A quantitative analysis of faulty EPCs in the SAP reference model

The SAP reference model contains more than 600 non-trivial process models expressed in terms of Event-driven Process Chains (EPCs). We have automatically translated these EPCs into YAWL models and analyzed these models usingWofYAWL, a veri¯cation tool based on Petri nets. We discovered that at least 34 of these EPCs contain errors (i.e., at least 5.6% is °awed). We analyzed which parts of the SAP reference model contain most errors. Moreover, based on 15 characteristics (e.g., the size of the model), we used logistic regression to ¯nd possible pre- dictors for these errors. This systematic analysis of the SAP reference model illustrates the need for veri¯cation tools such as WofYAWL

On the relevance of design knowledge for design-oriented business and information systems engineering : supplemental considerations and further application examples

This contribution represents a supplement to the article "On the Relevance of Design Knowledge for Design-Oriented Business and Information Systems Engineering — Conceptual Foundations, Application Example, and Implications" in the special issue on Science of Business and Information Systems Engineering of the journal Business and Information Systems Engineering (BISE) in 2010. It contains further application examples concerning the introduced reference framework for systemizing design knowledge. Besides the comprehensive documentation of design knowledge concerning eventdriven process chains (EPC) with the dedicated literary sources and an evaluation of the evidence of the provided statements, in this report the framework is furthermore applied for the documentation of design knowledge about the Process Grammar Approach, another technique for process design presented by Lee et al. in MIS Quarterly in 2008. Subsequently the results are discussed.Der vorliegende Beitrag dient als Anhang zum Artikel "On the Relevance of Design Knowledge for Design-Oriented Business and Information Systems Engineering — Conceptual Foundations, Application Example, and Implications", der in der Zeitschrift Business and Information Systems Engineering (BISE) zum Schwerpunktheft "Science of Business and Information Systems Engineering" im Jahr 2010 erschienen ist. Er ergänzt das dort aufgeführte Beispiel zur Anwendung des Bezugsrahmens zur Dokumentation von Gestaltungswissen. Der Bezugsrahmen wurde verwendet, um Gestaltungswissen zur Modellierungstechnik "Ereignisgesteuerte Prozesskette" (EPK) zu systematisieren, zu explizieren und hinsichtlich seiner Evidenz zu bewerten. Die dort gegebene Übersicht wird im vorliegenden Beitrag ergänzt. Darüber hinaus findet sich in diesem IWi-Heft ein weiteres Anwendungsbeispiel, das aufgrund von Platzrestriktionen im Journalartikel nicht präsentiert werden konnte. Der Bezugsrahmen dient hier der Systematisierung und Dokumentation von Gestaltungswissen zur Technik des Process Grammar Approach, der von Lee et al. 2008 im Journal MIS Quarterly präsentiert wurde. Weiterhin werden die erhobenen Ergebnisse im vorliegenden Beitrag diskutiert

Musterbasierte Kontrollflusssemantik für Geschäftsprozessmodellierungssprachen

Die Bedeutung einzelner Symbole ist bei Geschäftsprozessmodellierungssprachen häufig nicht eindeutig festgelegt, wodurch Missverständnisse zwischen Domänenexperten und Modellierern gefördert werden. In dieser Arbeit wird eine auf Kontrollflussmustern basierende Methode zur Beschreibung der Kontrollflusssemantik von graphischen Geschäftsprozessmodellierungssprachen vorgestellt. Darüber hinaus werden die effiziente Anwendbarkeit und grundsätzliche Nützlichkeit der Methode aufgezeigt

MINERVA : Model drIveN and sErvice oRiented framework for the continuous improVement of business process & relAted tools

Organizations are facing several challenges nowadays, one of the most important ones being their ability to react quickly to changes either to their business process (BP) models or to the software implementing them. These changes can come from different sources: external requirements from partners or the market, or new internal requirements for the way that things are carried out by the defined BPs; they may also arise from improvement opportunities detected for the BPs defined, based on BPs execution monitoring and execution evaluation that is done by the organization, and/or its partners and customers. The increasing complexity of both BPs models and the software implementing them, requires the changes needed or the improvements to be carefully weighed against the impact their introduction will have; they ought also to be carried out in a systematic way to assure a successful development. Two key elements are to provide these requirements: the separation of BPs definition from their implementation to minimize the impact of changes in one to the other, and a process to introduce the changes or improvements in the existing BPs and/or software implementing them. Business Process Management (BPM) provides the means for guiding and supporting the modeling, implementation, deployment, execution and evaluation of BPs in an organization, based on the BP lifecycle. The realization of BPs by means of services provides the basis for separating their definition from the technologies implementing them and helps provide a better response to changes in either of the layers defined -definition and implementation of business processes- with minimum impact on the other. Modeling of both BP and services is a key aspect to support this vision, helping provide traceability between elements from one area to the other, so easing the analysis of the impact of changes, among other things. Models have proven to play an important role in the software development process, one of its key uses in the context of BP realization by means of services is that of designing services at a more abstract level than with specific technologies, also promoting reuse by separating services logic from its implementation. MINERVA: Model drIveN & sErvice oRiented framework for the continuous business process improVement & relAted tools is the framework that has been defined in this thesis work; it takes into account all the aspects mentioned, in which the SOC and MDD paradigms are applied to BPs focusing on their continuous improvement, extending an existing BP lifecycle with explicit execution measurement and improvement activities and elements. It is made up of three dimensions: i) conceptual, which defines the concepts that are managed throughout the framework. ii) methodological, which defines a methodology for service oriented development from BPs with automatic generation of SoaML service models from BPMN2 models, along with a continuous improvement process based on execution measurement of the occurrences of BPs in the organization to carry out the improvement effort. iii) tools support for the whole proposal based on several existing tools we have integrated, along with new ones we have developed. The proposals in MINERVA have been validated by means of an experiment and two case studies carried out in the context of real projects in two organizations, from which, as the main result of the applications performed, it can be concluded that MINERVA can be a useful and key guide for the continuous improvement of BPs realized by services and for the development of service oriented systems from BPs, with automatic generation of service models from BP models.Las organizaciones se enfrentan en la actualidad a varios retos, siendo uno de los más importantes su capacidad para reaccionar rápidamente a los cambios ya sea en sus modelos de procesos de negocio (PN) o en el software que los implementa. Estos cambios pueden provenir de distintas fuentes: requisitos externos de socios o del mercado, o nuevos requisitos internos para la forma en que las cosas se llevan a cabo por los PNs definidos; también pueden surgir de las oportunidades de mejora detectadas para los PNs definidos, en base al monitoreo y evaluación de la ejecución de los PNs llevada a cabo por la organización, y/o sus socios y clientes. La creciente complejidad de los modelos de PNs y del software que los implementa, requiere que los cambios o las mejoras sean sopesados cuidadosamente contra el impacto que su introducción tendrá; también deben llevarse a cabo de manera sistemática para asegurar un desarrollo exitoso. Dos elementos son clave para proveer estos requisitos: la separación de la definición de los PNs de su implementación, para minimizar el impacto de los cambios de uno en otro, y un proceso para introducir los cambios o mejoras en los PNs y/o en el software que los implementa. La Gestión de Procesos de Negocio (Business Process Management, BPM) proporciona los medios para guiar y apoyar el modelado, implementación, despliegue, ejecución y evaluación de PNs en una organización, basado en el ciclo de vida de PNs. La realización de PNs con servicios proporciona la base para la separación de su definición de las tecnologías para implementarlos, y ayuda a proporcionar una mejor respuesta a los cambios en cualquiera de las capas definidas -definición e implementación de procesos de negocio- con un impacto mínimo sobre la otra. El modelado de PNs y servicios es un aspecto clave para apoyar esta visión, ayudando a proveer trazabilidad entre los elementos de un área a la otra, por lo tanto facilitando el análisis del impacto de los cambios, entre otras cosas. Los modelos han demostrado jugar un papel importante en el proceso de desarrollo de software, uno de sus usos principales en el contexto de la realización de PNs con servicios es el de diseñar servicios a un nivel más abstracto que con tecnologías específicas, promoviendo la reutilización separando la lógica de los servicios de su implementacion. MINERVA: Model drIveN & sErvice oRiented framework for the continuous business process improVement & relAted tools es el marco que se ha definido en este trabajo de tesis, que toma en cuenta todos los aspectos mencionados, en el cual los paradigmas de Computación Orientada a Servicios (Service Oriented Computing, SOC) y Desarrollo Dirigido por Modelos (Model Driven Development, MDD) se aplican a los PNs con foco en su mejora continua, extendiendo un ciclo de vida PN existente con actividades y elementos explícitos para la medición de la ejecución y mejora de PNs. El marco se compone de tres dimensiones: i) conceptual, que define los conceptos que se manejan en todo el marco. ii) metodológica, que define una metodología para el desarrollo orientado a servicios desde PNs, con generación automática de modelos de servicio en SoaML desde modelos en BPMN2, junto con un proceso de mejora continua basado en la medición de la ejecución de las ocurrencias de los PNs en la organización para llevar a cabo el esfuerzo de mejora. iii) soporte de herramientas para la propuesta completa basado en la integracion de varias herramientas existentes, junto con otras nuevas que hemos desarrollado. Las propuestas de MINERVA han sido validadas por medio de un experimento y dos casos de estudio realizados en el marco de proyectos reales en dos organizaciones, de los cuales, como resultado principal de las aplicaciones realizadas, se puede concluir que MINERVA puede ser una guía útil y clave para la mejora continua de PNs realizados por servicios y para el desarrollo de sistemas orientados a servicios desde PNs, con generación automática de modelos de servicio a partir de modelos de PN

Multikonferenz Wirtschaftsinformatik (MKWI) 2016: Technische Universität Ilmenau, 09. - 11. März 2016; Band II

Übersicht der Teilkonferenzen Band II • eHealth as a Service – Innovationen für Prävention, Versorgung und Forschung • Einsatz von Unternehmenssoftware in der Lehre • Energieinformatik, Erneuerbare Energien und Neue Mobilität • Hedonische Informationssysteme • IKT-gestütztes betriebliches Umwelt- und Nachhaltigkeitsmanagement • Informationssysteme in der Finanzwirtschaft • IT- und Software-Produktmanagement in Internet-of-Things-basierten Infrastrukturen • IT-Beratung im Kontext digitaler Transformation • IT-Sicherheit für Kritische Infrastrukturen • Modellierung betrieblicher Informationssysteme – Konzeptuelle Modelle im Zeitalter der digitalisierten Wirtschaft (d!conomy) • Prescriptive Analytics in I

Automated software systems generation for process-oriented organizations

Tese de doutoramento do Programa Doutoral em Tecnologias e Sistemas de InformaçãoCada vez mais, as organizações suportam as suas operações em sistemas de software. Torna-se, portanto, muito relevante o correto mapeamento das operações nos sistemas de software. Esta tese foca-se em organizações orientadas a processos de negócio, devido à relevância dada pelas normas de qualidade, pelos modelos de excelência, e pelos requisitos dos clientes, a esse tipo de estruturação interna das organizações. Nas organizações orientadas a processos de negócio existem diversos fatores, como o tempo envolvido nos projetos de implementação de processos de negócio em software, as diferenças existentes entre os modelos de processos de negócio e a sua implementação real, ou a quantidade e o tipo de recursos envolvidos nesses projetos, que fazem com que os projetos de desenvolvimento de software sejam demasiado dispendiosos, demorem demasiado tempo, e não garantam que o produto de software resultante seja o mais adequado à realidade da organização que o vai usar. Esta tese propõe que os sistemas de informação e de software devam ser desenvolvidos, desde o início, incorporando os modelos das organizações onde irão ser usados. Além disso, e como existem disponíveis modelos de referência de processos de negócio, esta tese também propõe o seu uso explícito aquando da recolha de requisitos. Assim, o objetivo principal da tese é propor uma metodologia que se inicie com modelos de processos de negócio e que termine com a geração de sistemas de software, para organizações orientadas a processos de negócio. A metodologia denomina-se BIM e é formalizada através do metamodelo EPF. Dada a abrangência dos temas a tratar, a tese foi conduzida tendo em atenção que o processo de desenvolvimento de software para suportar organizações orientadas a processos pode ser otimizado. Para melhor mostrar os diversos passos e resultados intermédios, usamos a metodologia de investigação Action Research. A tese propõe que as atividades de investigação sejam terminadas quando uma dada condição de paragem seja atingida, e para isso usa uma avaliação baseada num conjunto de indicadores para os resultados do produto e do processo, e uma adaptação do modelo de excelência EFQM para a forma como foi executado o processo de desenvolvimento. O foco das Action são os sistemas de software MES, essenciais na ligação entre sistemas de software embebido e sistemas ERP. Nesta tese, as Action iniciam-se com modelos de processos e com arquiteturas de software standard, e terminam com uma proposta de modelo de processo e com arquiteturas de software e tecnologias adaptadas à execução de processos de negócio. A tese propõe também alguns conceitos como IAvO (extensão de modelos de processos de negócio), OBO (componentes de software intermutáveis e não-proprietários), OA (aspetos organizacionais), e PF (framework de processos) para aumentarem a eficiência e eficácia na implementação em software de processos de negócio.Increasingly, organizations support their operations by using software systems, turning very relevant the proper mapping of operations into software systems. This thesis focuses on organizations oriented to business processes, due to the importance that quality norms, excellence models, and customer requirements put on this type of internal structures of organizations. Process-oriented organizations have characteristics, such as the time needed to implement business processes in software, the differences between the business process models and the real business processes, or the quantity and type of the required resources, that lead to development projects too expensive, taking too long to complete, and that do not assure that the resulting product is the most adequate to the reality of the client organization. This thesis proposes that the development of information and software system embodies, since the early stages, the models of the organization where they operate. In addition, and since business process reference models are available, the thesis also proposes to use explicitly such reference models by requirements collection time. Thus, the main goal of the thesis is to propose a methodology that picks business process reference models and ends with software systems, for process-oriented organizations. The methodology is denominated BIM and is formalized by using the EPF metamodel. Due to the wide scope of the studied areas, the thesis is tailored considering that the development process for processoriented organizations can be optimized. To express better the intermediate steps and results, we use the Action Research methodology. The thesis proposes that the research activities terminate when a stopping condition is met, based on a set of indicators for the product, and a tailoring of the EFQM model for the development process. The Actions are focused on MES, crucial for the linking of embedded software systems with ERP systems. In this thesis, the Actions start by using standard process models and software architectures, and end by using a proposed process model, and software architectures and technologies adapted to the execution of business software. The thesis also proposes new concepts like IAvO (extension to business process reference models), OBO (interchangeable and nonproprietary software components), AO (organizational aspects), and PF (process framework) to increase the efficiency and the effectiveness of the implementation of business processes in software