Viewpoints on Business Process Models

Author(s):  
Giorgio Bruno

Over the past few years a number of viewpoints have influenced the design of notations for business processes. They emphasize the different elements (tasks, business entities and roles) that compose business process models; for this reason, they are referred to as activity-centric, data-centric, and role-centric viewpoints. The activity-centric viewpoint focuses on the orchestration of operational activities, which encompass human tasks and automatic ones. On the contrary, the data-centric viewpoint stresses the identification of the key business entities and their life cycles consisting of states and transitions. In the role-centric viewpoint, a process model is made up of several “role” models; each role model provides a restricted view of the process limited to the behavior of the role under consideration. This article illustrates how the above-mentioned viewpoints can be extracted from a global model, with the help of an example concerning the submission of papers to conferences.

Author(s):  
Giorgio Bruno

Over the past few years, a number of viewpoints have influenced the design of notations for business processes. They emphasize the different elements (tasks, business entities, and roles) that compose business process models; for this reason, they are referred to as activity-centric, data-centric, and role-centric viewpoints. The activity-centric viewpoint focuses on the orchestration of operational activities, which encompass human tasks and automatic ones. On the contrary, the data-centric viewpoint stresses the identification of the key business entities and their lifecycles consisting of states and transitions. In the role-centric viewpoint, a process model is made up of several “role” models; each role model provides a restricted view of the process limited to the behavior of the role under consideration. This chapter illustrates how the above-mentioned viewpoints can be extracted from a global model, with the help of an example concerning the submission of papers to conferences.


Author(s):  
Giorgio Bruno

Current approaches to the representation of business processes can be divided into two major categories, referred to as activity-centric and artifact-centric. The former underline the tasks as the basic units of work, and the latter stress the importance of the life cycles of the artifacts (i.e., the business entities). This paper analyzes the major issues that characterize the artifact-centric approach, i.e., structure, dynamics and coordination. These issues can be dealt with in various ways, ranging from separate models to holistic ones. The pros and cons of separate models and compact ones are analyzed on the basis of how they cope with three relevant aspects, i.e., aggregation, synchronization and matching. A number of motivating examples are presented along with the notation used to define them. This notation, named ARTS (ARtifacts and TAsks), considers both artifacts and tasks as first-class citizens of business process models.


2019 ◽  
Vol 25 (5) ◽  
pp. 908-922 ◽  
Author(s):  
Remco Dijkman ◽  
Oktay Turetken ◽  
Geoffrey Robert van IJzendoorn ◽  
Meint de Vries

Purpose Business process models describe the way of working in an organization. Typically, business process models distinguish between the normal flow of work and exceptions to that normal flow. However, they often present an idealized view. This means that unexpected exceptions – exceptions that are not modeled in the business process model – can also occur in practice. This has an effect on the efficiency of the organization, because information systems are not developed to handle unexpected exceptions. The purpose of this paper is to study the relation between the occurrence of exceptions and operational performance. Design/methodology/approach The paper does this by analyzing the execution logs of business processes from five organizations, classifying execution paths as normal or exceptional. Subsequently, it analyzes the differences between normal and exceptional paths. Findings The results show that exceptions are related to worse operational performance in terms of a longer throughput time and that unexpected exceptions relate to a stronger increase in throughput time than expected exceptions. Practical implications These findings lead to practical implications on policies that can be followed with respect to exceptions. Most importantly, unexpected exceptions should be avoided by incorporating them into the process – and thus transforming them into expected exceptions – as much as possible. Also, as not all exceptions lead to longer throughput times, continuous improvement should be employed to continuously monitor the occurrence of exceptions and make decisions on their desirability in the process. Originality/value While work exists on analyzing the occurrence of exceptions in business processes, especially in the context of process conformance analysis, to the best of the authors’ knowledge this is the first work that analyzes the possible consequences of such exceptions.


2014 ◽  
Vol 11 (2) ◽  
pp. 461-480 ◽  
Author(s):  
Nuno Castela ◽  
Paulo Dias ◽  
Marielba Zacarias ◽  
José Tribolet

Business process models are often forgotten after their creation and its representation is not usually updated. This appears to be negative as processes evolve over time. This paper discusses the issue of business process models maintenance through the definition of a collaborative method that creates interaction contexts enabling business actors to discuss about business processes, sharing business knowledge. The collaboration method extends the discussion about existing process representations to all stakeholders promoting their update. This collaborative method contributes to improve business process models, allowing updates based in change proposals and discussions, using a groupware tool that was developed. Four case studies were developed in real organizational environment. We came to the conclusion that the defined method and the developed tool can help organizations to maintain a business process model updated based on the inputs and consequent discussions taken by the organizational actors who participate in the processes.


2020 ◽  
Author(s):  
Henry Chika Eleonu

Purpose - The purpose of this paper is to present a business process measurement framework for the evaluation of a corpus of business processes modelled in different business process modelling approaches. The results of the application of the proposed measurement framework will serve as a basis for choosing business process modelling approaches. Design/methodology/approach - The approach uses ideas of the Goal Question Metric (GQM) framework to define metrics for measuring a business process where the metrics answer the questions to achieve the goal. The Weighted Sum Method (WSM) is used to aggregate the measure of attributes of a business process to derive an aggregate measure, and business process modelling approaches are compared based on the evaluation of business process models created in different business process modelling approaches using the aggregate measure. Findings - The proposed measurement framework was applied to a corpus of business process models in different business process modelling approaches and is showed that insight is gained into the effect of business process modelling approach on the maintainability of a business process model. From the results, business process modelling approaches which imbibed the principle of separation of concerns of models, make use of reference or base model for a family of business process variants and promote the reuse of model elements performed highest when their models are evaluated with the proposed measurement framework. The results showed that the applications of the proposed framework proved to be useful for the selection of business process modelling approaches. Originality - The novelty of this work is in the application of WSM to integrate metric of business process models and the evaluation of a corpus of business process models created in different business process modelling approaches using the aggregate measure.


2010 ◽  
Vol 21 (4) ◽  
pp. 14-34 ◽  
Author(s):  
Rong Liu ◽  
Frederick Y. Wu ◽  
Santhosh Kumaran

Much of the prior work in business process modeling is activity-centric. Recently, an information-centric approach has emerged, where a business process is modeled as the interacting lifecycles of business entities. The benefits of this approach are documented in a number of case studies. In this paper, the authors formalize the information-centric approach and derive the relationships between the two approaches. The authors formally define the notion of a business entity, provide an algorithm to transform an activity-centric model into an information-centric process model, and demonstrate the equivalence between these two models. Further, they show the value of transforming from the activity-centric paradigm to the information-centric paradigm in business process componentization and Service-Oriented Architecture design and also provide an empirical evaluation.


Author(s):  
Sven Feja ◽  
Andreas Speck ◽  
Elke Pulvermüller ◽  
Marcel Schulz

Nevertheless distinctive improvements are necessary before this technology can be applied in the real system development. Graphical formal requirement notations for different kinds of process model notations as representations of the specification of rules are also crucial, along with the ability to present the positive and especially negative results to the different types of stakeholders. And finally, the model checking technique has to be improved in order to deal with different types of model elements which are typical for business process models.


Author(s):  
Alessandro Marchetto ◽  
Chiara Di Francescomarino

Web Applications (WAs) have been often used to expose business processes to the users. WA modernization and evolution are complex and time-consuming activities that can be supported by software documentation (e.g., process models). When, as often happens, documentation is missing or is incomplete, documentation recovery and mining represent an important opportunity for reconstructing or completing it. Existing process-mining approaches, however, tend to recover models that are quite complex, rich, and intricate, thus difficult to understand and use for analysts and developers. Model refinement approaches have been presented in the literature to reduce the model complexity and intricateness while preserving the capability of representing the relevant information. In this chapter, the authors summarize approaches to mine first and refine later business process models from existing WAs. In particular, they present two process model refinement approaches: (1) re-modularization and (2) reduction. The authors introduce the techniques and show how to apply them to WAs.


Author(s):  
Alessandro Marchetto ◽  
Chiara Di Francescomarino

Web Applications (WAs) have been often used to expose business processes to the users. WA modernization and evolution are complex and time-consuming activities that can be supported by software documentation (e.g., process models). When, as often happens, documentation is missing or is incomplete, documentation recovery and mining represent an important opportunity for reconstructing or completing it. Existing process-mining approaches, however, tend to recover models that are quite complex, rich, and intricate, thus difficult to understand and use for analysts and developers. Model refinement approaches have been presented in the literature to reduce the model complexity and intricateness while preserving the capability of representing the relevant information. In this chapter, the authors summarize approaches to mine first and refine later business process models from existing WAs. In particular, they present two process model refinement approaches: (1) re-modularization and (2) reduction. The authors introduce the techniques and show how to apply them to WAs.


2020 ◽  
pp. 1681-1695
Author(s):  
Giorgio Bruno

This chapter stresses the importance of the dataflow in business process models and illustrates a notation called DMA that is meant to fulfill two major goals: promoting the integration between business processes and information systems and leveraging the dataflow to provide flexibility in terms of human decisions. The first goal is fulfilled by considering both tasks and business entities as first-class citizens in process models. Business entities form the dataflow that interconnects the tasks: tasks take the input entities from the input dataflow and deliver the output entities to the output dataflow. Human decisions encompass the selection of the input entities when a task needs more than one, and the selection of the task with which to handle the input entities when two or more tasks are admissible. DMA provides a number of patterns that indicate how tasks affect the dataflow. In addition, two compound patterns, called macro tasks, can be used to represent task selection issues. An example related to an order handling process illustrates the notation.


Sign in / Sign up

Export Citation Format

Share Document