7 Seamless Travel Use Cases v2.0
7.6 Airport
7.6.7 Pax Info - Baggage tag and drop options to passenger UseCase in package 'Airport'
Page 96 of 234
7.6.7 Pax Info - Baggage tag and drop options to passenger
Page 97 of 234
7.6.7.1 Pax Info - Baggage tag and drop options to passenger_ActivityGraph
Activity owned by 'Pax Info - Baggage tag and drop options to passenger', in package 'Airport'
Figure 58: Pax Info - Baggage tag and drop options to passenger_ActivityGraph Start
Airline and airport prov ide information about baggage options.
End-user receiv es information.
End
Page 98 of 234
7.6.7.2 Pax Info - Baggage tag and drop options to passenger_SequenceDiagram
Interaction owned by 'Pax Info - Baggage tag and drop options to passenger', in package 'Airport'
1_Basic_Path
Interaction diagram in package 'Airport'
Figure 59: 1_Basic_Path
Airline: Airline Airport: Airport User: User
2.End-user receives information.() 1.Airline and airport provide information about baggage options.()
Page 99 of 234
7.6.8 Pax Info - Gate information
UseCase in package 'Airport'
Element Notes
USE CASE ID: 1.8.5
USE CASE DESCRIPTION:
receive information on Gate number
ACTORS (GOAL):
The airline and the airport provide information on gate number. The application consumes the information
PERFORMANCE GOALS:
PRE CONDITIONS:
POST CONDITIONS:
SCENARIO:
1. A partner requests information about the gate number 2. The airline provides the information
3. End user receives information
EXTENSION POINT:
ALTERNATIVE SCENARIO:
RELATED REQUIREMENTS:
RELATED RULES:
PERFORMANCE MEASURES:
VERSION/HISTORY:
0.1; 28.5.15; Lücking; created
0.2; 5.6.15; Rogal; More detailed description
0.3; 10.6.15; Stiffel; Find services at default, current or selected airport (workshop result)
Page 100 of 234
7.6.8.1 Pax Info - Gate information_ActivityGraph
Activity owned by 'Pax Info - Gate information', in package 'Airport'
Figure 60: Pax Info - Gate information_ActivityGraph Start
A partner requests information about the
gate number
The airline prov ides the information
End user receiv es information
End
Page 101 of 234
7.6.8.2 Pax Info - Gate information_SequenceDiagram
Interaction owned by 'Pax Info - Gate information', in package 'Airport'
1_Basic_Path
Interaction diagram in package 'Airport'
Figure 61: 1_Basic_Path
Airline: Airline User: User
2.The airline provides the information()
3.End user receives information()
Page 102 of 234
7.6.9 Pax Info - Security screening regulations
UseCase in package 'Airport'Element Notes
USE CASE ID: 1.8.4
USE CASE DESCRIPTION:
receive information on security screening regulations
ACTORS (GOAL):
The screening authority provides information on restricted/prohibited items and divest information. The application consumes the information
PERFORMANCE GOALS:
PRE CONDITIONS:
POST CONDITIONS:
SCENARIO:
1. A partner requests information about security and screening regulations 2. The screening authority provides the information
3. End user receives information
EXTENSION POINT:
ALTERNATIVE SCENARIO:
RELATED REQUIREMENTS:
RELATED RULES:
PERFORMANCE MEASURES:
VERSION/HISTORY:
0.1; 28.5.15; Rogal; created
0.2; 5.6.15; Rogal; More detailed description
0.3; 10.6.15; Stiffel; Service listing for default, current or selected airport (workshop result)
Page 103 of 234
7.6.9.1 Pax Info - Security screening regulations_ActivityGraph
Activity owned by 'Pax Info - Security screening regulations', in package 'Airport'
Figure 62: Pax Info - Security screening regulations_ActivityGraph Start
A partner requests information about security and screening
regulations
The screening authority prov ides the information
End user receiv es information
End
Page 104 of 234
7.6.9.2 Pax Info - Security screening regulations_SequenceDiagram
Interaction owned by 'Pax Info - Security screening regulations', in package 'Airport'
1_Basic_Path
Interaction diagram in package 'Airport'
Figure 63: 1_Basic_Path User: User
3.End user receives information()
Page 105 of 234
7.6.10 Pax Info - Security waiting times
UseCase in package 'Airport'
Element Notes
USE CASE ID: 1.8.3
USE CASE DESCRIPTION:
Fetch airport information on security waiting times
ACTORS (GOAL):
The airport provides information about security waiting times.
The application consumes the information.
PERFORMANCE GOALS:
PRE CONDITIONS:
POST CONDITIONS:
SCENARIO:
1. A partner requests information about security waiting times information.
2. The information is provided by the airport.
3. End-user will be offered an option to buy security fast track (if not yet included).
EXTENSION POINT:
ALTERNATIVE SCENARIO:
RELATED REQUIREMENTS:
RELATED RULES:
PERFORMANCE MEASURES:
VERSION/HISTORY:
0.1; 28.5.15; Lücking; created
0.2; 5.6.15; Rogal; More detailed description
0.3; 10.6.15; Stiffel; Agreement to add sub use cases (workshop result) 0.4; 25.06.15; Stiffel; added description & scenario
Page 106 of 234
7.6.10.1 Pax Info - Security waiting times_ActivityGraph
Activity owned by 'Pax Info - Security waiting times', in package 'Airport'
Figure 64: Pax Info - Security waiting times_ActivityGraph Start
A partner requests information about security w aiting times
information.
The information is prov ided by the airport.
End-user w ill be offered an option to buy security
fast track (if not yet included).
End
Page 107 of 234
7.6.10.2 Pax Info - Security waiting times_SequenceDiagram
Interaction owned by 'Pax Info - Security waiting times', in package 'Airport'
1_Basic_Path
Interaction diagram in package 'Airport'
Figure 65: 1_Basic_Path
Airport: Airport User: User
2.The information is provided by the airport.()
3.End-user will be offered an option to buy security fast track (if not yet included).
Page 108 of 234
7.6.11 Search Airport Services
UseCase in package 'Airport'
Element Notes
USE CASE ID: 2.3
USE CASE DESCRIPTION:
The user wants to search for a specific service. To make it easy to find a service the user can search via a single search field.
ACTORS (GOAL):
The user wants to search services by entering some search criteria.
The application tries to generate a result-list which should be ordered by calculated relevance of the result-items.
Therefore different service fields have different importance for calculating the relevance. E.g. the title is more important than the description.
PERFORMANCE GOALS:
PRE CONDITIONS:
The user has an account for the seamless travel platform.
The user has selected a default or current airport
POST CONDITIONS:
SCENARIO:
1. The user opens the service overview 2. The application shows a search bar
3. The user types a search string into the search bar and presses enter 4. The system searches for all services fitting to the search request
5. The application displays the matching services as list ordered by relevance
EXTENSION POINT:
ALTERNATIVE SCENARIO:
If the user hasn’t selected a default or current airport, the first step is that the application asks the user which Airport should be used.
RELATED REQUIREMENTS:
RELATED RULES:
PERFORMANCE MEASURES:
VERSION/HISTORY:
0.1; 28.5.15; Rogal; created 0.2; 9.6.15; Lücking; added flow
Page 109 of 234
7.6.11.1 Search Airport Services_ActivityGraph
Activity owned by 'Search Airport Services', in package 'Airport'
Page 110 of 234
Start
Alternate1
If the user hasn’t selected a default or current airport, the first
step is that the application asks the user
w hich Airport should be used.
The user opens the serv ice ov erv iew
The application show s a search bar
The user types a search string into the search bar
and presses enter
The system searches for all serv ices fitting to the
search request
The application displays the matching serv ices
as list ordered by relev ance
End
[Alternative Path]
Page 111 of 234
Figure 66: Search Airport Services_ActivityGraph
7.6.11.2 Search Airport Services_SequenceDiagram
Interaction owned by 'Search Airport Services', in package 'Airport'
1a_Alternative Path
Interaction diagram in package 'Airport'
Figure 67: 1a_Alternative Path
1_Basic_Path
Interaction diagram in package 'Airport'
Airport: Airport User: User
1.If the user hasn’t selected a default or current airport, the first step is that the application asks the user which Airport should be used.()
1.If the user hasn’t selected a default or current airport, the first step is that the application asks the user which Airport should be used.() 1.If the user hasn’t selected a default or current airport, the first step is that the application asks the user which Airport should be used.()
Page 112 of 234 Figure 68: 1_Basic_Path