Common use of Synchronisation Clause in Contracts

Synchronisation. Specialisation of: • Merge-Control A Synchronisation indicates the merging of several paths back into one. Its inclusion type indicates when the elements following the Synchronisation should be started (i.e. if one, if some or if all of the incoming paths are finished). The Synchronisation itself does not terminate any remaining Actions of the incoming paths4. Subtypes Inclusion type Based on the three available inclusion types, the subtypes can be “of all” (AND), “of some” (OR) or “of one” (XOR). It should be only one of those types. Specialisation of: • Process A Requirements process represents a more detailed description of an Action that focuses on depicting the things that are required by it and how they are used. It can therefore look closer like a workflow than a Business process, and is often created by splitting and merging Actions from a Business process. Specialisation of: • requires This specialisation of requires indicates that the target is necessary to perform something. It is recommended to use this level of detail in the Requirements process. Allowed source concepts: • Elements contained by a Requirements process Allowed target concepts: • Participant template Specialisation of: • requires This specialisation of requires indicates that the target supports performing something, meaning it is good to have it, but even if it is missing you can perform the action. It is recommended to use this level of detail in the Requirements process. Allowed source concepts: • Elements contained by a Requirements process Allowed target concepts: • Participant template Specialisation of: • Process An Interaction flow represents a more detailed description of an Action that centres on depicting the interactions between a device and its user as well as what functions a device is executing. Mostly mobile devices and the interaction with their mobile applications are in the focus.