Admin: Created page with "{{DISPLAYTITLE: Case Management Modelling and Notation - A how to guide on the new OMG standard}} == Introduction == Case handling has been discussed in the literature since 2..."

2017-01-18T12:59:07Z

Created page with "{{DISPLAYTITLE: Case Management Modelling and Notation - A how to guide on the new OMG standard}} == Introduction == Case handling has been discussed in the literature since 2..."

New page

{{DISPLAYTITLE: Case Management Modelling and Notation - A how to guide on the new OMG standard}}
== Introduction ==
Case handling has been discussed in the literature since 2001, when van der Aalst and Berens described its unique requirements. Case handling aims at supporting knowledge workers with a more flexible process execution by avoiding well known restrictions present in conventional BPM and workflow technology. Examples of such restrictions include rigid control flow, context tunneling and restricted data visibility.

The central concept behind case management modeling is an information model useful to react to data conditions and data state change events. BPMN 2.0 doesn’t have it, and without it, conditional events are not as usable, because the only data visible to them are process variables and properties. The information model includes both data and documents, so changes in values, metadata, and lifecycle state can all be used to model the case.

Case handling is also about empowering participants in a process, by removing context tunneling and providing better support for exception handling. Case handling was considered a difficult use case for process and workflow technology; and among others, Swenson proposed Adaptive Case Management to address the requirements described by van der Aalst et al. In this ‘how to guide’, we use case handling and case management interchangeable as they represent the same use case.

Before arriving to the case handling use case described by van der Aalst and Berens in 2001, other researchers have worked on increasing the flexibility of workflow and process technology. For example, Hull et al. focused on declarative processes in 1998, Kappel et al. focused on the interception between rules and workflow in 1998. Oba and Komoda in 2001 worked on dynamically controlled processes for enterprise application integration.

In 2009, the Object Management Group started the process of standardizing a case management notation to complement its BPMN specification. The result is the Case Management Modeling and Notation (CMMN) specification. This new specification looks at case management from a data centric perspective based on business artifacts, which is a line of research that originates with Niggam and Caswell in 2003, and focus on the artifacts that knowledge workers use to accomplish their work, which in most cases are documents. This ‘how-to guide’ introduces CMMN, describe how it works, where it can be applied, and provides an example.

[[Category: Case Management]]

LEAD Reference Content:Case Management - Introduction - Revision history

Admin: Created page with "{{DISPLAYTITLE: Case Management Modelling and Notation - A how to guide on the new OMG standard}} == Introduction == Case handling has been discussed in the literature since 2..."