Use Cases: Unterschied zwischen den Versionen
Perezf (Diskussion | Beiträge) (→Use Cases by Category) |
Perezf (Diskussion | Beiträge) (→Train) |
||
| Zeile 68: | Zeile 68: | ||
==== Handling: Payment ==== | ==== Handling: Payment ==== | ||
==== Train ==== | ==== Train ==== | ||
| + | * [[Train Availability (Bahnauskunft)]] | ||
| + | |||
| + | * [[Book an Train trip]] | ||
| + | |||
| + | * [[Book an Seat only]] | ||
=== Use Cases by Action === | === Use Cases by Action === | ||
Version vom 24. April 2018, 08:22 Uhr
This is the main page for our collection of use cases.
To add a new one please insert a suitable name and then click "Create Use Case" to launch a new page for your entry. Then fill in the missing sections of the template.
Inhaltsverzeichnis
- 1 Why Use Cases?
- 1.1 Role Definitions
- 1.2 Use Cases by Category
- 1.3 Use Cases by Action
- 1.3.1 Actions for the Display of Examples
- 1.3.2 Vacancies
- 1.3.3 Actions for the Differentiation of an Offer
- 1.3.4 Booking Actions
- 1.3.5 Actions for the Display of a Reservation
- 1.3.6 Actions for the Modification of a Reservation
- 1.3.7 Payment Actions
- 1.3.8 Actions for Printing of Vouchers
- 1.3.9 Display of Reservation Lists
- 1.3.10 Information
- 1.3.11 Test Actions
- 1.3.12 Service Actions
- 1.4 Use Cases by Reference to Request Document
Why Use Cases?
We aim to create a complete replacement for all transactions which are handled by STADIS and many external extensions today. To do so we have to find out which transactions are needed and what kind of data is exchanged between clients and tour operator systems.
So for a start every action code used today in TOMA-like systems should have at least one assigned use case here (or be deprecated).
The same applies for all proposed extensions of the "Anforderungsdefinition".
See Flight Availability (Gerätevakanz) for an example of what we need.
Role Definitions
- tour operator / airline system
- (supplier for the above)
- CRS / GDS
- client system non-automatic (travel agency)
- client sytem automatic (internet booking engine)
- offer / search system
Use Cases by Category
Flight
- ( Flugbegriffe )
Hotel
Package
- Flight Availability (Gerätevakanz)
- Package included direct flight, no stops
- Stops on outbound- and inbound-flight
RentalCar
Cruise
Handling: Booking administration
Handling: Payment
Train
Use Cases by Action
The STRING interface will not use action codes but request/response pairs. We aim however to support all methods of the old interfaces we're superseding as long as they are not deprecated or applicable.
Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.
Actions for the Display of Examples
- B?
Vacancies
Graphical seating plan for the vacancy of tickets
- HF
- HK
- C
- CF
- CK
Actions for the Differentiation of an Offer
- HW
- KW
Detailed Customer Preferences (Kundenwünsche)
- HO
- HU
- MW
- KG/VA
Booking Actions
- B
Using references to search results in Book
Traveler Name Fields without character limitation
Check for completeness of data
Choice of the format of the travel documents
- BC
Display booking-relevant information before booking
- BR
- BA
Deliver variants of occupancy possibilities
- BK
- BQ
- BW
- BM
- BT
- O
- OC
- OR
- OA
- OQ
- BS
- RF
- PB
- RS
- CM
- ZL
- ZW
- KV
- KS
Actions for the Display of a Reservation
- D
- DR
- CR
Actions for the Modification of a Reservation
- F
- FR
- OV
- U
- UR
- UC
- UQ
- S
- SR
- SA
- W
Payment Actions
Later modifications of payment information (credit card)
- DI
- DZ
- KU
- KX
- KE
Actions for Printing of Vouchers
- RA
Display of Reservation Lists
- V
Information
- I
- IP
- BI
- DD
- AI
- AG
Test Actions
- TB
- TD
- TF
- TO
- TS
- TU
Service Actions
- +/- (Paging)
- ?
