The figure below represents graphically all the set of Use Cases of OASIS, in a generic diagram.
Figure 62: Generic Use Cases Diagram.
After the UCs were defined and described in detail, they were evaluated and modified by MCA in terms of users interests.
Use Cases analytical descriptions
Following, the analytical Use Cases are described, according to the template (see Annex). For each UC, the relevant UML diagram is also included.
Category 1: Transport information services Pre-trip info SP3-1 Plan a trip2 -
Context of use (aim)
|
The elderly user wants to plan a trip and receive all the information about the journey in an elderly-friendly way.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
| -
Connected UCs
|
| -
Priority Level
|
Essential
| -
Scenario(s)
| -
The user is at home and wants to plan a trip to a place he/she wants to visit for the week end.
-
The user is at home and wants to plan a PT trip to a specific address (e.g. medical center) in the city where he/she lives.
-
The user is outdoors and wishes to walk to a museum nearby but he/she does not know exactly its location.
-
The user is outdoors and wishes to go to his/her home (by inserting the address and bookmarked).
-
The user is at home or outdoors and wishes to plan a trip from address to address or from POI to POI.
| -
System output
|
The system will present to the user the best alternative routes
in a textual format and on a map if requested.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Pre-trip planning on PC, PDA or mobile phone.
|
11b. Sensor devices & restrictions
|
Localisation on PDA, PC, mobile phone (plan a trip from current location only if the user is outdoors).
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Return of alternatives to user within 1 min.
|
| -
Environmental restrictions
|
Plan a trip from current location possible only if the user is outdoor.
| -
Interaction level
|
Step 1 - The user selects the starting point; it can be one of the following:
-
Bookmarked location (e.g. home, hospital)
-
Address or POI
-
Current location (only if outside home)
Step 2 – The user selects trip between:
-
Bookmarked location (e.g. home, recreation centre)
-
Address or POI
Step 3 - The system asks the user whether to use the bookmarked routing options or to insert manually the following preferences:
-
Mean of transport (PT, car, pedestrian)
-
Arrival/starting time
-
Route optimization type (shortest, fastest, calmest)
-
Maximum walking distance
-
Maximum number of changes
Step 4 - The system processes the user’s query and presents zero or more alternative routes in a textual format and optionally on a map.
| -
Personalisation/ adaptation level
|
Yes:
static parameters: static user profile
semi-dynamic parameters: user type
dynamic parameters: preferred route options (maximum walking distance accepted, POIs en route preferences, assistance services en route preference)
| -
Quality of service indicators
|
Return of info < 1min
| -
Potential input needed from other UCs (what input and which UCs?)
| -
User location needed from UC SP3-16 “Find current location” if the user is outdoors.
-
Bookmarked POIs or places should be available from UC SP3-18 “Bookmark POI”.
| -
Important accessibility attributes (per UG)
|
Route textual description: accurate and short in order to facilitate the comprehension.
The system should ask the user (when possible) to print out the selected route description.
When pedestrian segments will be requested, the route will be calculated based on the user profile pedestrian speed (e.g. different pedestrian speeds associated to different user groups)
Take into account the type of disability of the elderly user, if there is one.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
‘Accessible’ routing is demonstrated in ASK-IT; thus, not to be repeated here. However, if relevant content on accessible routes is available, it will be taken into account.
|
Figure 63: SP3-1 Plan a trip
SP3-2 Plan a special attributed trip
-
Context of use (aim)
|
The elderly user intends to plan a ”scenic” or “safe” or “calm” route/ trip to go from one point to another pre-trip and/or on-trip.
| -
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”. Therefore it can also be part of use cases “Be guided en route” and “Look after me”
| -
Priority Level
|
Essential
| -
Scenario(s)
| -
Scenic or safe or calm trip from my “home” to an address
-
Scenic or safe or calm trip from my current position to the address of my hotel.
-
Scenic or safe or calm trip from my current position to my “home” (book marked).
-
Scenic or safe or calm trip from address to address or from POI to POI
| -
System output
|
A list of scenic or safe or calm (to this user) routes to go from origin to destination through via points, together with estimated trip time. Suggested POIs are given in addition en route or at destination, if asked for. Scenic or safe or calm route segments are shown. The user should be able to click on partially scenic, safe and/or calm route segments to view the attributes or update them. In case scenic, safe and/ or information are not available, the user will get a normal trip plan and an indication about the lack of these specific data.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
Route guidance
| -
Devices & restrictions
|
PDA, PC
11a. User Interaction devices & restrictions
|
|
11b. Sensor devices & restrictions
|
Localization module
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
|
Route guidance
|
Return of optimal 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
| -
The user requests a scenic or safe or calm trip from origin to destination through via points.
-
The user defines start time of trip and (optionally or alternatively) the desired arrival time.
-
The system returns a list of suggested scenic or safe or calm trips, clearly listing and showing the scenic safe or calm attributes of each trip segment. Info on map and with text.
| -
Personalisation/ adaptation level
|
Yes:
static parameters: static user profile
semi-dynamic parameters: user type
dynamic parameters: preferred route ( maximum walking distance accepted, maximum number of transport mode changes accepted, taxi preference, POIs en route preferences, assistance services en route preferences)
environmental parameters/context of use: driving
| -
Quality of service indicators
|
Return of route < 5min
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
Guidance avoiding heavy traffic, through calm and pleasure grounds
-
Always best possible accuracy
-
Special speed profiles will be available for certain user groups, e.g. one for pedestrians, one for cars, etc.
-
Depending on the type, safe, scenic and calm attributes must be available in the databases of the service providers and attached to the geographic road network.
-
POI’s en route can be self-selected having as default the last route selection by the user (initially) and user preferences (later, when the users dynamic profile is available).
Take into account the type of disability of the elderly user, if there is one.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Figure 64: SP3-2 Plan a special attributed trip
SP3-3 Get destination information
-
Context of use (aim)
|
The elderly user has planned a trip and wishes to have information about the selected destination like nearest hotels, parking, touristic places, elderly associations, medical centers, etc.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
| -
Connected UCs
|
“Plan a trip”, “Search nearest POIs”
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The user is at home or outdoor, has just planned a trip and wants to know more about the place he/she is going to visit. The user asks for touristic information about the destination of the planned trip.
The elderly user has health problems (e.g. diabetes, cardiopathies), and has just planned a trip to a city he/she has never been. The user needs to know what are the medical centers he/she can receive assistance.
| -
System output
|
The system provides destination information requested in a textual and visual (map) way.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
PDA, PC
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Return of info to user within 5 min.
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – After having planned a trip, the user selects the option “get destination info”
Step 2 – The user chooses the POI categories like touristic, transport, health care, etc. or decides to have the information on POI categories bookmarked on his/her profile.
Step 3 – The user can select the maximum distance from the destination for proximity search or alternatively the system takes this parameters from the user profile.
Step 4 - The system processes the user request and returns the found POIs around the destination both in a textual and in a graphical way (map)
| -
Personalisation/ adaptation level
|
Yes:
static parameters: static user profile
semi-dynamic parameters: user type
dynamic parameters: preferred POIs options
environmental parameters/context of use: if travelling by car, the system proposes also the nearest parking spaces.
| -
Quality of service indicators
|
Return of info < 5min
| -
Potential input needed from other UCs (what input and which UCs?)
|
Required “plan a trip” output since the route destination must be available.
Required “proximity search” to get POI information around the route destination.
| -
Important accessibility attributes (per UG)
|
Take into account the type of disability of the elderly user, if there is one. E.g., if such info is available, restaurants with special menu for people with diabetes as they might be registered as POI.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Figure 65: SP3-3 Get destination information
SP3-4 Get additional route information
-
Context of use (aim)
|
The elderly user has planned a trip and wants to have more information about the POIs along the selected route.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
Health care and emergency support service providers
Leisure and re-creation service providers
| -
Connected UCs
|
“Plan a trip”, “Search nearest POIs”
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The user has planned a long trip by car and wishes to know where are the gas stations and car services along the route.
The user has planned a trip and wishes to know if there are restaurants with specific characteristics the use likes/dislikes.
| -
System output
|
The system provides the details about the found POIs along the planned route.
| -
Relevant OASIS WP
|
WP3.3
| -
Services involved
|
Transport information
Route guidance
Tourism support
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
PDA, PC
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Return of info to user within 5 min.
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – After having planned a trip, the user selects the option “get more trip info”
Step 2 – The user selects the POI categories like touristic, transport, health care, etc. or decides to ask for the POI categories bookmarked on his/her profile.
Step 3 - The system processes the user request and return the found POIs along the selected route in a textual and graphical way (map)
| -
Personalisation/ adaptation level
|
Yes:
static parameters: static user profile
semi-dynamic parameters: user type
dynamic parameters: preferred POIs options
environmental parameters/context of use: if travelling by car, the system proposes also the fuel stations and car services along the route.
| -
Quality of service indicators
|
Return of info < 5min
| -
Potential input needed from other UCs (what input and which UCs?)
|
Depends from “plan a trip” UC since the planned route must be available.
| -
Important accessibility attributes (per UG)
|
Take into account the type of disability of the elderly user, if there is one.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Figure 66: SP3-4 Get additional route information
Short range trip info SP3-5 Get short trip info
-
Context of use (aim)
|
The elderly user gets accurate information when planning a short trip (city level).
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
Other: PT operator
| -
Connected UCs
|
Plan a trip
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The elderly user is not motorized and travels by bus or by walk taking a PDA with himself/herself to receive information about the short trip already planned, like PT timetables, estimated arrival times, social recreation events.
| -
System output
|
The system pushes to the user the preferred information with a short description as the user is already familiar with the area of the short range trip.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Mobile phone, PDA, PC
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Timetables should be correct, so accuracy is crucial here.
|
Route guidance
|
|
Driver telematic support
|
|
Driver comfort support
|
|
Tourism support
|
|
Leisure and social activities support
|
Social recreation events are associated with this.
|
Smart workplaces
|
|
| -
Environmental restrictions
|
None.
| -
Interaction level
|
Step 1 – The user selects select the short trip he/she is interested to receive information of.
Step 2 – The system asks the user to select a set of categories present in the nearby living places (touristic, recreation, medical…) or to use the bookmarked.
Step 3 – The system provides all selected information while the user in on the selected short range trip.
| -
Personalisation/ adaptation level
|
Yes:
static parameters: static user profile
semi-dynamic parameters: user type
dynamic parameters: preferred route (POI categories, selected mean of transport)
environmental parameters/context of use: the route can be re-planned after receiving short range trip information.
| -
Quality of service indicators
|
Return of info < 5min
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
Take into account the type of disability of the elderly user, if there is one. An elderly person with a walking stick might be quicker taking 2 different trains, but it might be better to suggest 1 train which is maybe slower but avoids hasty and sometimes difficult (read: dangerous) walks from and to different platforms. Again, accessible routing will be supported only if relevant content exists, as it has been already demonstrated in ASK-IT project.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Figure 67: SP3-5 Get short trip info
Info in stations and hubs SP3-6 Get Public Transport Timetables
-
Context of use (aim)
|
The elderly user wants to get information on public transport timetables for a specific line or stop.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
| -
Connected UCs
|
Can be connected to “find nearest stop”
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The elderly user is at home or anywhere (i.e. on a journey) and wishes to view or print out the timetables of the nearest stop because later he/she will decide to go out for a walk in the city centre or he/she is already out looking for means to continue his/her journey.
| -
System output
|
The system presents to the user the selected line/stop timetable in a tabular format.
If no timetables information is available for the selected date/time, the system shows a message of “no information available” to the user.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Mobile phone, PDA, PC
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
The system successfully contacts the local PT transport information provider and returns information to the user within 5 min.
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – the user selects the desired line from a list
Step 2 (optional) – the user selects the desired stop of the line selected at step 1
Step 3 – the user select the date/time of interest
Step 4 – the user asks for timetable information
Step 5 – the system collect all the requested information
Step 6 – the system provides to the user the available timetables information
| -
Personalisation/ adaptation level
|
Yes:
static parameters: static user profile
semi-dynamic parameters: user type
| -
Quality of service indicators
|
Return of info < 5min
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
PT Stop accessibility information needed.
| -
Background info/ reason on selection and on assigning the priority level
|
The user can access information about PT timetables in a personalized way (graphical user interface adapted to his/her preferences/disabilities) and not only through a web portal /timetables book, but also while he/she is outside (e.g. using a PDA).
| -
References
|
| -
Comments
|
|
Figure 68: SP3-6 Get public transport timetables
TMIC interface SP3-7 Get real time traffic information
-
Context of use (aim)
|
The elderly user wishes to know what is the current traffic situation in a selected street or geographic area.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
Other: TMIC operator
| -
Connected UCs
|
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The elderly user has to go to an administrative office in the afternoon but before leaving home would be informed about the current traffic situation as he may decides to postpone the trip.
| -
System output
|
The system presents to the user a list and optionally a map with the traffic events found.
If there are no events, the system shows a message to the user informing that there are no traffic events found for the selected area/street.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Mobile phones, PDA, PC
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Traffic events returned within 5 min.
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1a - The elderly user selects the road of interest from a list or asks for the bookmarked streets
Step 1b – The elderly user selects a geographic area of interest (address + radius)
Step 2 – The elderly user asks for traffic events in that area/road
Step 3 – The system returns all the events found.
| -
Personalisation/ adaptation level
|
Yes:
static parameters: user profile
semi-dynamic parameters: user type
| -
Quality of service indicators
|
Return of info < 5min
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
User physical restricitons to be taken into account.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
The user should be able to select the type of traffic events that are being shown. E.g. someone using a bike is less interested in traffic jams, than someone conducting his/her car. If a road is broken up, than that is totally different.
|
Figure 69: SP3-7 Get real time traffic info
-
-
Context of use (aim)
|
The elderly user is on-trip and a disruption happens along the planned route. The system notifies the user about this unexpected condition and the re-plan the trip.
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
Other: TMIC operator
| -
Connected UCs
|
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The elderly user is still working and wants to be informed in advance if there are traffic events on the street he/she usually covers when going at work.
The elderly user is travelling to a touristic place and an accident happens on the highway he will have to take, the system re-plans the trip and the user avoid the congested area.
| -
System output
|
The system provides information about unexpected trip events on a specific route.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
Mobile phone, PDA, PC
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
The system successfully contacts the local PT transport information provider and returns information to the user within 5 min.
|
| -
Environmental restrictions
|
| -
Interaction level
|
| -
Personalisation/ adaptation level
|
Yes:
static parameters: static user profile
semi-dynamic parameters: user type
dynamic parameters: preferred route: assistance service on traffic events as en route preference
environmental parameters/context of use: real time traffic conditions may affect the user trip
| -
Quality of service indicators
|
Return of info < 5min
| -
Potential input needed from other UCs (what input and which UCs?)
|
“Plan a trip” is required in order to provide events on a specific route.
| -
Important accessibility attributes (per UG)
|
The re-routing must take into account the type of disability of the elderly user, if there is one.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Figure 70: SP3-8 Get unexpected trip events while on trip
Long-range trip info SP3-9 Long-range trip info
-
Context of use (aim)
|
To provide accurate and efficient information on long trips (metropolitan areas, region/interurban level) to all elderly users
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
| -
Connected UCs
|
Plan a PT Trip
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The user has already asked the system to plan a public transport trip and the system has returned at least one possible solution. So, the output of the “Plan a PT trip” use case is used as input for this use case, in particular the intermediary terminals and trip segments returned by the trip planning algorithm. These segments may include travelling with interurban buses/trains for metropolitan areas, etc. An option for pedestrian routing may also exist (e.g. beginning and ending of the route by foot).
| -
System output
|
The system must provide optimal and detailed long range trip information (region/interurban level) to the elderly user concerning terminals and trip segments special services.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
PC, mobile phone, PDA
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Provide accurate and efficient information to the elderly user.
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – the select a possible solution returned by the system because of a “Plan a PT trip” request
Step 2 – The GUI presents a set of options to be defined by the user in order to get specific results, like information for terminals and trip segments special services
Step 3 – The system acquires the data and the GUI presents it to the user in an elderly-friendly way. The results may concern travelling in a metropolitan area, in another city or country, etc.
Step 4 – The user can refine his/her search or ask for another long-range trip
| -
Personalisation/ adaptation level
|
Yes:
static parameters: adapted UI to potential disabilities
semi-dynamic parameters: type of traveler
dynamic parameters: preferred special service
environmental parameters/context of use: perhaps adapted route according to real time traffic data and type of disability
| -
Quality of service indicators
|
Provide accurate long-range trip information to the elderly user.
| -
Potential input needed from other UCs (what input and which UCs?)
|
Terminal information
| -
Important accessibility attributes (per UG)
|
Take into account the type of disability of the elderly user, if there is one.
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Figure 71: SP3-9 Long-range trip info
Multimodal trip planning SP3-10 Multimodal trip planning
-
Context of use (aim)
|
To plan a PT trip efficiently and accurately
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Service Centre
| -
Connected UCs
|
Plan a Trip
| -
Priority Level
|
Essential
| -
Scenario(s)
|
The user has to enter the place of origin and destination and the desired date and time. Then he/she has to choose the desired modes of transport and optionally define other options like the maximum waiting time at each terminal, the maximum number of trip legs etc
| -
System output
|
The system must provide optimal and detailed multi modal PT trip planning information to the elderly user.
| -
Relevant OASIS WP
|
WP3
| -
Services involved
|
Transport information
| -
Devices & restrictions
|
11a. User Interaction devices & restrictions
|
PC, mobile phone, pda
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
Provide accurate and efficient information to the elderly user.
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 1 – The user initiates a request for a PT trip
Step 2 – The user provides origin, destination, date and time information for the desired trip along with detailed information concerning the desired modes use and optionally some supplementary details
Step 4 – The system executes the trip planning algorithm and the graphical interface presents the returned solutions to the user
Step 5 – The user can refine his/her search, ask for another trip or restart the “Plan a trip” asking for a different type of solution, such as Demand Responsive Transport service or Rent a special car service
| -
Personalisation/ adaptation level
|
Yes:
static parameters: adapted UI to potential disabilities
semi-dynamic parameters: type of traveller
dynamic parameters: preferred time and route
environmental parameters/context of use: perhaps adapted route according to real time traffic data
| -
Quality of service indicators
|
Calculate optimal route in order to satisfy user demands. Provide accurate information to the elderly user.
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
Take into account the type of disability of the elderly user, if there is one
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Figure 72: SP3-10 Multimodal trip planning
Share with your friends: |
