download deliverable - AIDE

Deliverable D4.2.1 Dissemination Level PU Contract N. IST-1-507674-IP
3.9. Track I: AIDE Scenarios and Functions (morning session, attendance list can be
found in Annex A)
Chairman: Johan Engstrom, VOLVO
Angelos Amditis, ICCS
3.9.1. Summary
A presentation of the adopted methodology towards the derivation of AIDE design
scenarios was made. The key elements which, combined, constitute an AIDE design scenario
description were addressed one by one. In order to explain the format of the scenarios’
description, a description of the key terms used by subproject 3 of AIDE project was
presented through the presentation of the AIDE glossary. More specifically, the following
terms were discussed: AIDE design scenario, Driver-Vehicle-Environment conditions,
Actions, AIDE meta-functions, driver distraction, driving demand, and application.
The description of the adopted methodology involves mainly three of the
aforementioned terms: Actions, Driver-Vehicle-Environment conditions and AIDE
metafunctions. The first two represent the driver-vehicle interaction in various driver-vehicleenvironment
states, whereas the last one represents the system’s general solution to the
possible action or condition depending conflict.
3.9.2. Methodology adopted for the derivation of the AIDE design scenarios
Having in mind the adaptive characteristics that AIDE project envisions to adopt
towards a real-time adaptive HMI design and development, the design of the driver/vehicle
dialogue should be based on clear scenario descriptions, able to represent not only the set of
interactions between systems and the driver, but also the rationale behind system’s adaptivity.
While standard use case templates are mainly intended for individual IVIS/ADAS functions
(e.g. route guidance, phone, ACC, collision warning etc.), the AIDE system will implement
“meta-functions” that supports the interaction between a large number of such functions and
the driver (e.g. resolving conflicts between functions and enabling adaptation of individual
functions). Thus, the standard use case methodology is not applicable. Still, in order to derive
the AIDE requirements and specifications, we need a parsimonious way to describe the use
cases and scenarios that AIDE will address. Such a methodology does not currently exist and
thus had to be worked out in the project.
Action categorization – required steps:
• Define a set of basic parameters that can be used to characterize the actions
AIDE action = f (initiator, duration, safety criticality, time criticality, real time,
mandatory, driving relevance, preference)
• Assign the parameters to the considered actions (list of 50 AIDE actions)
• Three classes are derived from the in-vehicle HMI expert point of view considering
the individual interaction content:
•Warnings, which present very urgent information to the driver and which comes mainly
from driving assistance systems like a lane departure warning system or collision avoidance
25/07/2005 30 ICCS