Abstract
The Business Process Modeling Notation has emerged as a popular choice for representing processes among Business Analysts and Information Systems professionals. While the BPMN specification provides a rich syntax for the capture and representation of process models, it does not provide any guidance for the organization of the resulting models. As a consequence, large process libraries may become disorganized and hard to manage due to variability in abstraction levels, process interfaces, and activity descriptions. Based on the analysis of a process library in a US government agency we present a proposal for design guidelines and use our design guideline to qualitatively assess existing work on model quality guidance. To better organize models at different abstraction levels we propose a process architecture that allows for the systematic organization of BPMN models for different stakeholder concerns.
Recommended Citation
zur Muehlen, Michael; Wisnosky, Dennis E.; and Kindrick, James, "Primitives: Design Guidelines and Architecture for BPMN Models" (2010). ACIS 2010 Proceedings. 32.
https://aisel.aisnet.org/acis2010/32