Wednesday, 12 June 2013 15:57

Pattern AP3: MOVE Process Fragment

The Move Process Fragment pattern allows users to shift a process fragment from its current position to a new one. Like for the Insert Process Fragment pattern, an additional design choice specifies the way the fragment can be re-embedded in the process schema afterwards. Although the Move Process Fragment pattern could be realized by the combined use of AP1 and AP2 (Insert/Delete Process Fragment) or be based on change primitives, we introduce it as separate pattern, since it provides a higher level of abstraction to users.


A process fragment is moved from its current position in process schema S to another position within the same schema.


Usually employees may only book a flight after it has been approved by the manager. Exceptionally, for a particular process the booking of a flight shall be done in parallel to the approval activity; consequently the book flight activity has to be moved from its current position in the process to a position parallel to the approval activity.


Predefined ordering constraints cannot be completely satisfied for a set of activities.

Design Choices 

in addition to the General Design Choices

C. How is the shifted process fragment X re-embedded in S?

  1.  X is re-inserted between two directly succeeding activities (serial move)
  2.  X is re-inserted between two activity sets (move between node sets)
    1. without additional condition (parallel move)
    2. with additional condition (conditional move)



This adaptation pattern can be implemented based on patterns AP1 and AP2 (insert / delete process fragment) or be based on change primitives (e.g., add/remove node, add/remove edge).

Related Patterns

Swap adaptation pattern (AP5)


View Sequential Animation

View Parallel Animation

View Conditional Animation

Read 1123 times

Get the Book!

book cover small