Information Technology Reference
In-Depth Information
engine
that invokes the tools specified in the process model and ensures
the proper handling of the related artefacts. This way the process devel-
oper is able to focus on the semantics of the tool-chain without dealing
with specific lower level notations and configuration options of the exe-
cution engine.
- Model-based execution and supervision of tool-chains. Aman-
agement interface is provided that uses the platform specific model for
the execution of the tool-chains, and the platform independent model as
the interface to the system developer who executes the process.
- Data integration. The artefacts processed and generated by a tool-
chain are handled as an integral part of the process: these are represented
explicitly in the models, are stored in persistent data repositories, and
the download and upload are managed automatically.
- Definition of a flexible framework. In the architecture key compo-
nents are identified independently of the underlying technology. For the
implementation of the components high level, modern technologies having
strong industrial support are used if possible. Between the components
interfaces are defined in order to be able to change the implementation
technology.
- Traceability of processes. Certification of the developed system is a
need in case of safety-critical systems, thus all steps executed during the
development process with all the data handled shall be documented and
be able to traced back upon request.
The paper is organized as follows: the architecture of the framework with
key components is described in Section 2. In the next section details about
the implementation are provided, while Sec. 4 demonstrates the concepts in
a model based test case generation case study. Finally we conclude our work.
2
Architecture of the Tool Integration Framework
Basedonourresearchanddevelopmentexperienceandontherelatedworks
in the field we have identified the key components that are needed to fulfil
the goals described in the introduction. The architecture is depicted in Fig. 1.
The components can be grouped into four categories: process modeling, tool
management, data management, and process execution.
Tool Management.
A
Too l
represents an executable program that performs
one or more tasks during the development. Tools are independent of the
framework and can be implemented in different languages and according to
different technologies (e.g., also as web service). The only requirement is to
have the functionality exposed as a well-defined interface which is externally
accessible.
For each tool a
Connector
shall be implemented which exposes the func-
tionality of the tools as services. Connectors are usually simple wrapper
