![]() Instead of forcing the process modeler to define a specific order that all of the tasks happen in, CMMN gives each activity a condition upon which they start or complete. This was viewed as too restrictive for case management. It was assumed that’s a problem with BPMN was that activities were linked up in a specific unchanging order like the way a car factory links up work into a single assembly line. CMMN aimed to be a declarative model of the process. CMMN was aimed at meeting more flexible and more tuned to the ever-changing requirements in an organization. This motivated an alternative approach to modeling processes known as Case Management Model and Notation (CMMN). The last post pointed to limitations in BPMN, and this post covers CMMN.īy 2010 we began to understand the flaw of representing a processes as a static imperative diagram. This is another installment in the series on how we need to move beyond process models for automating work. Version 1.0 of CMMN was released in May 2014 and amended by Version 1.1 in December 2016.We knew that BPMN needed fixing, but CMMN didn’t fix it enough. While BPMN deals with predictable processes, CMMN is more oriented to focus on supporting processes that are intrinsically unpredictable, not repeatable, weakly-structured, and knowledge-intensive.Ī consortium of 11 companies contributed to the development of CMMN, which is now being maintained by the Object Management Group. In this context: "A Case is a proceeding that involves actions taken regarding a subject in a particular situation to achieve a desired outcome" and it is derived from the concept of Case management used e.g. Case Management Model and Notation ( CMMN) is a graphical representation for graphically expressing a Case, as well as an interchange format for exchanging Case models among different tools. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |