The main aim of this task is to develop the component-based ITEmIS service engineering tools according to the requirements and architecture defined during the Task 1.
These tools are addressing the whole life cycle of ITEmIS systems encompassing all the design, development, packaging, deployment, and management activities.
Task 4 starts by defining meta-models commonly shared between ITEmIS tools. Then, design, development,deployment, and management tools are built on top of these ITEmIS meta-models.
- Subtask 4.1: Meta-models
The main aim of this subtask is to design and implement ITEmIS meta-models. These meta-models encompass all the needed concepts to describe large-scale, extremely heterogeneous and potentially
embedded ITEmIS systems, for instance, in terms of services, components, ports, interfaces, bindings,etc.
These meta-models allow supporting all the design, development, packaging, deployment, and management activities for building ITEmIS systems.
These meta-models start from:
- The SCA meta-model provided by the ANR SCOrWare project and available in the Eclipse STP SCA subproject (http://www.eclipse.org/stp/sca),
- The ANR Flex-eWare component meta-model,
Then, these meta-models are enhanced according to ITEmIS requirements defined in Task 1.
- Subtask 4.2: Design and development tools
The main aim of this subtask is to design and implement ITEmIS design and development tools. These tools allow designing large-scale heterogeneous SCA-based ITEmIS systems, and defining and
developing individual services and components involved into ITEmIS systems.
These tools start from:
- The SCA tools (Composite Designer, Form Editor and Textual Editor) provided by the ANR SCOrWare project and available in the Eclipse STP SCA subproject,
- The TOPCASED tools: Ecore editors (graphical, textual), AADL editors (graphical, textual),
- The MDE tools developed within the ANR OPENEMBEDD (http://openembedd.inria.fr/) platform.
Then, these tools are enhanced according to ITEmIS requirements defined in Task 1.
Another aspect targeted by this subtask is verification. Based on the ITEmIS meta-models and their required properties, verification models (expressed in the FIACRE language) associated to thebehavioural aspects are generated.
Their properties are automatically handled by the verification engines available within the aforementioned platforms and toolsets (e.g., CADP, TINA).
A deliverable will results from these activities under the form of verification scenarios for the use cases studied in tasks 1 and 5Task 5 of the proposal.
- Subtask 4.3: Deployment tools
The main aim of this subtask is to design and implement ITEmIS deployment tools. The goal is to automate the deployment of large-scale and extremely heterogeneous ITEmIS systems. Here,
deployment encompasses the installation, configuration, launching, and tearing down of any software artefact, taking part of an ITEmIS system, onto any physical node (servers, large and small PDAs, and
micro-devices). Software artefacts are, at least, business ITEmIS services and workflows, but can also encompass the whole ITEmIS infrastructure and workflow engine software stack (and all its software
dependencies) implemented by Tasks 2 and3.
These tools start from those provided by the ANR JOnES and SCOrWare projects, i.e., deployment facilities provided by the ESB PEtALS and by DeployWare/FDF, a framework to deploy large-scale
distributed and heterogeneous software systems automatically (http://fdf.gforge.inria.fr). Then, these tools are enhanced according to ITEmIS requirements defined into Task 1.
- Subtask 4.4: Management tools
The main of this subtask is to design and implement ITEmIS management tools. These tools allow administrating, controlling, reconfiguring, and monitoring large-scale ITEmIS systems encompassing the
whole ITEmIS distributed infrastructure and any business service.
These tools start from the management facilities offered by the ESB PEtALS and implemented by the ANR JOnES and SCOrWare projects. Then, these tools are enhanced according to ITEmIS requirements
defined into Task 1.