scholarly journals On the Interplay of Business Process Modeling and Missions in Systems-of-Information Systems

Author(s):  
Valdemar Vicente Graciano Neto ◽  
Everton Cavalcante ◽  
Jamal El Hachem ◽  
Daniel Soares Santos
Author(s):  
Jan Mendling

This chapter provides an overview of business process management and business process modeling. We approach business process management by giving a historical classification of seminal work, and define it by the help of the business process management life cycle. Business process models play an important role in this life cycle, in particular, if information systems are used for executing processes. We deduct a definition for business process modeling based on a discussion of modeling from a general information systems point of view. In the following, we detail business process modeling techniques, in particular, modeling languages and modeling procedures for business process modeling. Finally, we discuss some future trends with a focus on the business process execution language for Web services (BPEL), and conclude the chapter with a summary. The chapter aims to cover business process modeling in a comprehensive way such that academics and practitioners can use it as a reference for identifying more specialized works.


Author(s):  
Jan Mendling

This chapter provides an overview of business process management and business process modeling. We approach business process management by giving a historical classification of seminal work, and define it by the help of the business process management life cycle. Business process models play an important role in this life cycle, in particular, if information systems are used for executing processes. We deduct a definition for business process modeling based on a discussion of modeling from a general information systems point of view. In the following, we detail business process modeling techniques, in particular, modeling languages and modeling procedures for business process modeling. Finally, we discuss some future trends with a focus on the business process execution language for Web services (BPEL), and conclude the chapter with a summary. The chapter aims to cover business process modeling in a comprehensive way such that academics and practitioners can use it as a reference for identifying more specialized works.


Author(s):  
Sundar Gopalakrishnan ◽  
John Krogstie ◽  
Guttorm Sindre

For mobile and multi-channel information systems it is often relevant to model where something is supposed to take place. Traditional business process modeling notations seldom capture location. Examining if there might be any gain in extending mainstream modeling notations with the capture of location is an interesting research topic. This paper addresses this question both through an analytical comparison of various notation alternatives and two experiments investigating different ways of visualizing location. The results of the experiments indicate that the notation using color for distinguishing different places have advantage over textual annotations, whereas no significant difference was found between the use color and pattern fills when it came to the subjects’ performance solving the experimental tasks.


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.


Sign in / Sign up

Export Citation Format

Share Document