PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf

Final Report PRE-DRIVE C2X 29.9.2010
objective was set on enabling combined traffic-communication-application
scenarios. The requirements are selected in several categories, traffic, driving,
communication and applications simulators have been identified as the main
categories. Nevertheless in order to support integrated simulations, requirements for
a simulation integration platform, its functionalities and interface requirements
between simulators have to be considered. Requirements are serving as the basis
for the evaluation of existing tools and as preparation for the application simulation
scenarios. A requirements template has been developed to capture all requirements
in a consistent manner.
Code Type Description
REQ.SAR.007
F
The simulation
architecture shall allow
an overall scenario
minimum length that
considers the use case
relevant region.
Applicable
Element
Traffic
simulator
Simulation
model
Priority
M
Dependency
Justification
The length of the scenario
has to be enough to cover
the use case relevant
region.
Table 1: Requirements template and requirements example
Table 1 shows an example of the requirements template and an example of a
requirement (REQ) on the simulation architecture (SAR) with number 7. Each of the
template categories has been defined. In the case of the example the requirement
(explained from left to right) has a unique code “REQ.SAR.007”, a type “functional
(F)” a description, the applicable element of the integrated simulation architecture
“Traffic simulator”, no applicable simulation model, the priority level identified
“mandatory (M)”, there are no dependencies to other requirements and a
justification for the requirement. A detailed explanation of the categories is given in
Deliverable 2.1 “Description of user needs and requirements, and evaluation of
existing tools”. With this method around 30 general requirements on the simulator
interfaces, 50 against the simulation architecture functionalities and in average 16
requirements towards each selected application scenario were identified.
Deliverable D2.1 “Description of user needs and requirements, and evaluation of
existing tools” describes in detail the collection of user needs, the resulting
requirements and the simulators investigated.
2.3.2.2 Available simulation tools
The list of available simulation tools lead to a total of
eight detailed descriptions of traffic models
seven detailed descriptions of communications models
eleven “other” tools (environment, architecture, driving simulators)
Plus further available tools outside the project
Deliverable D0.3 Version 1.0 30
Final Report