PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf
PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf
PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Final</strong> Report <strong>PRE</strong>-<strong>DRIVE</strong> <strong>C2X</strong> 29.9.2010<br />
users outside of the project, whom the partners are cooperating with (e.g. road<br />
operators).<br />
2.2.2.2 Requirements for a comprehensive tool set<br />
The “Requirements for a comprehensive tool set” were very closely related to the<br />
use cases defined in WP4000 “Methodologies and tools for field operational tests”.<br />
Firstly, a template for the description of requirements was distributed to the partners<br />
in this task. Each partner generated the requirements for the use case(s) most<br />
relevant for their institution. This process assured that the requirements came from<br />
those partners who are concerned with the realization of the use cases, and were<br />
not only theoretically derived. This ensured the practicality of the results.<br />
Furthermore, during the process of compiling the requirements it was decided that<br />
the structure of the document should reflect different levels of requirements. This<br />
second step of a two-step approach developed during the process of working in this<br />
area was then agreed between the partners and led to a more refined compilation<br />
than originally planned.<br />
The collection of the requirements for the comprehensive tool set proved to be more<br />
effort-intensive than originally thought. The requirements derived from the user<br />
needs were discussed within the group of partners, actually between all partners<br />
and not only between the ones involved according to the work plan. This discussion<br />
proved to be very fruitful and led to a wider definition of “requirements”. It was found<br />
that different levels of requirements can be distinguished. This led to a second round<br />
of requirement collection that was originally not foreseen. In this collection of<br />
requirements practically all partners of WP2000 were involved. This was the<br />
preferred approach in order to identify a sound and widely accepted set of<br />
requirements. Although this process led to a delay compared to the original work<br />
plan it was considered worthwhile to spend extra effort here instead of postponing to<br />
the succeeding WPs when discussion would start again.<br />
2.2.2.3 Evaluation of existing tools and identification of gaps<br />
The work on “Evaluation of existing tools and identification of gaps” started with an<br />
initial discussion of the procedure. While the evaluation will be based on the<br />
requirements, a structured approach was defined before the work on requirements<br />
was concluded.<br />
The actual first work item here was the creation of a comprehensive template into<br />
which all partners involved were able to include the information on available tools.<br />
This template was first drafted and then finalized in discussions among some of the<br />
involved parties. The process greatly benefited from the experience of the partners.<br />
In the end, a very detailed and comprehensive compilation of available simulation<br />
tools in all categories (communication, traffic and environment) was generated. Not<br />
only the models developed and/or owned by the partners but also models developed<br />
by other institutions were included in this compilation.<br />
This approach especially adds to the value of the work even beyond the <strong>PRE</strong>-<br />
<strong>DRIVE</strong> <strong>C2X</strong> project. Similar activities were already carried out much earlier, e.g. by<br />
the SMARTEST project and efforts in very early ITS development phases (e.g. like<br />
in PROMETHEUS). The compilation produced is considered a very valuable<br />
collection of information.<br />
<strong>Deliverable</strong> <strong>D0.3</strong> Version 1.0 6<br />
<strong>Final</strong> Report