process-flexibility.com

Wednesday, 12 June 2013 15:50

Pattern AP2: DELETE Process Fragment

The Delete Process Fragment pattern can be used to remove a process fragment. No additional design choices are needed for this pattern. There exist alternative ways in which this pattern can be implemented. The first implementation option is to delete the respective process fragment, i.e, to remove the corresponding nodes and control edges from the process schema. The second implementation option replaces the fragment by one or more silent activities (i.e., activities without associated action). In the third implementation option, the fragment is embedded in a conditional branch, which is then never executed (i.e., the fragment remains part of the schema, but will not be executed).

Description

A process fragment is deleted from a process schema S.

Example

For a particular patient a planned computer tomography must not be performed in the context of her treatment process as she has a cardiac pacemaker, i.e., the computer tomography activity is deleted.

Problem

In a real world process a planned task has to be skipped or deleted.

AP2

Implementation

This adaptation pattern can be realized by transforming the high level delete operation into a sequence of low level change primitives (e.g., remove node, remove edge). Implementation options include the deletion of the fragment from the process schema, the replacement of the fragment by a silent  activity or the embedding of the fragment in a conditional branch which is never executed.

Animation

View Animation

Read 835 times
 

Get the Book!

book cover small