Showing papers on "Business Process Model and Notation published in 2009"

Business Artifacts: A Data-centric Approach to Modeling Business Operations and Processes

Abstract: Traditional approaches to business process modeling and wo rkflow are based on activity flows (with data often an afterthought) or documents (with processing o ften an afterthought). In contrast, an emerging approach uses(business) artifacts, that combine data and process in an holistic manner as the ba sic building block. These correspond to key business entities w hich evolve as they pass through the business’s operation. This short paper motivates the approach,surveys research and its applications, and discusses how principles and techniques from database mana gement research can further develop the artifact-centric paradigm.

Business process modeling - a comparative analysis

Abstract: Many business process modeling techniques have been proposed over the last decades, creating a demand for theory to assist in the comparison and evaluation of these techniques. A widely established way of determining the effectiveness and efficiency of modeling techniques is by way of representational analysis. This paper comparatively assesses representational analyses of 12 popular process modeling techniques in order to provide insights into the extent to which they differ from each other. We discuss several implications of our findings. Our analysis uncovers and explores representational root causes for a number of shortcomings that remain in process modeling practice, such as lack of process decomposition and integration of business rule specification. Our findings also serve as motivation and input to future research in areas such as context-aware business process design and conventions management.

Modern Business Process Automation: YAWL and its Support Environment

Abstract: Topics covered include: The fundamentals of business process modeling, including workflow patterns, an in-depth treatment of process flexibility, including approaches to dealing with on-the-fly changes, unexpected exceptions, and constraint-based processes, Technological aspects of a modern BPM environment, including its architecture, process design environment, process engine, resource handler and other support services,a comparative insight into current approaches to business process modeling and execution such as BPMN, EPCs, BPEL, jBPM, OpenWFE, and Enhydra Shark, process mining, verification, integration and configuration; and case studies in health care and screen business. This book provides a comprehensive treatment of the field of Business Process Management (BPM) with a focus on Business Process Automation. It achieves this by covering a wide range of topics, both introductory and advanced, illustrated through and grounded in the YAWL (Yet Another Workflow Language) language and corresponding open-source support environment. In doing so it provides the reader with a deep, timeless, and vendor-independent understanding of the essential ingredients of business process automation. The BPM field is in a continual state of flux and is subject to both the ongoing proposal of new standards and the introduction of new tools and technology. Its fundamentals however are relatively stable and this book aims to equip the reader with both a thorough understanding of them and the ability to apply them to better understand, assess and utilize new developments in the BPM field. As a consequence of its topic-based format and the inclusion of a broad range of exercises, the book is eminently suitable for use in tertiary education, both at the undergraduate and the postgraduate level, for students of computer science and information systems. BPM researchers and practitioners will also find it a valuable resource. The book serves as a unique reference to a varied and comprehensive collection of topics that are relevant to the business process life-cycle.

From business process models to process-oriented software systems

Abstract: Several methods for enterprise systems analysis rely on flow-oriented representations of business operations, otherwise known as business process models. The Business Process Modeling Notation (BPMN) is a standard for capturing such models. BPMN models facilitate communication between domain experts and analysts and provide input to software development projects. Meanwhile, there is an emergence of methods for enterprise software development that rely on detailed process definitions that are executed by process engines. These process definitions refine their counterpart BPMN models by introducing data manipulation, application binding, and other implementation details. The de facto standard for defining executable processes is the Business Process Execution Language (BPEL). Accordingly, a standards-based method for developing process-oriented systems is to start with BPMN models and to translate these models into BPEL definitions for subsequent refinement. However, instrumenting this method is challenging because BPMN models and BPEL definitions are structurally very different. Existing techniques for translating BPMN to BPEL only work for limited classes of BPMN models. This article proposes a translation technique that does not impose structural restrictions on the source BPMN model. At the same time, the technique emphasizes the generation of readable (block-structured) BPEL code. An empirical evaluation conducted over a large collection of process models shows that the resulting BPEL definitions are largely block-structured. Beyond its direct relevance in the context of BPMN and BPEL, the technique presented in this article addresses issues that arise when translating from graph-oriented to block-structure flow definition languages.

Enterprise, Business-Process and Information Systems Modeling

Abstract: This book contains the proceedings of two long-standing workshops: The 10th International Workshop on Business Process Modeling, Development and Support, BPMDS 2009, and the 14th International Conference on Exploring Modeling Methods for Systems Analysis and Design, EMMSAD 2009, held in connection with CAiSE 2009 in Amsterdam, The Netherlands, in June 2009. The 17 papers accepted for BPMDS 2009 were carefully reviewed and selected from 32 submissions. The topics addressed by the BPMDS workshop are business and goal-related drivers; model-driven process change; technological drivers and IT services; technological drivers and process mining; and compliance and awareness. Following an extensive review process, 16 papers out of 36 submissions were accepted for EMMSAD 2009. These papers cover the following topics: use of ontologies; UML and MDA; ORM and rule-oriented modeling; goal-oriented modeling; alignment and understandability; enterprise modeling; and patterns and anti-patterns in enterprise modeling.

Petri Net Transformations for Business Processes --- A Survey

Abstract: In Process-Aware Information Systems, business processes are often modeled in an explicit way. Roughly speaking, the available business process modeling languages can be divided into two groups.Languages from the first group are preferred by academic people but shunned by business people, and include Petri nets and process algebras. These academic languages have a proper formal semantics, which allows the corresponding academic models to be verified in a formal way. Languages from the second group are preferred by business people but disliked by academic people, and include BPEL, BPMN, and EPCs. These business languages often lack any proper semantics, which often leads to debates on how to interpret certain business models. Nevertheless, business models are used in practice, whereas academic models are hardly used. To be able to use, for example, the abundance of Petri net verification techniques on business models, we need to be able to transform these models to Petri nets. In this paper, we investigate a number of Petri net transformations that already exist.For every transformation, we investigate the transformation itself, the constructs in the business models that are problematic for the transformation and the main applications for the transformation.

A computer scientist's introductory guide to business process management (BPM)

Abstract: Computers play an integral part in designing, modelling, optimising and managing business processes within and across companies. While Business Process Management (BPM), Workflow Management (WfM) and Business Process Reengineering (BPR) have been IT-related disciplines with a history of about three decades, there is still a lack of publications clarifying definitions and scope of basic BPM terminologies like business process, BPM versus WfM, workflow, BPR, etc. Such a myriad of similar-sounding terminologies can be overwhelming for computer scientists and computer science students who may wish to venture into this area of research. This guide aims to address this gap by providing a high level overview of the key concepts, rationale, features and the developments of BPM.

Modeling Languages for Business Processes and Business Rules: A Representational Analysis

Abstract: Process modeling and rule modeling languages are both used to document organizational policies and procedures. To date, their synergies and overlap are under-researched. Understanding the relationship between the two modeling types would allow organizations to maximize synergies, avoid content duplication, and thus reduce their overall modeling effort. In this paper we use the Bunge-Wand-Weber (BWW) representation theory to compare the representation capabilities of process and rule modeling languages. We perform a representational analysis of four rule modeling specifications: The Simple Rule Markup Language (SRML), the Semantic Web Rules Language (SWRL), the Production Rule Representation (PRR) and the Semantics of Business Vocabulary and Business Rules (SBVR) specification. We compare their BWW representation capabilities with those of four popular conceptual process modeling languages. In our analysis we focus on the aspects of maximum ontological completeness and minimum ontological overlap. The outcome of this study shows that no single language is internally complete with respect to the BWW representation model. We also show that a combination of two languages, in particular SRML and BPMN, appears to be better suited for combined process and rule modeling than any of these modeling languages used independently.

A Data-Centric Design Methodology for Business Processes

Abstract: This chapter describes a design methodology for business processes and workflows that focuses first on “business artifacts”, which represent key (real or conceptual) business entities, including both the business-relevant data about them and their macro-level lifecycles. Individual workflow services (a.k.a. tasks) are then incorporated, by specifying how they operate on the artifacts and fit into their lifecycles. The resulting workflow is specified in a particular artifact-centric workflow model, which is introduced using an extended example. At the logical level this workflow model is largely declarative, in contrast with most traditional workflow models which are procedural and/or graph-based. The chapter includes a discussion of how the declarative, artifact-centric workflow specification can be mapped into an optimized physical realization.

Instantaneous Soundness Checking of Industrial Business Process Models

Abstract: We report on a case study on control-flow analysis of business process models. We checked 735 industrial business process models from financial services, telecommunications and other domains. We investigated these models for soundness (absence of deadlock and lack of synchronization) using three different approaches: the business process verification tool Woflan, the Petri net model checker LoLA, and a recently developed technique based on SESE decomposition. We evaluate the various techniques used by these approaches in terms of their ability of accelerating the check. Our results show that industrial business process models can be checked in a few milliseconds, which enables tight integration of modeling with control-flow analysis. We also briefly compare the diagnostic information delivered by the different approaches.

Business process verification – finally a reality!

Abstract: The goal of this paper is to demonstrate that process verification has matured to a level where it can be used in practice. Earlier techniques assumed simplified process models without the more advanced constructs available in today’s modelling languages (e.g., cancellation and OR-joins). This paper reports on new verification techniques that can be used to assess the correctness of real-life models. The proposed approach relies on using formal methods (i.e., mapping a business model to a reset net which is an extension of Petri nets, and performing state space analysis) to determine the correctness of business processes with cancellation and OR-joins. The paper also demonstrates how reduction rules can be used to improve the efficiency. We present these techniques in the context of the workflow language YAWL that provides direct support for 20 most frequently used patterns found today (including cancellation and OR-joins). But the results also apply to other languages with these features (e.g., BPMN, EPCs, UML activity diagrams, etc.). We have developed an editor that provides diagnostic information based on the techniques presented in this paper.

Business process management with the user requirements notation

Abstract: A number of recent initiatives in both academia and industry have sought to achieve improvements in e-businesses through the utilization of Business Process Management (BPM) methodologies and tools. However there are still some inadequacies that need to be addressed when it comes to achieving alignment between business goals and business processes. The User Requirements Notation (URN), recently standardized by ITU-T, has some unique features and capabilities beyond what is available in other notations that can help address alignment issues. In this paper, a URN-based framework and its supporting toolset are introduced which provide business process monitoring and performance management capabilities integrated across the BPM lifecycle. The framework extends the URN notation with Key Performance Indicators (KPIs) and other concepts to measure and align processes and goals. An example process for controlling access to a healthcare data warehouse is used to illustrate and evaluate the framework. Early results indicate the feasibility of the approach.

Amoeba: A methodology for modeling and evolving cross-organizational business processes

Abstract: Business service engagements involve processes that extend across two or more autonomous organizations. Because of regulatory and competitive reasons, requirements for cross-organizational business processes often evolve in subtle ways. The changes may concern the business transactions supported by a process, the organizational structure of the parties participating in the process, or the contextual policies that apply to the process. Current business process modeling approaches handle such changes in an ad hoc manner, and lack a principled means for determining what needs to be changed and where. Cross-organizational settings exacerbate the shortcomings of traditional approaches because changes in one organization can potentially affect the workings of another.This article describes Amoeba, a methodology for business processes that is based on business protocols. Protocols capture the business meaning of interactions among autonomous parties via commitments. Amoeba includes guidelines for (1) specifying cross-organizational processes using business protocols, and (2) handling the evolution of requirements via a novel application of protocol composition. This article evaluates Amoeba using enhancements of a real-life business scenario of auto-insurance claim processing, and an aerospace case study.

The Journey to Business Process Compliance

Abstract: It is a typical scenario that many organisations have their business processes specified independently of their business obligations (which includes contractual obligations to business partners, as well as obligations a business has to fulfil against regulations and industry standards). This is because of the lack of guidelines and tools that facilitate derivation of processes from contracts but also because of the traditional mindset of treating contracts separately from business processes. This chapter will provide a solution to one specific problem that arises from this situation, namely the lack of mechanisms to check whether business processes are compliant with business contracts. The chapter begins by defining the space for business process compliance and the eco-system for ensuring that process are compliant. The key point is that compliance is a relationship between two sets of specifications: the specifications for executing a business process and the specifications regulating a business. The central part of the chapter focuses on a logic based formalism for describing both the semantics of normative specifications and the semantics of compliance checking procedures.

On managing business processes variants

Abstract: Variance in business process execution can be the result of several situations, such as disconnection between documented models and business operations, workarounds in spite of process execution engines, dynamic change and exception handling, flexible and ad-hoc requirements, and collaborative and/or knowledge intensive work. It is imperative that effective support for managing process variances be extended to organizations mature in their BPM (business process management) uptake so that they can ensure organization wide consistency, promote reuse and capitalize on their BPM investments. This paper presents an approach for managing business processes that is conducive to dynamic change and the need for flexibility in execution. The approach is based on the notion of process constraints. It further provides a technique for effective utilization of the adaptations manifested in process variants. In particular, we will present a facility for discovery of preferred variants through effective search and retrieval based on the notion of process similarity, where multiple aspects of the process variants are compared according to specific query requirements. The advantage of this approach is the ability to provide a quantitative measure for the similarity between process variants, which further facilitates various BPM activities such as process reuse, analysis and discovery.

Information flows and business process integration

Abstract: Purpose – Many business process improvement efforts emphasize better integration, yet process integration can mean many things. The purpose of this paper is to emphasize the importance of information flows to modern business processes, and draw upon recent organizational and information systems literature to characterize process integration and to derive four principles of process integration: accessibility, timeliness, transparency, and granularity of information flows.Design/methodology/approach – Using a field study, the four principles of process integration are applied to analyze ten different business processes across five organizations.Findings – In total, 18 generalized activities are identified that describe non‐integrated behavior, and “keying in known data” was found to be the most common. Among other findings, analysis highlights the importance of documentation to modern business processes, especially for coordination roles, and the paper describes three different purposes for documentation fo...

The Architecture of the ArchiMate Language

Abstract: In current business practice, an integrated approach to business and IT is indispensable. In many enterprises, however, such an integrated view of the entire enterprise is still far from reality. To deal with these challenges, an integrated view of the enterprise is needed, enabling impact and change analysis covering all relevant aspects. This need sparked the development of the ArchiMate language. This paper is concerned with documenting some of the key design decisions and design principles underlying the ArchiMate language.

Process-Aware Information Systems: Lessons to Be Learned from Process Mining

Abstract: A Process-Aware Information System (PAIS) is a software system that manages and executes operational processes involving people, applications, and/or information sources on the basis of process models. Example PAISs are workflow management systems, case-handling systems, enterprise information systems, etc. This paper provides a brief introduction to these systems and discusses the role of process models in the PAIS life-cycle. Moreover, it provides a critical reflection on the state-of-the-art based on experiences with process mining . Process mining techniques attempt to extract non-trivial and useful information from event logs. One aspect of process mining is control-flow discovery, i.e., automatically constructing a process model (e.g., a Petri net) describing the causal dependencies between activities. The insights provided by process mining are very valuable for the development of the next generation PAISs because they clearly show a mismatch between the models proposed for driving these systems and reality. On the one hand, models tend to oversimplify things resulting in systems that are too restrictive. On the other hand, models fail to capture important aspects of business processes.

Complexity metrics for Workflow nets

Abstract: Process modeling languages such as EPCs, BPMN, flow charts, UML activity diagrams, Petri nets, etc., are used to model business processes and to configure process-aware information systems. It is known that users have problems understanding these diagrams. In fact, even process engineers and system analysts have difficulties in grasping the dynamics implied by a process model. Recent empirical studies show that people make numerous errors when modeling complex business processes, e.g., about 20% of the EPCs in the SAP reference model have design flaws resulting in potential deadlocks, livelocks, etc. It seems obvious that the complexity of the model contributes to design errors and a lack of understanding. It is not easy to measure complexity, however. This paper presents three complexity metrics that have been implemented in the process analysis tool ProM. The metrics are defined for a subclass of Petri nets named Workflow nets, but the results can easily be applied to other languages. To demonstrate the applicability of these metrics, we have applied our approach and tool to 262 relatively complex Protos models made in the context of various student projects. This allows us to validate and compare the different metrics. It turns out that our new metric focusing on the structuredness outperforms existing metrics.

Communication flow orientation in business process modeling and its effect on redesign success: Results from a field study

Abstract: Business process redesign has been intensely studied, particularly since the mid 1990s. One aspect that received little attention, however, is the relationship between business process modeling choices and redesign success. This research gap is addressed through a multi-methods study of 18 business process redesign projects conducted in 18 different organizations. A structural equation model is developed and tested based on data collected from those projects; the results are then triangulated with qualitative data. The structural equation model depicts relationships between the following broad perceptual constructs: communication flow orientation of a business process model, quality of a business process model, and business process redesign success. The communication flow orientation of a business process model is defined as the extent to which a model explicitly shows how communication interactions take place in a process. A model's perceived quality is defined as the degree to which the model presents the following perceptual sub-constructs: ease of generation, ease of understanding, completeness, and accuracy. The results of the study suggest that the degree of communication flow orientation of a business process model is significantly related to the model's perceived quality. Perceived model quality, in turn, is significantly related to perceived business process redesign success. Interestingly, a business process model's perceived completeness does not seem to be influenced by a model's communication flow orientation. The structural equation model accounted for 56% of the explained variance in the business process redesign success construct. The main implication of this study is that a focus on communication flows in business processes is an important ingredient in successful business process redesign projects.

Semantic Process Modeling – Design and Implementation of an Ontology-based Representation of Business Processes

Abstract: An extension of process modeling languages is designed which allows representing the semantics of model element labels which are formulated in natural language by using concepts of a formal ontology. This combination of semiformal models with formal ontologies will be characterized as semantic process modeling. The approach is exemplarily applied to the languages EPC (Event-driven Process Chain), BPMN (Business Process Modeling Notation) and OWL (Web Ontology Language) and is generalized by means of an information model. The proposed formalization of the semantics of individual model elements in conjunction with the usage of inference engines allows the improvement of query functionalities in modeling tools and enables new possibilities of model validation. The integration of the approach in the IT-based work environments of modelers is demonstrated by a system architecture and a prototypical implementation. Evidently, advantages in the areas of modeling, model management, IT-business alignment, and compliance can be achieved by the application of modeling tools augmented with semantic technologies.

Redesigning business processes: a methodology based on simulation and process mining techniques

Abstract: Nowadays, organizations have to adjust their business processes along with the changing environment in order to maintain a competitive advantage. Changing a part of the system to support the business process implies changing the entire system, which leads to complex redesign activities. In this paper, a bottom-up process mining and simulation-based methodology is proposed to be employed in redesign activities. The methodology starts with identifying relevant performance issues, which are used as basis for redesign. A process model is “mined” and simulated as a representation of the existing situation, followed by the simulation of the redesigned process model as prediction of the future scenario. Finally, the performance criteria of the current business process model and the redesigned business process model are compared such that the potential performance gains of the redesign can be predicted. We illustrate the methodology with three case studies from three different domains: gas industry, government institution and agriculture.

Improved model management with aggregated business process models

Abstract: Contemporary organizations invest much efforts in creating models of their business processes. This raises the issue of how to deal with large sets of process models that become available over time. This paper proposes an extension of Event-driven Process Chains, called the aggregate EPC (aEPC), which can be used to describe a set of similar processes with a single model. By doing so, the number of process models that must be managed can be decreased. But at the same time, the process logic for each specific element of the set over which aggregation takes place can still be distinguished. The presented approach is supported as an add-on to the ARIS modeling tool box. To show the feasibility and effectiveness of the approach, we discuss its practical application in the context of a large financial organization.

Towards Object-Aware Process Management Systems: Issues, Challenges, Benefits

Abstract: Contemporary workflow management systems (WfMS) offer promising perspectives in respect to comprehensive lifecycle support of business processes. However, there still exist numerous business applications with hard-coded process logic. Respective application software is both complex to design and costly to maintain. One major reason for the absence of workflow technology in these applications is the fact that many processes are data-driven; i.e., progress of process instances depends on value changes of data objects. Thus business processes and business data cannot be treated independently from each other, and business process models have to be compliant with the underlying data structure. This paper presents characteristic properties of data-oriented business software, which we gathered in several case studies, and it elaborates to what degree existing WfMS are able to provide the needed object-awareness. We show that the activity-centered paradigm of existing WfMS is too inflexible in this context, and we discuss major requirements needed to enable object-awareness in processes management systems.

Defining ETL worfklows using BPMN and BPEL

Abstract: Decisional systems are crucial for enterprise improvement. They allow the consolidation of heterogeneous data from distributed enterprise data stores into strategic indicators. An essential component of this data consolidation is the Extract, Transform, and Load (ETL) process. In the research literature there has been very few work defining conceptual models for ETL processes. At the same time, there are currently many tools that manage such processes. However, each tool uses its own model, which is not necessarily able to communicate with the models of other tools. In this paper, we propose a platform-independent conceptual model of ETL processes based on the Business Process Model Notation (BPMN) standard. We also show how such a conceptual model can be implemented using Business Process Execution Language (BPEL), a standard executable language for specifying interactions with web services.

Advances in enterprise engineering I

Abstract: Process Modeling.- On the Nature of Business Rules.- Process Flexibility: A Survey of Contemporary Approaches.- Subsuming the BPM Life Cycle in an Ontological Framework of Designing.- Information Gathering for Semantic Service Discovery and Composition in Business Process Modeling.- Collaboration and Interoperability.- Challenges in Collaborative Modeling: A Literature Review.- A Petri-Net Based Formalisation of Interaction Protocols Applied to Business Process Integration.- Enterprise Architecture.- Competencies and Responsibilities of Enterprise Architects.- Interoperability Strategies for Business Agility.- Towards a Business-Oriented Specification for Services.- Model Transformation and Simulation.- Automated Model Transformations Using the C.C Language.- Improvement in the Translation Process from Natural Language to System Dynamics Models.- Developing a Simulation Model Using a SPEM-Based Process Model and Analytical Models.- Formal Modeling and Discrete-Time Analysis of BPEL Web Services.

The Impact of Secondary Notation on Process Model Understanding

Abstract: Models of business processes are usually created and presented using some visual notation. In this way, one can express important activities, milestones, and actors of a process using interconnected graphical symbols. While it has been established for other types of models that their graphical layout is a factor in making sense of these, this aspect has not been investigated in the business process modeling area. This paper proposes a set of propositions about the effects of the secondary notation, which entails layout, on process model comprehension. While individual graphical readership and pattern recognition skills are known mediators in interpreting visual cues, these propositions take expertise into account. The goal of this paper is to lay the foundation of follow-up, empirical investigations to challenge these propositions.

Configurable Process Models: Experiences from a Municipality Case Study

Abstract: Configurable process models integrate different variants of a business process into a single model. Through configuration users of such models can then combine the variants to derive a process model optimally fitting their individual needs. While techniques for such models were suggested in previous research, this paper presents a case study in which these techniques were extensively tested on a real-world scenario. We gathered information from four Dutch municipalities on registration processes executed on a daily basis. For each process we identified variations among municipalities and integrated them into a single, configurable process model, which can be executed in the YAWL workflow environment. We then evaluated the approach through interviews with organizations that support municipalities in organizing and executing their processes. The paper reports on both the feedback of the interviewed partners and our own observations during the model creation.

Artifact-Based Transformation of IBM Global Financing

Abstract: IBM Global Financing (IGF) is transforming its business using the Business Artifact Method, an innovative business process modeling technique that identifies key business artifacts and traces their life cycles as they are processed by the business. IGF is a complex, global business operation with many business design challenges. The Business Artifact Method is a fundamental shift in how to conceptualize, design and implement business operations. The Business Artifact Method was extended to solve the problem of designing a global standard for a complex, end-to-end process while supporting local geographic variations. Prior to employing the Business Artifact method, process decomposition, Lean and Six Sigma methods were each employed on different parts of the financing operation. Although they provided critical input to the final operational model, they proved insufficient for designing a complete, integrated, standard operation. The artifact method resulted in a business operations model that was at the right level of granularity for the problem at hand. A fully functional rapid prototype was created early in the engagement, which facilitated an improved understanding of the redesigned operations model. The resulting business operations model is being used as the basis for all aspects of business transformation in IBM Global Financing.