|
|
|
|
A multi-model process for managing project complexity |
|
|
|
|
|
|
|
|
|
Developers of large software systems have to face an exponential increase in the volume and complexity of the requisite knowledge, together with tighter time constraints and a continually growing number of stakeholders. Current solutions are based on breaking the system down into smaller pieces in order to be able to handle them, but a side effect of this approach is to weaken the overall view of the system.
The full paper (see link below) presents a model centric process supported by tools, which has been implemented in various application domains such as air traffic control (EUROCONTROL, FAA), aeronautics (Airbus) and automatic railway systems (Siemens). This process is based on a multi-model approach for managing synthetic views and making project information available to all stakeholders, with an appropriate view and presentation.
The objectives of the process are to:
- urge project members to structure and formalise their knowledge and their system view by the means of connected models (Requirements, Architecture, Component, Deployment, Interface / Communication and Equipment / Execution Platform),
- allow teamwork by sharing and synchronising relevant information,
- produce adapted models that contain linked information necessary for a specific task,
- manage dependencies and consistency between the different models, especially when their development lifecycles are different,
- establish and evaluate impacts and costs linked to changes,
- produce an up-to-date status of project developments
|
|
|
The process is supported by a tool called the Multi-Model Editor (MME). The concepts used by each type of stakeholder are defined through meta-models. MME provides import, export and filtering capabilities, which support merging, linking and “gluing” of information coming from various documents or models produced by different tools.
Initial feedback from various projects shows that the multi-model process allows better communication between teams: each participant works with his own tools or languages but can share a subset of the information he manages with other teams by means of integration models. The tool provides an efficient support to the propagation of modifications among the different views. Above all, this approach allows multiple and consistent views of the system to be built, so recovering control of their development, extension and maintenance.
|
|
|
|
| |
|
 |
|
Author:
Last validation: 12/02/2008
|
|
|
|
|
|
|
|
