Tangible Business Process Modeling – Methodology and Experiment Design

Author(s):  
Alexander Grosskopf ◽  
Jonathan Edelman ◽  
Mathias Weske
Author(s):  
M. Spadoni ◽  
A. Abdmouleh

The purpose of this chapter is to present our contribution in business process modeling within the CAS (CIMOSA Application Server) project. In this project, a referential, which helps enterprises to model their internal or collaborative activities within an enterprise chain (i.e., extended enterprise) is proposed. The referential is supported by a meta-model, which consists of a process modeling concept and a methodology as a user modeling guide. Enterprise activities modeling is based on a business process approach CIMOSA-based and that we define into an enterprise system. In this manuscript, the implementation of the referential is detailed within an information system by a component approach and a framework, which integrates the modeling methodology. The referential components are developed with .NET Microsoft technology.


Author(s):  
J. Barjis ◽  
I. Barjis

For a successful study, design and development of the enterprise architecture, a thorough insight into the essence of the work and operation of an enterprise, is a crucial factor. As the well-known Zachman and other modern frameworks illustrate, enterprise processes and process modeling are one of the fundamental components of enterprise architecture for providing such an insight. Like building construction in which construction drawings or blueprints play crucial roles, enterprise process models are critical in developing enterprise architecture. Moreover, one may argue that the role of business process modeling in enterprise architecture is similar to the floor plan that defines the boundaries of a building to be constructed. Therefore, a suitable enterprise process modeling approach that could capture the essential operations and reflect the cross-enterprise (cross-departmental) processes is a needed component to complement enterprise architecture. In this chapter, authors study, discuss, and review the practical role of enterprise process modeling in enterprise architecture using a real life organization-based case study. Authors introduce a modeling methodology that captures essential activities not only within a process but also from the enterprise perspective where cross departmental or enterprise processes are represented.


2010 ◽  
pp. 621-635
Author(s):  
M. Spadoni ◽  
A. Abdmouleh

The purpose of this chapter is to present our contribution in business process modeling within the CAS (CIMOSA Application Server) project. In this project, a referential, which helps enterprises to model their internal or collaborative activities within an enterprise chain (i.e., extended enterprise) is proposed. The referential is supported by a meta-model, which consists of a process modeling concept and a methodology as a user modeling guide. Enterprise activities modeling is based on a business process approach CIMOSA-based and that we define into an enterprise system. In this manuscript, the implementation of the referential is detailed within an information system by a component approach and a framework, which integrates the modeling methodology. The referential components are developed with .NET Microsoft technology.


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