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.
- 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.
- 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
- ( Flugbegriffe )
- Flight Availability (Gerätevakanz)
- Package included direct flight, no stops
- Stops on outbound- and inbound-flight
First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: 190522 use case insurance.pdf
Use Case 1a by LTA, replaces first use case of 20.05.2019, 19.06.2019: Medium: 20190619 Use Case 1a travel insurance separate to an existing travel booking.xlsx
Use Case 1b by LTA, 19.06.2019 (booking of package and insurance via same platform, so that booking data can be transferred to insurance booking after initial package booking: Medium:20190619 Use Case 1b Integration into a travel booking.xlsx
Use Case 1c by LTA, 19.06.2019, including additional steps A to C: Medium:20190619 Use Case 1c travel insurance without an existing travel booking.xlsx
Protokoll Versicherungsmeeting, 26.07.2019, Berlin: STRING Versicherung 260719.pdf
Protokoll Meeting TUI Cruises, 08.08.2019, Hamburg: STRING Cruise 080819.pdf
Handling: Booking administration
In the first step, it should initially be possible to book train journeys within Germany. In the following step also cross-border train journeys.
The display (D, DR etc.) and cancellation (S, SA, SR etc.) actions should be possible.
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
Actions for the Differentiation of an Offer
Actions for the Display of a Reservation
Actions for the Modification of a Reservation
Actions for Printing of Vouchers
Display of Reservation Lists
- +/- (Paging)