Abstract
Many organizations use business process models for documenting their business opera- tions. In recent years, the Business Process Model and Notation (BPMN) evolved into the leading standard for process modeling. However, BPMN is complex: the specification offers a huge variety of different elements and often several representational choices for the same semantics. This raises the question of how well modelers can deal with these choices. Empirical insights into BPMN us- age from the perspective of practitioners are still missing. We close this gap by analyzing a large set of BPMN 2.0 process models from practice. We found that particularly representational choices for splits and joins, the correct use of message flow, the proper decomposition of models, and the consistent labeling appear to be connected with quality issues. Based on our findings we give five recommendations how these issues can be avoided in the future. The work summarized in this ex- tended abstract has been published in [LMG16].
Originalsprache | Englisch |
---|---|
Seiten (von - bis) | 26 - 33 |
Fachzeitschrift | IEEE Software |
Jahrgang | 33 |
Ausgabenummer | 4 |
DOIs | |
Publikationsstatus | Veröffentlicht - 2016 |
Österreichische Systematik der Wissenschaftszweige (ÖFOS)
- 502050 Wirtschaftsinformatik