scholarly journals Checking Conformance of High-Level Business Process Models to Event Logs

Author(s):  
Antonina Begicheva ◽  
Irina Lomazova
Author(s):  
Bruna Brandão ◽  
Flávia Santoro ◽  
Leonardo Azevedo

In business process models, elements can be scattered (repeated) within different processes, making it difficult to handle changes, analyze process for improvements, or check crosscutting impacts. These scattered elements are named as Aspects. Similar to the aspect-oriented paradigm in programming languages, in BPM, aspect handling has the goal to modularize the crosscutting concerns spread across the models. This process modularization facilitates the management of the process (reuse, maintenance and understanding). The current approaches for aspect identification are made manually; thus, resulting in the problem of subjectivity and lack of systematization. This paper proposes a method to automatically identify aspects in business process from its event logs. The method is based on mining techniques and it aims to solve the problem of the subjectivity identification made by specialists. The initial results from a preliminary evaluation showed evidences that the method identified correctly the aspects present in the process model.


Author(s):  
Cesare Pautasso

Model-driven architecture (MDA), design and transformation techniques can be applied with success to the domain of business process modeling (BPM) with the goal of making the vision of business-driven development a reality. This chapter is centered on the idea of compiling business process models for executing them, and how this idea has been driving the design of the JOpera for Eclipse workflow management tool. JOpera presents users with a simple, graph-based process modeling language with a visual representation of both control and data-flow aspects. As an intermediate representation, the graphs are converted into Event-Condition-Action rules, which are further compiled into Java bytecode for efficient execution. These transformations of process models are performed by the JOpera process compiler in a completely transparent way, where the generated executable artefacts are kept hidden from users at all times (i.e., even for debugging process executions, which is done by augmenting the original, high level notation). The author evaluates his approach by discussing how using a compiler has opened up the several possibilities for performing optimization on the generated code and also simplified the design the corresponding workflow engine architecture.


2018 ◽  
Vol 59 (2) ◽  
pp. 251-284 ◽  
Author(s):  
Adriano Augusto ◽  
Raffaele Conforti ◽  
Marlon Dumas ◽  
Marcello La Rosa ◽  
Artem Polyvyanyy

Author(s):  
Stijn Goedertier ◽  
David Martens ◽  
Bart Baesens ◽  
Raf Haesen ◽  
Jan Vanthienen

2019 ◽  
Vol 84 ◽  
pp. 214-237 ◽  
Author(s):  
Hoang Nguyen ◽  
Marlon Dumas ◽  
Arthur H.M. ter Hofstede ◽  
Marcello La Rosa ◽  
Fabrizio Maria Maggi

2013 ◽  
Vol 55 (6) ◽  
Author(s):  
Achim D. Brucker

AbstractModern enterprise systems are often process-driven and, thus, rely heavily on process-aware information systems. In such systems, high-level process-models play an important role both for communicating business requirements between domain experts and system experts as well as basis for the system implementation. Since several years, enterprise system need to fulfil an increasing number of the security and compliance requirements. Thus, there is an increasing demand for integrating high-level security and compliance requirements into process models, i. e. a common language for domain experts, system experts, and security experts. We present a security modelling language, called SecureBPMN, that can easily be integrated into business process modelling languages. In this paper, we exemplary integrate SecureBPMN into BPMN and, thus, present a common language for describing business process models together with their security and compliance requirements.


Author(s):  
Giorgio Bruno

Flexibility and data handling are two hot topics in current research on business process models. However, these issues are tackled separately through declarative languages and artifact-centric approaches, respectively. It follows that the situations in which the choice of the task to perform is a human decision affected by the presence of suitable input entities are not adequately handled; unfortunately, these situations are common in several industrial processes such as build-to-order ones. An integrated approach able to combine flexibility and data handling is needed and to this end this paper presents a notation named ENTA (ENtities and TAsks): it makes both business entities and tasks first-class citizens in process models and it provides high-level descriptions of the tasks in terms of intended effects and constraints to be met. Some examples of order handling processes are used to explain the issues of entity selection and task selection: deciding which customer orders can be associated with the same supplier order is a case of entity selection while deciding whether to generate a new supplier order for the customer orders selected or to add them to an existing supplier order is a case of task selection.


2018 ◽  
Vol 24 (4) ◽  
pp. 1023-1049
Author(s):  
Asma Mejri ◽  
Sonia Ayachi-Ghannouchi ◽  
Ricardo Martinho

Purpose The purpose of this paper is to measure the flexibility of business process models. The authors give the notions of flexible process distance, which corresponds to the number of change operations needed for transforming one process model into another, considering the different perspectives (functional, operational, behavioral, informational, and organizational). Design/methodology/approach The proposed approach is a quantitative-based approach to measure the flexibility of business process models. In this context, the authors presented a method to compute the distance between two process models. The authors measured the distance between a process model and a process variant in terms of the number of high-level change operations (e.g. to insert or delete actors) needed to transform the process model into the respective variant when a change occurred, considering the different perspectives and the flexible features. Findings To evaluate the flexibility-measurement approach, the authors performed a comprehensive simulation using an emergency care (EC) business process model and its variants. The authors used a real-world EC process and illustrated the possible changes faced in the emergency department (possible variants). Simulation results were promising because they fit the flexibility needs of the EC process users. This was validated using the authors’ previous work which consists in a guidance approach for business process flexibility. Research limitations/implications The authors defined six different distances between business process models, which are summarized in the definition of total process distance. However, changes in one perspective may lead to changes in other perspectives. For instance, adding a new activity may lead to adding a new actor. Practical implications The results of this study would help companies to obtain important information about their processes and to compare the desired level of flexibility with their actual process flexibility. Originality/value This study is probably the first flexibility-measurement approach which incorporates features for capturing changes affecting the functional, operational, informational, organizational, and behavioral perspectives as well as elements related to approaches enhancing flexibility.


2017 ◽  
Vol 26 (02) ◽  
pp. 1742002 ◽  
Author(s):  
Shaya Pourmirza ◽  
Remco Dijkman ◽  
Paul Grefen

Process discovery algorithms aim to capture process models from event logs. These algorithms have been designed for logs in which the events that belong to the same case are related to each other — and to that case — by means of a unique case identifier. However, in service-oriented systems, these case identifiers are rarely stored beyond request-response pairs, which makes it hard to relate events that belong to the same case. This is known as the correlation challenge. This paper addresses the correlation challenge by introducing a technique, called the correlation miner, that facilitates discovery of business process models when events are not associated with a case identifier. It extends previous work on the correlation miner, by not only enabling the discovery of the process model, but also detecting which events belong to the same case. Experiments performed on both synthetic and real-world event logs show the applicability of the correlation miner. The resulting technique enables us to observe a service-oriented system and determine — with high accuracy — which request-response pairs sent by different communicating parties are related to each other.


Sign in / Sign up

Export Citation Format

Share Document