Business Process Modeling Using Petri Nets

Author(s):  
Kees M. van Hee ◽  
Natalia Sidorova ◽  
Jan Martijn van der Werf
Author(s):  
Athanasios G. Lazaropoulos

Business process modeling attracts great importance in enterprises due to the need for a graphically simplified and less verbal way to manage their operations. Nevertheless, the existence of various process modeling standards across the different departments of the same enterprise, such as Business Process Modeling Notation (BPMN) diagrams, classic flowcharts, Gantt charts and Petri nets, urges their notation alignment. After the business process model nota-tion alignment, complex constraints and relationships among the enterprise's department processes can be automated and simplified. In the light of the digital transformation of today's enterprises, the main objective of this paper is the proposal of a straightforward and simplified business educational equivalence table so that a direct conversion among BPMN diagrams, flowcharts, Gantt Charts and Petri Nets can be locally fulfilled by non-specialized personnel in each enterprise's department. The methodology of this paper can be generalized in every enterprise where the aforementioned process modeling standards across its different departments coexist.


Author(s):  
Daniel Lübke ◽  
Maike Ahrens ◽  
Kurt Schneider

AbstractBusiness process modeling is an important activity for developing software systems—especially within digitization projects and when realizing digital business models. Specifying requirements and building executable workflows is often done by using BPMN 2.0 process models. Although there are several style guides available for BPMN, e.g., by Silver and Richard (BPMN method and style, vol 2, Cody-Cassidy Press, Aptos, 2009), there has not been much empirical research done into the consequences of the diagram layout. In particular, layouts that require scrolling have not been investigated yet. The aim of this research is to establish layout guidelines for business process modeling that help business process modelers to create more understandable business process diagrams. For establishing benefits and penalties of different layouts, a controlled eye tracking experiment was conducted, in which data of 21 professional software developers was used. Our results show that horizontal layouts are less demanding and that as many diagram elements as possible should be put on the initially visible screen area because such diagram elements are viewed more often and longer. Additionally, diagram elements related to the reader’s task are read more often than those not relevant to the task. BPMN modelers should favor a horizontal layout and use a more complex snake or multi-line layout whenever the diagrams are too large to fit on one page in order to support BPMN model comprehension.


2004 ◽  
Vol 13 (03) ◽  
pp. 289-332 ◽  
Author(s):  
JULIANE DEHNERT ◽  
WIL M. P. VAN DER AALST

This paper presents a methodology to bridge the gap between business process modeling and workflow specification. While the first is concerned with intuitive descriptions that are mainly used for communication, the second is concerned with configuring a process-aware information system, thus requiring a more rigorous language less suitable for communication. Unlike existing approaches the gap is not bridged by providing formal semantics for an informal language. Instead it is assumed that the desired behavior is just a subset of the full behavior obtained using a liberal interpretation of the informal business process modeling language. Using a new correctness criterion (relaxed soundness), it is verified whether a selection of suitable behavior is possible. The methodology consists of five steps and is illustrated using event-driven process chains as a business process modeling language and Petri nets as the workflow specification language.


Sign in / Sign up

Export Citation Format

Share Document