1SAFEPROBE Plenary Meeting2006-12-06, Torino

T1.2.3 RequirementsT1.2.3 Requirements

Andreas Ekfjorden

Volvo (Sweden) andreas.ekfjorden@volvo.com

SAFEPROBESAFEPROBESAFEPROBESAFEPROBE

2SAFEPROBE Plenary Meeting2006-12-06, Torino

Current Status

• The actual requirements list has been checked (and refined) in several iterations.

• Some analysis has been done – covers all parts of the D122 UseCase diagram– Some Doubles have been removed but not all– Almost all requirements are directed to SP1, hand over some to

SP3 seem to be needed? Discussion needed– Requirements from SP4 may need to be transferred to SP3, this

has to be handled in Specifications process.

• The word document is in a first draft format but needs more descriptions.

• No formal Crosschecking has been done!

3SAFEPROBE Plenary Meeting2006-12-06, Torino

• The SAFEPROBE Platform in the World

SAFEPROBE Platform

OEM HMI

RSU

4SAFEPROBE Plenary Meeting2006-12-06, Torino

Common language for requirements

• Each requirement shall have a unique English name (it is not the case now)

• Slippery Road– Ice, gravel, snow, oil on the road etc

• GNSS – Satellite navigation systems: GPS, Galileo etc

• Change “Beacon” to “Transponder” in a vehicle?

5SAFEPROBE Plenary Meeting2006-12-06, Torino

Specific Requirements

• UTC as time standard for DF?• Volvo have added a “minimum platform”

requirement– “It shall be possible to install a limited platform on any vehicle only using a

minimal adaptation.” – Rationale: “A vehicle shall not need to carry a full sensor setup to

function as a SF vehicle. The minimum setup is the Platform, Short range communication and GNSS capabilities. A minimal set of vehicle data may be needed (TBD - Speed, Yawrate)”

• Slippery Road and Road Departure– Several proposals exist, can we use the term

Slippery road and rewrite? (next slide)

6SAFEPROBE Plenary Meeting2006-12-06, Torino

Slippery Road Req. from UC

SP1_UC_01_26Possibility of road

departure detected by ego vehicle

The system shall detect areas of reduced friction (due to slippery road conditions) and put the information in the LDM

SP1_UC_01_26Possibility of road

departure detected by infrastructure

The system shall be able to receive information on the road condition from the infrastructure and put the information on the LDM

SP1_UC_01_27Possibility of road

departure communicated

If information on low friction on the road is in the LDM, this information shall be sent to other vehicles and the infrastucture

SP1_UC_04_026Low friction detected by

ego vehicleThe system shall detect areas of reduced friction

and put the information in the LDM

SP1_UC_04_027Low friction detected by

infrastructure

The system shall be able to receive information on the road condition from the infrastructure and put the information on the LDM

SP1_UC_04_028Low friction

communicated

If information on low friction on the road is in the LDM, this information shall be sent to other vehicles and the infrastructure

7SAFEPROBE Plenary Meeting2006-12-06, Torino

• Unclear requirement:

SP1_UC_51_27

Road geometry calculation with sensors

The system shall help road geometry calculation with information from sensors

8SAFEPROBE Plenary Meeting2006-12-06, Torino

Architecture dependent

SP1_UC_06_007 Digital Map

The system must have a (static) digital map and the should be cooperable with the local dynamic map.

SP1_HW_51_35

Screen capabilities

(HMI)

The screen shall have graphic capabilities, with TBDxTBD pixels and TBD colors at least.

SP1_SW_05_10

Data Structure and Format

Documentation

The structure and format of all in-vehicle platform data exchanged

between major (tbd) modules shall be documented using XML

This is an SP7 issue?

• This should be kept in mind for the architecture discussion?

9SAFEPROBE Plenary Meeting2006-12-06, Torino

To Do Next

• Finish the D1.2.3– Add an introduction on the SAFEPROBE platform in

the SAFESPOT system – Fuller description on the introduction to the

requirements lists – The authors– “Cleaning up” unambiguous names and to extensive

explanations – Volvo and requirements originators

• Crosschecking with SP2,3,4,5,7– Should this a part of the specifications process and

will not be included in the deliverable.

• Standard msg development – separate task

10SAFEPROBE Plenary Meeting2006-12-06, Torino

Finishing of D1.2.3

• 1:st Draft (Word) for comments– out Friday afternoon– Comments and additions by– Second draft out– Comment by 19/12– Peer review delivery 20/12

• Final draft out for comments (Excel list) Monday afternoon

11SAFEPROBE Plenary Meeting2006-12-06, Torino

SP4 Requirements

• The list from SP4 with SP1 Requirements is 77 items long!

• Critical items - 59.

• SP4 requirements