Enhancing CMMN: Conceptual Development of a Notational Variant for Case Management Modeling
Abstract
1. Introduction
2. Theoretical Background
2.1. Cognitive Effectiveness and Physics of Notations (PoN)
2.2. Case Management and CMMN
3. Related Work
4. Methodological Framework
5. Identified Shortcomings
- S1
- Poor understanding of activation logic. One of the most commonly cited shortcomings is the lack of an intuitive and structured representation of activation logic. Unlike BPMN, which inherently supports explicit visual representations of process flow relationships [2], the flexible nature of CMMN makes it difficult to depict the progression of tasks as explicit relational structures, especially for novice users. This gap in visual representation results in lower cognitive effectiveness, making the CMMN-based models less suitable for business process modeling.
- S2
- Weak data support. Another major shortcoming is the limited support for representing and managing data within CMMN-based models. While the CMMN is inherently designed for flexibility, this focus on dynamic task management often overlooks the need for structured data handling, making it challenging to integrate data-driven decision-making processes into case models. This limitation reduces the practical applicability of CMMN-based modeling in data-intensive scenarios.
- S3
- Insufficient role definition. The existing CMMN modeling framework lacks a clear and systematic way to define roles and responsibilities within CMMN-based case models. This ambiguity can lead to inconsistencies in role assignment, particularly in complex cases involving multiple stakeholders. The absence of an integrated role assignment mechanism further complicates the adoption of CMMN-based modeling approaches in professional settings where role clarity is crucial.
6. Development of Structural and Visual Enhancements
6.1. Visual Enhancement of Activation Logic Representation (R1)
6.2. Strengthening Data Entity Support (R2)
6.3. Role Definition Enhancement (R3)
7. Interchange and Serialization of the Proposed Notational Variant
7.1. Schema Overview
cmmn:CaseFileItem;
cmmn:CaseFileItemDefinition.
cmmnplus:tCaseFileItemPlus;
cmmnplus:tCaseFileItemDefinitionPlus;
cmmnplus:resourceState (ResourceStateEnum);
cmmnplus:locationRef (xs:anyURI);
cmmnplus:access (AccessEnum);
cmmnplus:author;
cmmnplus:version.
cmmnplus:description;
cmmnplus:status (StatusEnum);
cmmnplus:version.
cmmnplus:respContainer;
cmmnplus:responsibility.
cmmnplus:tHumanTaskPlus;
cmmnplus:tUserEventListenerPlus;
cmmnplus:tTableItemPlus.
7.2. Mapping of Concepts to XML
7.3. XML-Based Technical Validation
- <cmmn:caseFileItem
- id="cfi1"
- definitionRef="cfd1"
- xsi:type="cmmnplus:tCaseFileItemPlus"
- cmmnplus:resourceState="InReview"
- cmmnplus:access="Public_ReadOnly"
- cmmnplus:author="John"
- cmmnplus:version="1.0.1"
- cmmnplus:locationRef="https://example.org/docs/123"/>
- <cmmn:caseFileItemDefinition
- id="cfd1"
- name="DocumentType"
- xsi:type="cmmnplus:tCaseFileItemDefinitionPlus"
- cmmnplus:status="Active"
- cmmnplus:version="1.0.0"
- cmmnplus:description="Definition of a lab document type."/>
- <cmmn:humanTask id="ht1" name="Review document"
- xsi:type="cmmnplus:tHumanTaskPlus">
- <cmmnplus:respContainer name="RACI for Review">
- <cmmnplus:responsibility
- cmmnplus:responsible="true"
- cmmnplus:accountable="false"
- cmmnplus:consulted="false"
- cmmnplus:informed="false"/>
- </cmmnplus:respContainer>
- </cmmn:humanTask>
8. Demonstration and Evaluation
8.1. Scenario-Based Demonstration
8.2. Analytical Evaluation
9. Discussion
9.1. Conceptual Positioning
9.2. Language-Level Implications of the Proposed Notational Variant
9.3. Interpretation of Evaluation Results
9.4. Limitations of the Analytical Evaluation
9.5. Trade-Offs and Remaining Limitations of the Proposed Notational Variant
9.6. Directions for Future Research
10. Conclusions
Author Contributions
Funding
Data Availability Statement
Conflicts of Interest
References
- Dumas, M.; La Rosa, M.; Mendling, J.; Reijers, H.A. Fundamentals of Business Process Management, 2nd ed.; Springer: Berlin/Heidelberg, Germany, 2018. [Google Scholar] [CrossRef]
- Object Management Group. Business Process Model and Notation (BPMN) Specifications, Version 2.0; Object Management Group: Milford, MA, USA, 2011.
- van der Aalst, W.M.P.; Weske, M.; Grünbauer, D. Case handling: A new paradigm for business process support. Data Knowl. Eng. 2005, 53, 129–162. [Google Scholar] [CrossRef]
- Object Management Group. Case Management Model and Notation (CMMN) Specifications, Version 1.1; Object Management Group: Milford, MA, USA, 2016.
- Routis, I.; Bardaki, C.; Dede, G.; Nikolaidou, M.; Kamalakis, T.; Anagnostopoulos, D. CMMN evaluation: The modelers’ perceptions of the main notation elements. Softw. Syst. Model. 2021, 20, 2089–2109. [Google Scholar] [CrossRef]
- Freund, J.; Rucker, B. Real-Life BPMN: With Introductions to CMMN and DMN, 3rd ed.; CreateSpace Independent Publishing Platform: North Charleston, SC, USA, 2016. [Google Scholar]
- Bule, M.; Polančič, G. Analysis and Synthesis of Theoretical and Practical Implications of Case Management Model and Notation. Information 2025, 16, 310. [Google Scholar] [CrossRef]
- Recker, J. Opportunities and constraints: The current struggle with BPMN. Bus. Process. Manag. J. 2010, 16, 181–201. [Google Scholar] [CrossRef]
- Jalali, A. Evaluating Perceived Usefulness and Ease of Use of CMMN and DCR. In Proceedings of the 22nd International Conference Business Process Modeling, Development and Support (BPMDS), Melbourne, VIC, Australia, 28–29 June 2021; pp. 147–162. [Google Scholar] [CrossRef]
- Moody, D. The "Physics" of Notations: Toward a Scientific Basis for Constructing Visual Notations in Software Engineering. IEEE Trans. Softw. Eng. 2009, 35, 756–779. [Google Scholar] [CrossRef]
- Peffers, K.; Tuunanen, T.; Rothenberge, M.A. A Design Science Research Methodology for Information Systems Research. J. Manag. Inf. Syst. 2014, 24, 45–77. [Google Scholar] [CrossRef]
- Kitchenham, B.A.; Charters, S. Guidelines for Performing Systematic Literature Reviews in Software Engineering; Technical Report EBSE 2007-001; School of Computer Science and Mathematics, Keele University: Newcastle, UK, 2007. [Google Scholar]
- Moody, D.; van Hillegersberg, J. Evaluating the Visual Syntax of UML: An Analysis of the Cognitive Effectiveness of the UML Family of Diagrams. In Proceedings of the Software Language Engineering, Toulouse, France, 29–30 September 2009; Springer: Berlin/Heidelberg, Germany, 2009; pp. 16–34. [Google Scholar] [CrossRef]
- Genon, N.; Heymans, P.; Amyot, D. Analysing the Cognitive Effectiveness of the BPMN 2.0 Visual Notation. In Proceedings of the Software Language Engineering, Braga, Portugal, 3–4 July 2011; Springer: Berlin/Heidelberg, Germany, 2011; pp. 377–396. [Google Scholar] [CrossRef]
- Kocbek Bule, M.; Polančič, G.; Huber, J.; Jošt, G. Semiotic clarity of Case Management Model and Notation (CMMN). Comput. Stand. Interfaces 2019, 66, 103354. [Google Scholar] [CrossRef]
- Marin, M.A.; Hull, R.; Vaculín, R. Data Centric BPM and the Emerging Case Management Standard: A Short Survey. In Proceedings of the Business Process Management Workshops (BPM), Tallinn, Estonia, 3 September 2013; pp. 24–30. [Google Scholar]
- Swenson, K.D. Mastering the Unpredictable: How Adaptive Case Management Will Revolutionize the Way that Knowledge Workers Get Things Done; Meghan-Kiffer Press: Tampa, FL, USA, 2010. [Google Scholar]
- van der Aalst, W.; Pesic, M.; Schonenberg, H. Declarative workflows: Balancing between flexibility and support. Comp. Sci. Res. Dev. 2009, 23, 99–113. [Google Scholar] [CrossRef]
- Freund, J.; Ruecker, B. Real-Life BPMN: Includes an Introduction to DMN, 4th ed.; Independently Published; 2019. [Google Scholar]
- Bruno, G. Extending CMMN with entity life cycles. Procedia CS 2017, 121, 98–105. [Google Scholar] [CrossRef]
- Bruno, G. Tasks and assignments in case management models. Procedia CS 2016, 100, 156–163. [Google Scholar] [CrossRef][Green Version]
- Zensen, A.; Küster, J.M. A Comparison of Flexible BPMN and CMMN in Practice: A Case Study on Component Release Processes. In Proceedings of the 22nd International Enterprise Distributed Object Computing Conference (EDOC), Stockholm, Sweden, 16–19 October 2018; pp. 105–114. [Google Scholar] [CrossRef]
- Skouti, S.; Cherfi, S.; Comyn-Wattiau, I. RBPMN: The Value of Roles for Business Process Modeling. Softw. Syst. Model. 2024, 23, 1375–1406. [Google Scholar] [CrossRef]
- Routis, I.; Nikolaidou, M.; Anagnostopoulos, D. Empirical evaluation of CMMN models: A collaborative process case study. Softw. Syst. Model. 2020, 19, 1395–1413. [Google Scholar] [CrossRef]
- Intrigila, B.; Della Penna, G.; D’Ambrogio, A. A Lightweight BPMN Extension for Business Process-Oriented Requirements Engineering. Computers 2021, 10, 171. [Google Scholar] [CrossRef]
- Sprovieri, D.; Vogler, S. Run-Time Composition of Partly Structured Business Processes using Heuristic Planning. In Proceedings of the International Conference on Enterprise Systems (ES), Basel, Switzerland, 14–15 October 2015; pp. 225–232. [Google Scholar] [CrossRef]
- Allah Bukhsh, Z.; van Sinderen, M.; Sikkel, K.; Quartel, D. How to Manage and Model Unstructured Business Processes: A Proposed List of Representational Requirements. In Proceedings of the 14th International Joint Conference E-Business and Telecommunications (ICETE), Madrid, Spain, 24–26 July 2019; pp. 81–103. [Google Scholar] [CrossRef]
- Plebani, P.; Marrella, A.; Mecella, M.; Mizmizi, M.; Pernici, B. Multi-party Business Process Resilience By-Design: A Data-Centric Perspective. In Proceedings of the 29th International Conference Advanced Information Systems Engineering (CAiSE), Essen, Germany, 12–16 June 2017; pp. 110–124. [Google Scholar] [CrossRef]
- Marrella, A.; Mecella, M.; Pernici, B.; Plebani, P. A design-time data-centric maturity model for assessing resilience in multi-party business processes. Inf. Syst. 2019, 86, 62–78. [Google Scholar] [CrossRef]
- Gonzalez-Lopez, F.; Pufahl, L. A Landscape for Case Models. In Proceedings of the Enterprise, Business-Process and Information Systems Modeling, Rome, Italy, 3–4 June 2019; pp. 87–102. [Google Scholar] [CrossRef]
- de Carvalho, R.M.; Mili, H.; Gonzalez-Huerta, J.; Boubaker, A.; Leshob, A. Comparing ConDec to CMMN—Towards a Common Language for Flexible Processes. In Proceedings of the 4th International Conference on Model-Driven Engineering and Software Development (MODELSWARD), Rome, Italy, 19–21 February 2016; pp. 233–240. [Google Scholar]
- Kurz, M.; Schmidt, W.; Fleischmann, A.; Lederer, M. Leveraging CMMN for ACM: Examining the Applicability of a New OMG Standard for Adaptive Case Management. In Proceedings of the 7th International Conference on Subject-Oriented Business Process Management, Kiel, Germany, 23–24 April 2015; pp. 1–9. [Google Scholar] [CrossRef]
- Herzberg, N.; Kirchner, K.; Weske, M. Modeling and Monitoring Variability in Hospital Treatments: A Scenario Using CMMN. In Proceedings of the Business Process Management Workshops (BPM), Eindhoven, The Netherlands, 7–8 September 2015; pp. 3–15. [Google Scholar] [CrossRef]
- Milani, F.; García-Bañuelos, L.; Filipova, S.; Markovska, M. Modelling blockchain-based business processes: A comparative analysis of BPMN vs CMMN. Bus. Process. Manag. J. 2021, 27, 638–657. [Google Scholar] [CrossRef]
- Hevner, A.; March, S.T.; Park, J.; Ram, S. Design Science in Information Systems Research. MIS Q. 2004, 28, 75–105. [Google Scholar] [CrossRef]
- Dublin Core Metadata Initiative. DCMI Metadata Terms. 2025. Available online: https://www.dublincore.org/ (accessed on 12 December 2025).
- Bule, M.; Polančič, G. CMMNplus-Formal Semantics. [Dataset] GitHub Repository. 2025. Available online: https://github.com/matejabule/CMMNplus-formalSemantics (accessed on 12 December 2025).
- Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 7th ed.; Project Management Institute, Inc.: Newtown Square, PA, USA, 2021. [Google Scholar]
- Bule, M.; Polančič, G. CMMNplus-Serialization Schema. [Dataset] GitHub Repository. 2025. Available online: https://github.com/matejabule/CMMNplus-serialization (accessed on 12 December 2025).
- Granada, D.; Vara, J.M.; Brambilla, M.; Bollati, V.A.; Marcos, E. Analysing the cognitive effectiveness of the WebML visual notation. Softw. Syst. Model. 2017, 16, 195–227. [Google Scholar] [CrossRef]
- Jošt, G.; Huber, J.; Heričko, M.; Polančič, G. Improving cognitive effectiveness of business process diagrams with opacity-driven graphical highlights. Decis. Support Syst. 2017, 103, 58–69. [Google Scholar] [CrossRef]
- Polančič, G.; Kous, K. High-Level Process Modeling—An Experimental Investigation of the Cognitive Effectiveness of Process Landscape Diagrams. Mathematics 2024, 12, 1376. [Google Scholar] [CrossRef]
- Figl, K.; Derntl, M. The Impact of Perceived Cognitive Effectiveness on Perceived Usefulness of Visual Conceptual Modeling Languages. In Proceedings of the Conceptual Modeling–ER 2011, Brussels, Belgium, 31 October–3 November 2011; Springer: Berlin/Heidelberg, Germany, 2011; pp. 78–91. [Google Scholar] [CrossRef]
- Genon, N.; Amyot, D.; Heymans, P. Analysing the Cognitive Effectiveness of the UCM Visual Notation. In Proceedings of the System Analysis and Modeling: About Models, Oslo, Norway, 4–5 October 2010; Springer: Berlin/Heidelberg, Germany, 2011; pp. 221–240. [Google Scholar] [CrossRef]
- Saeed, M.; Saleh, F.; Al-Insaif, S.; El-Attar, M. Empirical Validating the Cognitive Effectiveness of a New Feature Diagrams Visual Syntax. Inf. Softw. Technol. 2016, 71, 1–26. [Google Scholar] [CrossRef]









| Attribute | Value and Annotation | Icon |
|---|---|---|
| multiplicity MultiplicityEnum | ZeroOrOne (0..1) | ![]() |
| ZeroOrMore (0..*) | ![]() | |
| ExactlyOne (1) | ![]() | |
| OneOrMore (1..*) | ![]() | |
| Unspecified | ![]() | |
| Unknown | ![]() | |
| resourceState ResourceStateEnum | Draft | ![]() |
| InReview | ![]() | |
| InApproval | ![]() | |
| Approved | ![]() | |
| Published | ![]() | |
| Unpublished | ![]() | |
| Archived | ![]() | |
| Canceled | ![]() | |
| Unspecified | ![]() | |
| Unknown | ![]() | |
| access AccessEnum | Private_ReadOnly | ![]() |
| Private_Editable | ![]() | |
| Public_ReadOnly | ![]() | |
| Public_Editable | ![]() | |
| Unspecified | ![]() | |
| Unknown | ![]() |
| Attribute | Value and Annotation | Icon |
|---|---|---|
| definitionType URI | Folder in CMIS | ![]() |
| Document in CMIS | ![]() | |
| Relationship in CMIS | ![]() | |
| XML-Schema | ![]() | |
| Unspecified | ![]() | |
| Unknown | ![]() | |
| status StatusEnum | Active | – |
| Deprecated | – | |
| Archived | – | |
| Unspecified | – | |
| Unknown | – |
| Metamodel | XSD Element/Attribute |
|---|---|
| CSI resourceState | <cmmn:caseFileItem xsi:type="cmmnplus:tCaseFileItemPlus" cmmnplus:resourceState={Draft, InReview, InApproval, Approved, Published, Unpublished, Archived, Canceled, Unspecified, Unknown}> |
| CSI locationRef | <cmmn:caseFileItem xsi:type="cmmnplus:tCaseFileItemPlus" cmmnplus:locationRef="anyURI"> |
| CSI access | <cmmn:caseFileItem xsi:type="cmmnplus:tCaseFileItemPlus" cmmnplus:access={Private_ReadOnly, Private_Editable, Public_ReadOnly, Public_Editable, Unspecified, Unknown}> |
| CSI author | <cmmn:caseFileItem xsi:type="cmmnplus:tCaseFileItemPlus" cmmnplus:author="string"> |
| CSI version | <cmmn:caseFileItem xsi:type="cmmnplus:tCaseFileItemPlus" cmmnplus:version="string"> |
| Metamodel | XSD Element/Attribute |
|---|---|
| CSID description | <cmmn:caseFileItemDefinition xsi:type="cmmnplus:tCaseFileItemDefinitionPlus" cmmnplus:description="string"> |
| CSID status | <cmmn:caseFileItemDefinition xsi:type="cmmnplus:tCaseFileItemDefinitionPlus" cmmnplus:status=Active, Deprecated, Archived, Unspecified, Unknown> |
| CSID version | <cmmn:caseFileItemDefinition xsi:type="cmmnplus:tCaseFileItemDefinitionPlus" cmmnplus:version="string"> |
| Metamodel | XSD Element/Attribute |
|---|---|
| Role assignment | <cmmnplus:respContainer> <cmmnplus:responsibility cmmnplus:responsible="true" cmmnplus:accountable="false" cmmnplus:support="false" cmmnplus:consulted="false" cmmnplus:informed="false"/> </cmmnplus:respContainer> |
| Principle PoN | Evaluation Summary |
|---|---|
| Semiotic clarity | (Enhancement level—R1, R2, R3) The proposed CMMN-based notational variant affects semiotic clarity in different ways. R1 replaces the visual representation of EntryCriterion and ExitCriterion without altering their underlying semantics and therefore does not affect the one-to-one mapping between concepts and symbols. R3 improves semiotic clarity by introducing an explicit graphical symbol for the existing Role concept, thereby resolving a missing-symbol violation present in standard CMMN. In contrast, R2 introduces additional icons to CaseFileItem that do not correspond to separate semantic constructs. While this constitutes redundant mapping from a strict semiotic perspective, these markers function as informative visual cues that support interpretability despite formally reducing one-to-one correspondence. |
| Perceptual discriminability | The analysis of the proposed CMMN-based notational variant indicates an improved level of perceptual discriminability among its symbols compared to standard CMMN (0.98 vs. 0.95). The enhanced shapes and clearer visual cues introduced by the notational enhancements further minimize perceptual confusion and support faster, more accurate symbol recognition. |
| Semantic transparency | The proposed CMMN-based notational variant exhibits a higher level of semantic transparency compared to standard CMMN (0.53 vs. 0.38). The redesigned and extended symbols convey their intended meaning more directly, resulting in a higher proportion of immediately and intuitively interpretable constructs. |
| Complexity management | Standard CMMN and the proposed CMMN-based notational variant provide a comparable level of complexity management, as both rely on the same core mechanisms of modularity, hierarchy, and abstraction. While the notational variant introduces clearer and more explicit modeling constructs, these enhancements do not fundamentally extend the structural means available for managing complexity. Consequently, observed improvements are modest and primarily related to increased clarity rather than to enhanced complexity-handling capability. |
| Cognitive integration | The proposed CMMN-based notational variant exhibits a modest but meaningful improvement in cognitive integration across process, data, organizational, and rule-related perspectives compared to standard CMMN (0.29 vs. 0.26). The introduced notational enhancements provide more explicit and semantically clearer relationships between modeling concepts, supporting a higher degree of qualitative cohesion within the notation. |
| Visual expressiveness | Standard CMMN and the proposed CMMN-based notational variant exhibit a comparable level of visual expressiveness, as both rely on essentially the same set of visual variables, including shape, line style, and iconography. While the notational variant introduces additional symbols, these enhancements do not extend the underlying palette of graphical dimensions and therefore do not substantially increase the expressive capacity of the notation. Consequently, the level of visual expressiveness remains broadly aligned with that of standard CMMN. |
| Dual coding | Standard CMMN exhibits a moderate level of dual coding (0.69), reflecting a relatively consistent combination of textual and graphical cues across most elements. The proposed CMMN-based notational variant reaches a comparable but slightly lower value (0.47), as the notational enhancements extend the symbol set without substantially altering naming conventions. This indicates that the added constructs do not increase the degree of textual–graphical integration. Consequently, both notations rely primarily on visual forms for conveying meaning, with limited systematic use of textual labels. |
| Graphic economy | Standard CMMN exhibits a relatively high level of graphic economy at the level of its core notation, relying on a compact set of symbols to express its basic semantics. With the introduction of the proposed CMMN-based notational variant, the number of graphical constructs is moderately increased in order to externalize information that is only implicitly or informally represented in standard CMMN (e.g., through textual annotations or comments). Under the assumption of informational equivalence between standard CMMN and models expressed using the notational variant, this change does not introduce additional information but instead redistributes existing semantics into explicit, first-class visual constructs. Consequently, the observed reduction in graphic economy reflects a deliberate trade-off between visual vocabulary size and semantic explicitness rather than a loss of notational efficiency. |
| Cognitive fit | This principle depends on empirical validation with representative users and concrete task contexts and therefore cannot be meaningfully assessed through analytical evaluation alone. |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2026 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license.
Share and Cite
Bule, M.; Polančič, G. Enhancing CMMN: Conceptual Development of a Notational Variant for Case Management Modeling. Systems 2026, 14, 180. https://doi.org/10.3390/systems14020180
Bule M, Polančič G. Enhancing CMMN: Conceptual Development of a Notational Variant for Case Management Modeling. Systems. 2026; 14(2):180. https://doi.org/10.3390/systems14020180
Chicago/Turabian StyleBule, Mateja, and Gregor Polančič. 2026. "Enhancing CMMN: Conceptual Development of a Notational Variant for Case Management Modeling" Systems 14, no. 2: 180. https://doi.org/10.3390/systems14020180
APA StyleBule, M., & Polančič, G. (2026). Enhancing CMMN: Conceptual Development of a Notational Variant for Case Management Modeling. Systems, 14(2), 180. https://doi.org/10.3390/systems14020180





























