Use Cases

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.

<createarticle>

type=createarticle
preload=Template:UseCases
buttonlabel=Create Use Case
align=left
default=Please add title

</createarticle>

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".

Use Cases by Action

Actions for the Display of Examples

B?

Vacancies

G GF GK GZ H HF HK C CF CK

Actions for the Differentiation of an Offer

HW KW HO HU MW KG/VA

Booking Actions

B BC BR BA BK BQ BW BM BT O OC OR OA OQ BS RF PB RS CM ZL ZW

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

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