Business Process Model and Notation

About: Business Process Model and Notation is a research topic. Over the lifetime, 9038 publications have been published within this topic receiving 190712 citations. The topic is also known as: Business Process Modeling Notation & BPMN.

BPMN 2.0 for Modeling Business Processes

Abstract: In 2004, the Business Process Modeling Notation (BPMN) was presented as a standard business process modeling language. Its development was considered to be an important step in reducing the fragmentation that was witnessed between the existing process modeling tools and notations. Since then BPMN has been evaluated in different ways by the academic community and has become widely supported and used by industry. After completing the first major revisions of BPMN, the Object Management Group (OMG) released BPMN 2.0 in 2011. This chapter gives an overview of BPMN 2.0 and summarizes some of the evaluations of BPMN used for analysis and design of business processes and presents these together with reported experiences as well as some examples of proposed extensions and future expectations based on these. We will based on this also present some implications for practitioners.

A methodology for business process improvement and IS development

Abstract: This paper aims at discussing business process modelling and improvement as an essential work to create a successful and competitive enterprise. To achieve this goal, we use a methodology called TAD, which consists of six phases. The first three deal with business process identification, modelling and improvement. The methodology presents a new unique way for business process identification, modelling, and improvement. The last three phases continue with the implementation of the improved business process(es) by developing its information system. The business process ''Surgery'' is used as an example to show the implementation of the methodology.

A Model-based Approach for Diagnosing Fault in Web Service Processes

Abstract: Web services based on a service-oriented architecture framework provide a suitable technical foundation for business process management and integration. A business process can be composed of a set of Web services that belong to different companies and interact with each other by sending messages. Web service orchestration languages are defined by standard organizations to describe business processes composed of Web services. A business process can fail for many reasons, such as faulty Web services or mismatching messages. It is important to find out which Web services are responsible for a failed business process because we could penalize these Web services and exclude them from the business process in the future. In this paper, we propose a model-based approach to diagnose the faults in a Web service-composed business process. We convert a Web service orchestration language, more specifically BPEL4WS, into synchronized automata, so that we have a formal description of the topology and variable dependency of the business process. After an exception is thrown, the diagnoser can calculate the business process execution trajectory based on the formal model and the observed evolution of the business process. The faulty Web services are deduced from the variable dependency on the execution trajectory. We demonstrate our diagnosis technique with an example.

Action Patterns in Business Process Models

Abstract: Business process management experiences a large uptake by the industry, and process models play an important role in the analysis and improvement of processes. While an increasing number of staff becomes involved in actual modeling practice, it is crucial to assure model quality and homogeneity along with providing suitable aids for creating models. In this paper we consider the problem of offering recommendations to the user during the act of modeling. Our key contribution is a concept for defining and identifying action patterns - chunks of actions often appearing together in business processes. In particular, we specify action patterns and demonstrate how they can be identified from existing process model repositories using association rule mining techniques. Action patterns can then be used to suggest additional actions for a process model. Our approach is challenged by applying it to the collection of process models from the SAP Reference Model.