5. Modeling approach
IMPERATIVE MODELLING DECLARATIVE MODELLING
FORCING PATH OF HOW IT HAS
TO BE DONE
SUPPORTING FRAME OF WHAT
CAN BE DONE
CLEAR DEFINED SEQUENCE OF
TASKS
CLEAR DEFINED GOALS
6. How to describe the real world?
Modeling notations
Business Process
Model and Notation
Case Management
Model and Notation
Decision
Model and Notation
• Languages for describing operations
• Means to an end
• Notation tools not solutions
7. Core differences
Processes Cases Decisions
Activities Events Rules
Sequence flow Context and information Applied explicit knowledge
Token automation Event – condition - action First order logic (rules)
9. Adaptive Case Management
1
2
3
45
6
7 Collaboration
AdaptiveEvery case
follows its own
path
Centralisation of
information
Monitoring
& Planning
Goal oriented
Knowledge work
10. General concept
Planning at run-time is a fundamental characteristic of Case management
DESIGN TIME MODELING
During design time, business analysts
model and define:
‐ Plan items: items that are always part of
the case
‐ Discretionary items: items to be applied
‘ad-hoc’ to the user his/her discretion
RUN TIME PLANNING
During run time, case workers handle the
case by:
‐ executing (starting/planning/…) the plan
items at runtime
‐ adding discretionary items at runtime
11. Task
Discretionar
y task
Cocktail order
Milestone
Entry criterion
Exit criterion
User event
listener
Timer event
listener
On part connector
Discretionary
association
Text annotation
Case file item
updat
e
Recipe
-
Review
menu
card
Stage
-
Discretionary
stage
-
Processing
occur
Cancel
order
Served
Ordered
Mixed
Take
order
complet
e
Choose
appropriat
e glass
Add
liquor
Add ice
Add
spirit
Add
fruits
Add
herbs
Calculate
price
Deliver
receipt
Process
payment
occur complet
e
complet
e
Shake
Stir
occur
1 hour
after
serving
Add
bitters
!
#
#
Case Plan
Model
Task types
Human blocking
Human non-blocking
Process
Decision
Case
Required rule
Repetition rule
Manual activation
rule
Autocomplete
Planning table
!
#
Decorators
CMMN IS PROPERTY OF
OBJECT MANAGEMENT GROUP, INC.
ALL RIGHTS RESERVED
!
There are many solutions available for transactional processes, but what happens if you try to implement these in volatile and event-driven situations?
BPMN vs CMMN ;
Process management starts with the hypothesis that all possible scenario’s can be defined. This leaves (too) little room for flexibility during the process execution. The result is a rigid (bureaucratic?) process that takes away control of the operators (knowledge workers). Furthermore it leaves no room to adapt the process based on new context or insights.
For standard processes this works perfectly. You’ll hit a limit as soon as you are confronted with processed where exceptions, variation, and change are the rule rather than the exception.
Case management starts with the premise that the case worker should be in the driver’s seat, taking decisions on the fly due to events or additional information. Thereby steering the ‘case’ towards the best possible resolution, given the context of events & information.
Do note we are not letting the case worker wander in a Desert – bound by no rules or obligations.
The biggest discussion is about BPMN vs. CMMN, although designed to be complementary!!!
This poster aims to explain the core concepts of CMMN in a straightforward way. For this purpose we have rebranded it the Cocktail Making Model & Notation. Our ‘case’ explains the different stages, tasks, and milestones that occur when someone orders a cocktail. Feel free to check our website (www.groundlion.com) to find out how CMMN can help you with adaptive case management.
This poster explains the core concepts of CMMN in a straightforward way. CMMN is the standard notation for graphically modelling all ‘event-condition-action’ logic that is required to manage cases. It shows the plan (toolbox) for supporting knowledge-intensive work when sequence of activity is contextual. Check www.groundlion.com to find out how CMMN and adaptive case management can help.
Recieved, in research, in decission, approved, not approved, untill finally resolved/completed