|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (4)
View Page History
* The runtime viewpoint (see Subtask 3.3), as part of the ITEmIS service-oriented middleware.
Task 1 3 is decomposed into the following subtasks:
h3. *{_}Subtask 3.1: Workflow modelling{_}*
This subtask will elaborate on the workflow modelling, which will be applied to both the workflow design-time (workflow tooling) and the workflow runtime (workflow engine).

\- Another consideration concerns the meta-models required for the development and deployment of IT/embedded services and ITEmIS workflows. These meta models will be designed to back the following task up from the results of the preceding consideration.
h3. *{_}Subtask 3.2: Workflow tooling{_}*
This subtask will elaborate on a set of tools for the design, development and deployment of IT/embedded services and ITEmIS workflows, based on the workflow modelling provided by the previous subtask. These tools aim to enable agility by supporting the QoS-aware configuration and reconfiguration of workflows for their deployment in an ever-changing heterogeneous networking environment. ITEmIS workflows should be rapidly created, developed, deployed, reconfigured and redeployed.
h3. *{_}Subtask 3.3: Workflow engine{_}*
This subtask will elaborate an advanced workflow engine providing the execution substrate for ITEmIS workflows. ITEmIS workflows to be executed on the engine will be expressed in the ITEmIS workflow specification language provided by Subtask 3.1. The workflow engine will allow run-time integration of the heterogeneous IT/embedded services into ITEmIS workflows, enabling the multi-faceted interoperability and scalability required for ITEmIS systems. Furthermore, the workflow engine will ensure meeting the QoS requirements of workflows by aggregating the QoS provided by the constituent IT/embedded services.