Use Cases: Unterschied zwischen den Versionen

Aktuelle Version vom 21. Oktober 2019, 06:09 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.

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

Flight Availability (Gerätevakanz)

( Flugbegriffe )

Hotel

Hotel Availability (Hotelvakanz)

Hotel on Request

Book an Accommodation

Package

RentalCar

Insurance

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
REVISED Use Case 1a by LTA, replaces version of 19.06.2019, 24.09.2019: Medium: 20190924 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

Insurance tariffs not total price purchased (Ameropa)

Cruise

Protokoll Meeting TUI Cruises, 08.08.2019, Hamburg: STRING Cruise 080819.pdf

Handling: Booking administration

Handling: Payment

Train

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.

Train Availability (Bahnauskunft)

Book an Train trip

Book an Seat only

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

Searching for a hotel using a map

Show nearby hotels first

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

Book Flight

Shopping cart functionality

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

Upselling function of additional services

BC

Display booking-relevant information before booking

BR
BA

Deliver variants of occupancy possibilities

Deliver board variants

Calculate senior discount

BK
BQ
BW
BM
BT
O

Renew options by customer

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)
?

Use Cases by Reference to Request Document

@@ Zeile 59: / Zeile 59: @@
 ==== RentalCar ====
+==== Insurance ====
+First Use Case, Booking Request and Booking Response by LTA, 20.05.2019: [[Medium:190522 use case insurance.pdf|190522 use case insurance.pdf]] <br />
+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]] <br />
+REVISED Use Case 1a by LTA, replaces version of 19.06.2019, 24.09.2019: [[Medium: 20190924 Use Case 1a travel insurance separate to an existing travel booking.xlsx]] <br />
+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]] <br />
+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]] <br />
+Protokoll Versicherungsmeeting, 26.07.2019, Berlin: [[Medium:STRING Versicherung 260719.pdf|STRING Versicherung 260719.pdf]] <br />
+* [[Insurance tariffs not total price purchased (Ameropa)]] <br />
 ==== Cruise ====
+Protokoll Meeting TUI Cruises, 08.08.2019, Hamburg: [[Medium:STRING Cruise 080819.pdf|STRING Cruise 080819.pdf]] <br />
 ==== Handling: Booking administration ====
@@ Zeile 68: / Zeile 80: @@
 ==== Handling: Payment ====
 ==== Train ====
+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.
+* [[Train Availability (Bahnauskunft)]]
+* [[Book an Train trip]]
+* [[Book an Seat only]]
 === Use Cases by Action ===
@@ Zeile 86: / Zeile 107: @@
 * GZ
 * '''H''' [[Hotel Availability (Hotelvakanz)]]
+[[Searching for a hotel using a map]]
 [[Show nearby hotels first]]
 * HF
@@ Zeile 117: / Zeile 140: @@
 [[Choice of the format of the travel documents]]
+[[Upselling function of additional services]]
 * BC