Common use of App execution set-up Scope Clause in Contracts

App execution set-up Scope. The main focus of this Scope is on the description of app orchestrations, by specifying the sequences of app executions and the possible paths in an orchestration similar to a process. This description follows a similar process based structure to the one used in other Scopes, to allow facilitate the alignment with them. Since it describes an orchestration on a mobile device (“local” orchestration) and mobile devices are usually not switching the user (everybody uses their own mobile device), a collaboration of several such “local” orchestrations might be necessary to properly implement a business or requirements process. The major groups used here are: The Orchestration group describes the execution of apps to achieve a certain goal. Concept Comment Orchestration Additional constraints of an execution engine on what is allowed should be considered here. They however depend on the used execution engine. App execution A core element for describing an orchestration. It can be considered an action of type “execution”. Can also depict other orchestrations. Event Can be used and reused in other processes to provide points of reference between different processes. Halt Path split Used to split a path. Consider splitting one path into several (i.e. not an XOR split) to be similar to creating multiple threads in programming. Synchronisation Used to merge paths. executes (executed in) Replaces the requires relation to only focus on the app that is executed. notifies (notified by) Replaces the impacts relation to only focus on notifications between orchestrations. followed by (preceded by) The aspect-specific concept, to specify the sequence and conditions for the flow. detailed by (describes) The aspect-specific concept, to decompose actions into a finer granularity. has part (part of) The aspect-specific concept, to state what is contained by an interaction flow. influences (influenced by) The inter-aspect concept, to specify what values are consumed or produced. The Notification exchange group describes what notifications are exchanged between which orchestrations. The involved participants are handled through the procedural elements used here. Notification exchange It describes the notifications between several orchestrations, so it is also for several actions. contains (contained by) The general concept, to decompose a collaboration into its contents. is for (has collaboration) The inter-aspect concept, to indicate on which actions the collaboration is based on. The following groups should also be available in this Scope:  Value structure group (Table 14) – Should be used to describe what an orchestration achieves and what it consumes/wastes.  Mobile support structure group (Table 25) – In this Scope the mobile support structure is mostly used to state which apps are executed in an orchestration.  Information space group (Table 26) – Can be used here to describe the messages/notifications that are sent in an orchestration. One of the goals of this Scope is to provide input, with some additional adaptations outside of the specification, to workflow or orchestration execution engines. However, some execution engines might not be able to handle all of the possible cases that can be modelled (e.g. splitting of one thread into several, OR-splits, more than one entry in an orchestration etc.). Therefore the abilities of the chosen engine should be considered when creating orchestration models.

App execution set-up Scope. ‌ The main focus of this Scope is on the description of app orchestrations, by specifying the sequences of app executions and the possible paths in an orchestration similar to a process. This description follows a similar process based structure to the one used in other Scopes, to allow facilitate the alignment with them. Since it describes an orchestration on a mobile device (“local” orchestration) and mobile devices are usually not switching the user (everybody uses their own mobile device), a collaboration of several such “local” orchestrations might be necessary to properly implement a business or requirements process. The major groups used here are: The Orchestration group describes the execution of apps to achieve a certain goal. Concept Comment Orchestration Additional constraints of an execution engine on what is allowed should be considered here. They however depend on the used execution engine. App execution A core element for describing an orchestration. It can be considered an action of type “execution”. Can also depict other orchestrations. Event Can be used and reused in other processes to provide points of reference between different processes. Halt Path split Used to split a path. Consider splitting one path into several (i.e. not an XOR split) to be similar to creating multiple threads in programming. Synchronisation Used to merge paths. executes (executed in) Replaces the requires relation to only focus on the app that is executed. notifies (notified by) Replaces the impacts relation to only focus on notifications between orchestrations. followed by (preceded by) The aspect-specific concept, to specify the sequence and conditions for the flow. detailed by (describes) The aspect-specific concept, to decompose actions into a finer granularity. has part (part of) The aspect-specific concept, to state what is contained by an interaction flow. influences (influenced by) The inter-aspect concept, to specify what values are consumed or produced. The Notification exchange group describes what notifications are exchanged between which orchestrations. The involved participants are handled through the procedural elements used here. Notification exchange It describes the notifications between several orchestrations, so it is also for several actions. contains (contained by) The general concept, to decompose a collaboration into its contents. is for (has collaboration) The inter-aspect concept, to indicate on which actions the collaboration is based on. The following groups should also be available in this Scope:  Value structure group (Table 14) – Should be used to describe what an orchestration achieves and what it consumes/wastes.  Mobile support structure group (Table 25) – In this Scope the mobile support structure is mostly used to state which apps are executed in an orchestration.  Information space group (Table 26) – Can be used here to describe the messages/notifications that are sent in an orchestration. One of the goals of this Scope is to provide input, with some additional adaptations outside of the specification, to workflow or orchestration execution engines. However, some execution engines might not be able to handle all of the possible cases that can be modelled (e.g. splitting of one thread into several, OR-splits, more than one entry in an orchestration etc.). Therefore the abilities of the chosen engine should be considered when creating orchestration models.