An Event Listener is depicted by a double line circle shape.Event Listeners are used to model events that do not happen to plan items.Anything that can happen to Stages, Tasks and Milestones.Anything that can happen to information in the Case File.CMMN predefines many events, and their causes: An event is something that "happens" during the course of a Case.A Milestone may have zero or more entry criteria, which define, when a milestone is reached.A Milestone is depicted by a rectangle shape with half-rounded ends.
No work is directly associated with a Milestone, but completion of set of tasks or the availability of key deliverables (information in the Case File) typically leads to achieving a Milestone. A Milestone is a Plan Item Definition that represents an achievable target, defined to enable evaluation of progress of the Case. It is depicted by a rectangle with rounded corners and a "User" symbol in the upper left corner.Ī Case Task is depicted by rectangle shape with rounded corners with a "Folder" symbol in the upper left corner and they can be used to call another Case 
It is depicted by a rectangle with rounded corners and a "Hand" symbol in the upper left corner.
A discretionary Task is depicted by a rectangle shape with dashed lines and rounded corners. A Task is depicted by a rectangle shape with rounded corners. When the Stage is expanded it is depicted by a rectangle shape with angled corners and a marker in the form of a "-" sign in a small box at its bottom center. A Stage is depicted by a rectangle shape with angled corners and a marker in the form of a "+" sign in a small box at its bottom center. Stages maybe considered "episodes" of a Case. Stages are Plan Fragments that can be tracked. The name of the Case can be enclosed into the upper left rectangle. A Case Plan Model is depicted using a "Folder" shape that consists of a rectangle with an upper left smaller rectangle attached to it. The complete behavior model of a Case is captured in a Case Plan Model. Graphical Notation (Discretionary task on right) Two human event listeners are used to complete the Claim File Case by directly go to the exit or through the last Milestone - Claim Processed. Process task contained inside the Identify Responsibilities Stage and the Case File directly, they are: the Identify Responsibility Process and Create Letter Process. Each of the Case (Claim File), Attach Base Information Stage and Process Claim stage has a planning table Decorator attached to it which means that each of these container elements contains one or more discretionary element in it. Once completed the Responsibilities Identified Milestone, the second stage - Attach base information can be started. The Responsibility Identified Milestone can optionally perform the human task (blocking and discretionary) - Change Responsibilities which may need to be repeated (# sign). The Identify Responsibilities stage contains one process called identify Responsibilities which is "required" to complete or terminate before their containing Stage (in this case, Identified Responsibility Stage) can complete (! sign). There is a entry sentry attached to each of the three milestones. There are three milestones based on three stages in the example:. 
Now, let's take a first glance of CMMN using the example by going through the following 8 steps: The OMG Case Management Model and Notation (CMMN) is a declarative modeling language that provides an agile and dynamic way to address the situations that may happen within a context, known as a case.īy drawing a CMMN diagram, you can visualize the events that may happen in the context of a case, the tasks involved, the milestones, etc.
Business scenarios can be highly dynamic in that the workflow involved and the outcomes depend a lot on ad-hoc decisions and business events.
0 kommentar(er)
