|
|
| |
| |
The initial end-user requirements as well as the specification
report for the beta release are delivered.
Algorithms, tools, candidate systems to interoperate with, necessary
standards, and targeted platforms are selected according to the
end-user requirements and techno watch results.
Scenarios and data for test purpose are available to the developers.
|
|
|
| |
| |
The b release of the system
is developed and provided to end-users for validation.
Validation forms and validation data are available to the users.
Dissemination is limited for confidentiality reasons.
|
|
|
| |
| |
The b release is validated,
thus providing the validation report used to refine specifications
and design for the final version.
Real-cases are proposed by end-users for the validation of the
final release.
Public dissemination is started (conferences, public demonstrations).
|
|
|
| |
| |
The final release of the system is developed and provided to
end-users for final validation
Public dissemination activity is maximised.
|
|
|
| |
| |
The final release is validated. The results of the validation
are exploited in commercial material and a complete software package
is released. A final demonstration is organised.
The report outlining an assessment of the power of the system
as well as its economical impact is released
The system is ready to reach the market. Awareness of “key”
actors in the field is raised, exploitation and business plans
are ready and commercialisation is about to start.
The final report is delivered to the commission.
|
MILESTONES