To provide elderly driver-friendly in car (on-board & off-board) navigation, avoiding heavy traffic and specific (difficult) traffic scenarios to enhance elderly drivers safety and comfort.
Primary actor
Young elderly (ages 55-65) – perhaps
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre (for off-board navigation)
Other: rest traffic participants
Connected UCs
-
Priority Level
Essential
Scenario(s)
The user asks for navigation/route guidance and expects to get back a route that is “safe” and “comfortable”. The system has its own definition for “safe” and “comfortable” for an elderly driver (i.e. through calm traffic, avoiding traffic jams, haptic roundabouts, U-turns, T-junctions, etc.). The user may have the possibility to add/extract some of these features, thus personalizing the system (through tick-boxes).
The user will be able to see his/her position relative to his/her destination and selected POI.
In-vehicle navigation system (on-board) and/or PDA-based navigation (off-board)
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Route guidance
New route found more comfortable and safe than default routing by at least 50% of elderly users and not worse by more than 20%.
Environmental restrictions
Existence of adapted maps with elderly-friendly routes
Interaction level
Step 1 – the user asks for pre-defined route guidance and selects the elderly-friendly option.
Step 2 - the system provides point-by-point guidance, according to the embedded rules.
(Potentially also Step 0 – the user defines at the beginning his/her preferences on routing personalisation, ticking on/off some boxes)
Personalisation/ adaptation level
Yes:
static parameters
Quality of service indicators
Time demands: the new route does not enhance the overall journey time over …% (could be pre-selected or defined by the elderly user him/herself, as an option).
Reliability/accuracy demands: as a ‘standard’ navigation system.
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
The HMI should be the standard of the navigation device, plus a very effective and easy to use personalization screen.
But also the profile of the user should be considered, as this will have its impact on the HMI, and the specific route that might be suggested.
Background info/ reason on selection and on assigning the priority level
Relevant elderly drivers enhanced accident rates in specific traffic scenario (i.e. at T-junctions) and wish to drive more slowly and calmly.
The elderly user intends to plan a trip by car or is driving. Parking availability info near destination or current position is provided.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre
Other: Parking information (price, location, etc) providers
Connected UCs
This use case provide navigation features that can be used from another use cases:
“Plan a special attributed trip”.
“Be guided en route/trip”
Priority Level
Secondary
Scenario(s)
Trip from start point to a parking near the final destination.
While driving, find a parking (the nearest, cheapest, etc).
System output
A list of the parkings available is shown to user, it also can be displayed on the map. More specific information can be displayed for each output: walking distance/time to final destination, price, etc.
Relevant OASIS WP
WP3
Services involved
Transport information
Route guidance
Driver telematic support
Devices & restrictions
11a. User Interaction devices & restrictions
Ιn-car PC
11b. Sensor devices & restrictions
Localization module
Critical success parameters
Services
Success parameters
Transport information
Return the more convenient parking places within the time restriction of main route UCs.
Route guidance
Equal as the main UC that requested the service.
Driver telematic support
If after 2 minutes no parking information is obtained, only the local map information is shown.
Indoors, MOTES or NFC or WLAN or RFID or Bluetooth, etc.
Interaction level
The user is planning a trip by car or is driving and wants to find a parking, and has decided that he/she wants to know the parking availability.
The user has to configure (pre-configured values can be used) the maximum acceptable walking distance/time, price, etc.
A list of parkings available is provided to the user. They can also be displayed on the map, referenced to the destination point (if planning a trip) or to the current position (if driving).
For each parking place more specific information can be provided (price, number of places, opening time/dates, company, etc).
The user chooses one of these options.
If planning a trip, the parking is added to the route. If driving the driver is guided to the parking.
dynamic parameters: maximum walking distance/time accepted, maximum price accepted.
environmental parameters/context of use: weather forecast, day and hour (to check parking opening/closing time/date)
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
The destination/current position has to be provided to the service centre to initiate a parking search.
The list of parking places has to be provided from the POI database, and additional information from a Service provider.
Important accessibility attributes (per UG)
If the user dynamic profile detects a user limitation on walking distance, the application will take this automatically as maximum walking distance.
The definition of a max. walking distance, price, opening and closing times should not lead to the suppression of alternatives. It should always be the user’s decision if he/she wants to accept a result or not.
Background info/ reason on selection and on assigning the priority level
SP3-13 Be guided en route / trip (previously planned)
Context of use (aim)
The user activates the guidance on a pre-planned trip / route. This may be automatically activated, if so planned. The system monitors the user and provides support and guidance en route.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre
Connected UCs
This use case can only follow use case “Plan a trip” or “Plan a special attributed trip”. It is related to use case “Look after me” (but with known destination) and shows constantly use case “Find current location”.
Priority Level
Essential
Scenario(s)
Track the users movements if he/she has enabled this function
Re-plan my trip / route if there is a disruption of service (triggered by the user, not by the system!).
Show my position relative to my destination and selected POI
Show me where I am in my trip / route
System output
The actual position of the user is shown on the trip (default in a map) – optional (user may disable it). Relevant POI’s (requested when planning the trip or according to his/her own profile) are shown en route. Pushed information on interesting POIs or service disruption (upon user request) is possible.
Relevant OASIS WP
WP3
Services involved
Transport information
Route guidance
Devices & restrictions
PDA, PC
11a. User Interaction devices & restrictions
11b. Sensor devices & restrictions
Localisation module
Critical success parameters
Services
Success parameters
Route guidance
Follow-up of user and provide point-by-point guidance until (elderly) user reaches destination. If signal is lost the system tries continuously to find user location and recalculate route. If the user deviates from route, automatic route recalculation, using the same criteria of elderly-friendliness.
Environmental restrictions
Outdoors, with GPS connection
Indoors, MOTES or NFC or WLAN or RFID or Bluetooth, etc.
Interaction level
The user requests (or requested in the past) to be guided on a planned route / trip.
The system provides user monitoring and active guidance (i.e. re-planning the route in case of user deviation or service disruption). Also, re-planning or user advice in case of estimated delayed arrival at destination.
The system provides the user with pulled / pushed info on POI’s / services en route if he/she asked for them in his/her user profile)
The service is terminated when the user reaches destination or aborts the trip.
Personalisation/ adaptation level
Yes:
static parameters: static user profile
semi-dynamic parameters: type of user
dynamic parameters: user preferences on POI’s/ Services en route
environmental parameters/context of use: driving
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
Use case “Plan a trip” or “Plan a special attributed trip” is needed for this use case. The trip is planned before activating the guidance en route.
Important accessibility attributes (per UG)
Guidance avoiding heavy traffic, through calm and pleasure grounds.
The system should also consider the disability the user may have, so should connect with the user profile POIs (if relevant content on accessible routing is available).
Background info/ reason on selection and on assigning the priority level
References
Comments
Figure 75: SP3-13 Be guided en route/tip (previously planned)
SP3-14 Bookmark route
Context of use (aim)
The user wants to store a route/trip (current or planned), or load a stored route and change certain parameter settings.
This UC is applicable both for drivers and pedestrians.
1. Use a stored route as a starting point to plan a new one, to save time.
2. Do the same trip again.
3. Store current trip.
5. Delete a stored route.
6. Change some data of a stored route on purpose, for privacy reasons.
7. Store a planned route/trip.
System output
The system allows the user to store, view, modify, annotate or delete a route.
Relevant OASIS WP
WP3.3
Services involved
Transport information
√Route guidance
Driver telematic support
Driver comfort support
Tourism support
Leisure and social activities support
Smart workplaces
Devices & restrictions
< the devices that are needed for the specific UC, e.g. PDA, mobile phone, …as well as possible limitations>
11a. User Interaction devices & restrictions
All OASIS devices
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Transport information
The system keeps the route as bookmarked
Route guidance
Driver telematic support
Driver comfort support
Tourism support
Leisure and social activities support
Smart workplaces
Environmental restrictions
Deactivation of certain user actions if the user is driving (for safety reasons).
Interaction level
step 1: The user stores or consults the stored routes.
step 2: The user finds a stored route he/she wants to manage.
step 3: The user activates the selected route providing a new start time.
step 4: The user modifies, deletes or annotates the selected route.
step 5: The user may annotate stored POIs to the stored route.
Personalisation/ adaptation level
√Yes:
√static parameters: static user profile
semi-dynamic parameters: …………………..
dynamic parameters: …………………..
√environmental parameters/context of use: driving
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
The user searches for stored route according to some criteria (to be defined).
Frequent routes may be stored as “my favourites” (creation of shortcuts may be possible).
Selected routes should be able to be allocated a specific short-name by the user.
Only the bookmark and delete functions (and even these with “shortcut”) should be possibly activated while driving (no modification or annotation).
Background info/ reason on selection and on assigning the priority level
References
Comments
Figure 76: SP3-14 Bookmark route
SP3-15 Look after me
1. Context of use (aim)
The user asks the system to locate him/her and monitor his/her movements, assisting also if he/she requests to use an OASIS service. The user’s location is not previously drawn; it is being drawn in real time (following user’s movements).
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre
Connected UCs
Several use cases can be triggered – connected to it such as use case “Be guided en route/ trip”, “Find current location”.
Priority Level
Essential
Scenario(s)
I am afraid to get lost and not be able to return to my hotel. Monitor my movements,
I am wandering around and want to be notified about interesting POI’s / events along my route. Monitor and inform me according to my preferences / profiles.
System output
The system provides in a map the user’s position and progressively builds the route, showing en route selected POI’s (either requested by the user or according to his/her dynamic profile).
Relevant OASIS WP
WP3
Services involved
Route guidance
Devices & restrictions
11a. User Interaction devices & restrictions
PDA, PC
11b. Sensor devices & restrictions
Localisation module
Critical success parameters
Services
Success parameters
Transport information
Route guidance
If signal is lost the system tries continuously to find user location and to monitor him/ her. The location is being drawn in real time related to user’s movements.
Environmental restrictions
Outdoors, with GPS connection
Indoors, MOTES or NFC or WLAN or RFID or Bluetooth, etc.
Interaction level
The user asks to be localised and followed / assisted from this time onwards (always “now” as time default)
The system provides to the user his/her current location on map and informs him/her that he/she is being monitored. As he/she moves, it shows his/her movements on the map.
The system notifies the user on interesting (according to his/her dynamic profile or upon user request) POI’s / services en route.
The user pauses or stops the UC. If he/she pauses it, it may be re-activated later, without showing the route / actions performed in between.
Personalisation/ adaptation level
Yes:
static parameters: static user profile
dynamic parameters: user POI/ events/ service preferences
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
Possible disability of user should be considered (see comment).
Background info/ reason on selection and on assigning the priority level
References
Comments
Link to user profile to be aware of specific disability elderly user (walking, sight, hearing impairment, even if very mild), so maybe warnings should be provided here about accessibility for certain destinations, places, routes. This, only in case relevant accessibility info already exists in the connected service.
Figure 77: SP3-15 Look after me
SP3-16 Find current location
Context of use (aim)
The user wants to find current location, whether during a planned trip or at any instance.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre
Connected UCs
Current position can be selected by the user as start point for starting a new trip/ route (use case “Plan a trip or “Plan a special attributed trip”) or start being monitored (use case “Look after me”)
Priority Level
Essential
Scenario(s)
“Where am I?” (I am lost).
“Where am I?” (in relation to my active trip).
“Where am I?” (How far have I gone from my hotel or scheduled route?).
System output
The system shows the user location on the map (default) and notes if it coincides with any POI of his/her planned trip or other. In addition it can be a postal address. The UI may present the results to the user in additional different ways. Provides also current time indication to the user (in case he/she wants to know where he/she is in relation to how near he/she is to his her destination?. Also shows start and destination if active trip is on. Reverse geocoding provides the users position as postal address (minimum street name). In addition he receives information on the signal integrity and the position accuracy.
Relevant OASIS WP
WP3
Services involved
Route guidance
Devices & restrictions
11a. User Interaction devices & restrictions
PDA
11b. Sensor devices & restrictions
Localisation module
Critical success parameters
Services
Success parameters
Route guidance
If signal is lost the system tries continuously to find user location.
Environmental restrictions
Outdoors, with GPS connection
Indoors, MOTES or NFC or WLAN or RFID or Bluetooth, etc.
Interaction level
The user asks where he/she is.
The system provides location on the map or as postal address and correlates it to his/her current trip segment POI’s (if any) and other relevant POI’s (if any).
The accuracy of the position is about 15m or 3m. This depends on the localization module (e.g. GPS 15m; Motes 3m)
The system checks automatically for the best positioning technique available in the user’s current environment.
Integrity of the signal if possible
Personalisation/ adaptation level
Yes:
static parameters: static user profile (including e.g. how to display the position)
environmental parameters/context of use: out-door, in-door
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
Presentation of the position to the user in different ways through the UI according to his disability (e.g. voice output, vibration adapted UI)
Background info/ reason on selection and on assigning the priority level
References
Comments
Figure 78: SP316 Find current location
SP3-17 Get information on ways to reach POI types as pedestrian
Context of use (aim)
The user wants to be informed on how to reach a specific POI as pedestrian using a safe, calm or scenic route. It can be also seen as sub-UC of use cases “Plan a trip” and respectively “Plan a special attributed trip” with only one transportation mean; on foot. It is separated only because relevant info is sparse, difficult to get and maintain credibly. Thus, it requires additional attention
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre
Connected UCs
This is a sub-use case of use case “Plan a trip” and respectively “Plan a special attributed trip”. It can be part of use cases “Be guided en route” and “Look after me”.
Priority Level
Essential
Scenario(s)
How can I reach the museum of modern art on foot?
Is it a good idea to walk to the city centre?
Can I return to my hotel on foot?
System output
The system draws alternative safe, calm and/or scenic routes to the specific POI from the start point (default: current user position). Each route may have safe, calm and/or scenic segments. Each alternative route will be shown on an own map and can be viewed by the user via click on the appropriate button. On each route the length in km and the estimated walking time (adapted to the estimated specific users speed) is given.
Relevant OASIS WP
WP3
Services involved
Route guidance
Devices & restrictions
11a. User Interaction devices & restrictions
PDA, PC
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Route guidance
Return of alternative route to user within 5 min. If the signal is lost the system tries continuously to find user location and to re-calculate the route.
Environmental restrictions
Outdoors, with GPS connection
Indoors, MOTES or NFC or WLAN or RFID or Bluetooth, etc.
Interaction level
User requests info on safe, calm and/or scenic routes to reach a specific POI on foot.
User selects safe or/and calm or/and scenic route.
User gets all safe, calm and/or scenic routes on a own map, with safe, calm and/or scenic attributes able to be viewed, plus the length and estimated walking time per segment and for the overall route.
Personalisation/ adaptation level
Yes:
static parameters: static user profile
semi-dynamic parameters: type of user
dynamic parameters: maximum walking distance accepted, preferred POI’s
environmental parameters/context of use: weather forecast
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
If the user dynamic profile detects a user limitation on walking distance, the exceeding route will get a note, highlighting to the user that the walking distance seems too long for him/her.
The definition of a max. walking distance of e.g. 500m should not lead to the suppression of alternatives further away, e.g. 800m. It should always be the users decision if the wants to accept a result or not.
Background info/ reason on selection and on assigning the priority level
References
Comments
Clear link is needed to user profile where e.g. disability, preferences, etc. are stored (if relevant info is available).
Figure 79: SP3-17 Get information on ways to reach POI types as pedestrian
SP3-18 Bookmark a POI
Context of use (aim)
The user wants to bookmark, retrieve, check the attributes of, delete, annotate or change the attributes of a stored POI (POI’s: locations, buildings, venues….).
This UC is applicable mainly for pedestrians, but also partly applicable for drivers.
Formal care-givers (both inpatient and outpatient)
Public / private Social security service providers and insurance companies
Service Centre
Health care and emergency support service providers
Home automation service providers
Leisure and re-creation service providers
Infotainment service providers
Telematic service providers
Elderly associations
National, local and regional authorities
Policy makers
Other: ……………………………………………………….
Connected UCs
Priority Level
√ Essential Secondary Supportive
Scenario(s)
The user finds POI and bookmarks it. Then, The user is able to consult, change or annotate the information on the POI. Finally, the user may delete the stored POI.
System output
The system allows the user to store a POI, view, modify (personalise) its attributes (i.e. add his/her personal view on them, such as accessibility for him/her), bookmarks, or deletes it.
Relevant OASIS WP
WP3.3
Services involved
Transport information
√Route guidance
Driver telematic support
Driver comfort support
Tourism support
Leisure and social activities support
Smart workplaces
Devices & restrictions
11a. User Interaction devices & restrictions
All OASIS devices
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Transport information
The system keeps the PI as bookmarked
Route guidance
Driver telematic support
Driver comfort support
Tourism support
Leisure and social activities support
Smart workplaces
Environmental restrictions
Interaction level
1. User wants to bookmark a POI to find it again (i.e. nice restaurant).
2. User wants to bookmark his/her home to later plan trips from it.
3. User wants to bookmark a POI to be able to return to it while wandering around (i.e. his/her hotel).
4. User wants to delete a stored POI.
5. User wants to modify attributes of a stored POI, to reflect his / her own opinion on them (i.e. accessibility in relation to personal abilities and requirements).
6. User wants to annotate specific services / new attributes / name to a POI.
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
- Only the store and delete functions should be active while driving (no modification or annotation).
- The POI should contain accessibility information clearly visible to the user.
Background info/ reason on selection and on assigning the priority level
References
Comments
Figure 80: SP3-18 Bookmark a POI
SP3-19 Disruption of service notification and re-planning
Context of use (aim)
Due to a deviation of the user from the planned trip, the planned trip is disrupted and it is not possible to be realized as planned. The user is notified and he may re-plan the trip (if the user wishes automatically).
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre
Connected UCs
It is closely connected to use cases “Plan a trip”, “Plan a special attributed trip”, “Be guided en route” and it is also related to use case “Look after me”.
Priority Level
Secondary
Scenario(s)
User goes shopping in a shopping mall while trip. User deviates from the route…
User changes the transport mode and goes by bus. He/she deviates from the planned route..
User has lost the orientation and deviates from the route…
System output
The system notifies the user and asks if he/she wants to activate the re-planning option. Warning is highlighted if the user is already en route and milder if it is related to a planned trip.
Relevant OASIS WP
WP3
Services involved
Route guidance
Devices & restrictions
11a. User Interaction devices & restrictions
PDA, PC
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Route guidance
Return of re-planned route to user within 5 min. If the signal is lost the system tries continuously to find user location and to calculate the route.
Environmental restrictions
Outdoors, with GPS connection
Indoors, MOTES or NFC or WLAN or RFID or Bluetooth, etc.
Interaction level
Service notifies deviation of the user from the planned route and asks for user feedback (e.g. updating or new planning; for example to return to home or find alternatives ).
Personalisation/ adaptation level
Yes:
static parameters: static user profile
semi-dynamic parameters: type of user
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
Background info/ reason on selection and on assigning the priority level
References
Comments
Replanning must be matched with the user profile, so as to ensure that replanned route is still feasible for the user e.g. in term of walking distance.
Figure 81: SP3-19 Disruption of service notification and re-planning
SP3-20 Dynamic map update
Context of use (aim)
The elderly user gets an actual map with attributes which are related to scenic, calm and/ or safe route.
Primary actor
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
Secondary actor(s)
Service Centre
Connected UCs
This use case is related to use case “remote deployment“.
Priority Level
Secondary
Scenario(s)
Show safe route on a map
Show scenic route on a map
Show calm route on a map
Show actual changes on a map
System output
The system showssafe, calm and/or scenic routes on the map. Dynamic changes are provided on the map as well.
Relevant OASIS WP
WP3
Services involved
Route guidance
Devices & restrictions
11a. User Interaction devices & restrictions
PDA, PC
11b. Sensor devices & restrictions
Critical success parameters
Services
Success parameters
Transport information
Route guidance
Real time update of map.
Driver telematic support
Driver comfort support
Tourism support
Leisure and social activities support
Smart workplaces
Environmental restrictions
Scenic, safe and calm attributes available.
Interaction level
User requests a map update.
User requests route which is shown on a map with safe, calm and/or scenic attributes and has considered dynamic changes of map segments.
User gets all safe, calm and/or scenic routes on a map, with safe, calm and/or scenic attributes able to be viewed.
Personalisation/ adaptation level
Yes:
static parameters: static user profile
dynamic parameters: changes of map attributes/ segments
environmental parameters/context of use: heavy traffic intersections, pleasure grounds etc.
Quality of service indicators
Potential input needed from other UCs (what input and which UCs?)
Important accessibility attributes (per UG)
Avoiding heavy traffic, through calm and pleasure grounds, etc.
Background info/ reason on selection and on assigning the priority level
