[Paper Review] Business Process Modeling: Blueprinting

Sabah Al‐Fedaghi|arXiv (Cornell University)|Apr 9, 2017

Business Process Modeling and Analysis2 references3 citations

TL;DR

This paper proposes a flow-based methodology for business process modeling that offers an alternative to existing tools like IBM Blueworks. By re-modeling a Blueworks case study using a diagrammatic, flow-oriented approach, the author demonstrates a clear, explicit framework for capturing processes, contributing to methodological diversity in software engineering practice and research.

ABSTRACT

This paper presents a flow-based methodology for capturing processes specified in business process modeling. The proposed methodology is demonstrated through re-modeling of an IBM Blueworks case study. While the Blueworks approach offers a well-proven tool in the field, this should not discourage workers from exploring other ways of thinking about effectively capturing processes. The diagrammatic representation presented here demonstrates a viable methodology in this context. It is hoped this explicit analysis of diverse fundamental approaches will benefit the research in the field and also advance current practices.

Motivation & Objective

• To introduce a new, flow-based methodology for business process modeling that complements existing tools like IBM Blueworks.
• To provide a diagrammatic and explicit approach to modeling business processes that enhances clarity and consistency.
• To demonstrate the viability of alternative modeling approaches beyond dominant commercial tools.
• To support methodological diversity in software engineering research and practice by analyzing fundamental modeling techniques.
• To advance current practices by offering a structured, reusable framework for process representation and analysis.

Proposed method

• The methodology is based on flow-based representation, emphasizing the sequence and flow of process steps.
• It employs a diagrammatic notation to model business processes, focusing on clarity and logical progression.
• The approach is applied to re-model a case study originally developed in IBM Blueworks, enabling direct comparison.
• The model is constructed using explicit process flows, with clear start and end points, and defined transitions between activities.
• The method emphasizes traceability and explicitness in process representation, reducing ambiguity.
• The framework is designed to be independent of specific tools, promoting portability and reusability across environments.

Experimental results

Research questions

• RQ1 How can a flow-based, diagrammatic methodology improve the clarity and consistency of business process modeling?
• RQ2 What are the advantages of using a non-tool-specific, explicit modeling approach compared to commercial tools like IBM Blueworks?
• RQ3 Can a standardized, flow-oriented representation effectively re-express complex business processes from existing case studies?
• RQ4 How does this methodology contribute to methodological diversity in business process modeling research?
• RQ5 To what extent does this approach support better understanding and communication of business processes among stakeholders?

Key findings

• The proposed flow-based methodology successfully re-models the IBM Blueworks case study with enhanced clarity and explicit structure.
• The diagrammatic representation provides a viable, alternative approach to process modeling that is independent of proprietary tools.
• The method demonstrates improved traceability and logical flow, making process understanding more accessible.
• The explicit analysis of diverse modeling approaches contributes to both research and practical applications in software engineering.
• The methodology supports better communication and documentation of business processes through standardized, visual flow representation.
• The study confirms that alternative modeling frameworks can effectively coexist with and complement established tools like IBM Blueworks.