DRV STRING - Benutzerbeiträge [de]

Use Cases

2019-06-26T09:20:44Z

Perezf:

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== 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]] 
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]] 
* [[Insurance tariffs not total price purchased (Ameropa)]] 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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 ===

Use Cases

2019-06-26T09:20:14Z

Perezf:

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== 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]] 
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]] 
* [[Insurance tariffs not total price purchased (Ameropa)]] Insurance tariffs not total price purchased (Ameropa) 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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 ===

Use Cases

2019-06-26T09:16:32Z

Perezf: Versicherungsbedingungen Ameropa

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== 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]] 
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]] 
Insurance tariffs not total price purchased (Ameropa) 

==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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 ===

Insurance tariffs not total price purchased (Ameropa)

2019-06-26T09:14:31Z

Perezf: Die Seite wurde neu angelegt: „ Kategorie:UseCases == Insurance tariffs not total price purchased == '''Module:''' Insurance == Description == Insurance is charged '''per person'''…“

[[Kategorie:UseCases]]

== Insurance tariffs not total price purchased ==

'''Module:''' Insurance

== Description ==
Insurance is charged

'''per person''',

'''per couple'''

(Two adults are defined as a couple.)

'''per family''',

(A family is a maximum of two adults, regardless of relationship, and children up to 25 years of age.

Children are their own children, grandchildren and up to 5 other children travelling with them.)

'''per unit'''.

(A unit is a room, cabin, holiday flat, cottage or similar.)

== Examples ==
3 adults in 1 double room and 1 single room are charged with 2 objects.

2 adults and 1 child in the same accommodation are charged as 1 family.

5 adults + 5 children in a holiday home are charged with 1 unit.

Upselling function of additional services

2018-04-24T09:14:25Z

Perezf:

[[Kategorie:UseCases]]

== Use Case: ''Upselling function of additional services'' ==

'''Module:''' Hotel / Extras

== Description ==
Up-selling function after booking accommodation for possible booking of additional services

== Request Data ==

Mandatory parameters:
* after the booking of a accomodation

Optional parameters:
*

== Response Data ==
The response should to display the price for the accomodation including the possibility of further interaction to book additional services.

Upselling function of additional services

2018-04-24T09:14:16Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Upselling function of additional services'' == '''Module:''' Hotel / Extras == Description == Up-selling function afte…“

Use Cases

2018-04-24T09:14:02Z

Perezf: /* Booking Actions */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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 ===

Searching for a hotel using a map

2018-04-24T09:07:34Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Searching for a hotel using a map'' == '''Module:''' Hotel == Description == Integrate search for booking number by u…“

[[Kategorie:UseCases]]

== Use Case: ''Searching for a hotel using a map'' ==

'''Module:''' Hotel

== Description ==
Integrate search for booking number by using a map.

== Request Data ==

Mandatory parameters:
* 3LC (e.g. MUC) or
* city or part

Optional parameters:
* date
* person

== Response Data ==

The result will be a map of the city or part with hotel goals. If the request is specified with optional elements with pricing included.

Use Cases

2018-04-24T09:07:22Z

Perezf: /* Vacancies */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Use Cases

2018-04-24T09:07:11Z

Perezf: /* Vacancies */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Use Cases

2018-04-24T08:57:35Z

Perezf: /* Train */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Use Cases

2018-04-24T08:57:18Z

Perezf: /* Train */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Use Cases

2018-04-24T08:54:59Z

Perezf: /* Train */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

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

* [[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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Book an Seat only

2018-04-24T08:53:10Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Book an seat only'' == '''Module:''' Train == Description == Adding a seat reservation to an existing train booking.…“

[[Kategorie:UseCases]]

== Use Case: ''Book an seat only'' ==

'''Module:''' Train

== Description ==
Adding a seat reservation to an existing train booking.

== Request Data ==

Mandatory parameters:
* booking number of train booking
* hour
* person

Optional parameters:
* window/corridor
* compartment/big room

== Response Data ==
The response should to display the price and reserved seats.

In a second stage of development the result is a graphical seating plan with possible seats

Book an Train trip

2018-04-24T08:47:48Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Book an Train trip'' == '''Module:''' Train == Description == Based on the response from the train availibilty request…“

[[Kategorie:UseCases]]

== Use Case: ''Book an Train trip'' ==

'''Module:''' Train

== Description ==
Based on the response from the train availibilty request, the booking is made from the selection of the outward and return journey, if necessary.

== Request Data ==

Mandatory parameters:
* departure station
* arrival station
* date
* hour
* person
* class
* oneway or return trip
* discount card (e.g. BahnCard)
* loyalty card

Optional parameters:
* seat include

== Response Data ==
The answer contains the total price and all information such as day, times, changes, class etc.

Train Availability (Bahnauskunft)

2018-04-24T08:41:44Z

Perezf: /* Response Data */

[[Kategorie:UseCases]]

== Use Case: ''Train Availibiltiy'' ==

'''Module:''' Train

== Description ==
In the first step, appropriate train connections are to be displayed by specifying the necessary parameters. Three to five should be offered in each direction of travel.
The response should to display the different prices and give the possibility to select them for transfer to a booking action.

== Request Data ==

Mandatory parameters:
* departure station
* date
* person

Optional parameters:
* arrival station
* hour
* oneway or return trip
* class
* discount card (e.g. BahnCard)
* loyalty card
* seat include

== Response Data ==
The response should to display the different prices and give the possibility to select them for transfer to a booking action.
In addition to the price information, information on booking and cancellation conditions are also provided.

In a second stage of development the result is a graphical seating plan with possible seats

Train Availability (Bahnauskunft)

2018-04-24T08:40:06Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Train Availibiltiy'' == '''Module:''' Train == Description == In the first step, appropriate train connections are to…“

[[Kategorie:UseCases]]

== Use Case: ''Train Availibiltiy'' ==

'''Module:''' Train

== Description ==
In the first step, appropriate train connections are to be displayed by specifying the necessary parameters. Three to five should be offered in each direction of travel.
The response should to display the different prices and give the possibility to select them for transfer to a booking action.

== Request Data ==

Mandatory parameters:
* departure station
* date
* person

Optional parameters:
* arrival station
* hour
* oneway or return trip
* class
* discount card (e.g. BahnCard)
* loyalty card
* seat include

== Response Data ==
The response should to display the different prices and give the possibility to select them for transfer to a booking action.

In a second stage of development the result is a graphical seating plan with possible seats

Use Cases

2018-04-24T08:22:47Z

Perezf: /* Train */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====
==== Train ====
* [[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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Use Cases

2018-04-24T08:19:20Z

Perezf: /* Use Cases by Category */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Graphical seating plan for the vacancy of tickets

2018-04-23T13:38:04Z

Perezf: /* Response Data */

[[Kategorie:UseCases]]

== Use Case: ''Graphical seating plan for the vacancy of tickets'' ==

'''Module:''' Extra

== Description ==
Action for tickets e.g. Musiclas similar to "HF" or "GF", which displays in the response a graphical seating plan from which the tickets can be selected and transferred to a "B" transaction.

== Request Data ==

Mandatory parameters:
* booking number
* date
* person

Optional parameters:
* category

[[Datei:Saalplan.png|mini]]
== Response Data ==
The result is the graphical seating plan with possible seats

Datei:Saalplan.png

2018-04-23T13:37:41Z

Perezf: Saalplan, seating plan

Saalplan, seating plan

Graphical seating plan for the vacancy of tickets

2018-04-23T13:35:56Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Graphical seating plan for the vacancy of tickets'' == '''Module:''' Extra == Description == Action for tickets e.g. M…“

[[Kategorie:UseCases]]

== Use Case: ''Graphical seating plan for the vacancy of tickets'' ==

'''Module:''' Extra

== Description ==
Action for tickets e.g. Musiclas similar to "HF" or "GF", which displays in the response a graphical seating plan from which the tickets can be selected and transferred to a "B" transaction.

== Request Data ==

Mandatory parameters:
* booking number
* date
* person

Optional parameters:
* category

== Response Data ==
The result is the graphical seating plan with possible seats

Use Cases

2018-04-23T13:35:40Z

Perezf: /* Vacancies */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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]]
* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Calculate senior discount

2018-04-23T13:21:41Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Calculate senior discount'' == '''Module:''' Hotel == Description == With the specification of at least one date of bi…“

[[Kategorie:UseCases]]

== Use Case: ''Calculate senior discount'' ==

'''Module:''' Hotel

== Description ==
With the specification of at least one date of birth a senoir discount should be calculated and displayed.

== Request Data ==

Mandatory parameters:
* booking number
* date
* person
* date(s) of birth

Optional parameters:
* room type
* board

== Response Data ==
The result is the calculated and displayed senior discount price

Renew options by customer

2018-04-23T13:19:52Z

Perezf:

[[Kategorie:UseCases]]

== Use Case: ''Renew options by customer'' ==

'''Module:''' Hotel

== Description ==
Allow option extensions by travel agency

== Request Data ==

Mandatory parameters:
* option number
* date
*

Optional parameters:
* option date

== Response Data ==
The result is a confirmation or rejection of the option. optionally, the maximum option date is specified.

Use Cases

2018-04-23T13:19:17Z

Perezf: /* Booking Actions */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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 ====

* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* 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 ===

Renew options by customer

2018-04-23T13:17:01Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Renew options by customer'' == '''Module:''' Hotel == Description == Erlauben von Optionsverlängerungen durch Reisbü…“

[[Kategorie:UseCases]]

== Use Case: ''Renew options by customer'' ==

'''Module:''' Hotel

== Description ==
Erlauben von Optionsverlängerungen durch Reisbüro

== Request Data ==

Mandatory parameters:
* option number
* date
*

Optional parameters:
* option date

== Response Data ==
The result is a confirmation or rejection of the option. optionally, the maximum option date is specified.

Use Cases

2018-04-23T13:14:06Z

Perezf: /* Booking Actions */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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 ====

* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]
* 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 ===

Deliver board variants

2018-04-23T13:05:40Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Deliver board variants'' == '''Module:''' Hotel == Description == For vacancy or booking requests without board detail…“

[[Kategorie:UseCases]]

== Use Case: ''Deliver board variants'' ==

'''Module:''' Hotel

== Description ==
For vacancy or booking requests without board details, the possible board variants should be listed in the response e.g. breakfast, half board etc.

== Request Data ==

Mandatory parameters:
* booking number
* date
* person

Optional parameters:
* room type

== Response Data ==
The result is a list of board variants with price

Deliver variants of occupancy possibilities

2018-04-23T13:03:46Z

Perezf: /* Description */

[[Kategorie:UseCases]]

== Use Case: ''Deliver variants of occupancy possibilities with price'' ==

'''Module:''' Hotel

== Description ==
For vacancy or booking requests without room details, the possible accommodation options should be listed in the response. For 3 persons these are for example 3 single rooms, 1 double room + 1 single room or 1 triple room.

== Request Data ==

Mandatory parameters:
* booking number
* date
* person

Optional parameters:
*

== Response Data ==
The result is a list of possible accomodation with pricing

Use Cases

2018-04-23T13:03:28Z

Perezf: /* Booking Actions */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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 ====

* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]

[[Deliver board variants]]
* 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)
* ?

=== Use Cases by Reference to Request Document ===

Use Cases

2018-04-23T13:03:11Z

Perezf: /* Booking Actions */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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 ====

* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Deliver variants of occupancy possibilities]]
[[Deliver board variants]]
* 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)
* ?

=== Use Cases by Reference to Request Document ===

Deliver variants of occupancy possibilities

2018-04-23T13:01:01Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Deliver variants of occupancy possibilities with price'' == '''Module:''' Hotel == Description == For vacancy or booki…“

[[Kategorie:UseCases]]

== Use Case: ''Deliver variants of occupancy possibilities with price'' ==

'''Module:''' Hotel

== Description ==
For vacancy or booking requests without room details, the possible accommodation options should be listed in the answer. For 3 persons these are for example 3 single rooms, 1 double room + 1 single room or 1 triple room.

== Request Data ==

Mandatory parameters:
* booking number
* date
* person

Optional parameters:
*

== Response Data ==
The result is a list of possible accomodation with pricing

Use Cases

2018-04-23T13:00:51Z

Perezf: /* Booking Actions */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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 ====

* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

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

=== Use Cases by Reference to Request Document ===

Show nearby hotels first

2018-04-23T12:46:10Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Show nearby hotels first'' == '''Module:''' Hotel == Description == In the alternative display of hotels, the geograph…“

[[Kategorie:UseCases]]

== Use Case: ''Show nearby hotels first'' ==

'''Module:''' Hotel

== Description ==
In the alternative display of hotels, the geographically nearest hotels are to be displayed with priority. This should happen if the requested object cannot be booked.

== Request Data ==

Mandatory parameters:
* booking number

Optional parameters:
* date
* person
* hotel category
* room type

== Response Data ==
The result is a list of alternative hotels sorted by distance to the requested hotel

Use Cases

2018-04-23T12:45:58Z

Perezf: /* Vacancies */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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 ====

* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
[[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_single_Flight|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]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
* 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)
* ?

=== Use Cases by Reference to Request Document ===

Use Cases

2018-04-23T12:40:22Z

Perezf: /* Booking Actions */

Use Cases

2018-04-23T12:39:56Z

Perezf: /* Booking Actions */

[[Kategorie:UseCases]]

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

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 ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]
* [[Stops on outbound- and inbound-flight]]

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====

* [[Message Queue]]
* [[Handling-Preferences (Kundenwünsche)]]
* [[One-entry-code for a complete package]]

==== Handling: Payment ====

=== 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 ====

* '''G''' [[Flight Availability (Gerätevakanz)]]
* GF
* GK
* GZ
* '''H''' [[Hotel Availability (Hotelvakanz)]]
* 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_single_Flight|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]]

* BC
[[Display booking-relevant information before booking]]
* BR
* BA
[[Display booking-relevant information before booking]]
* 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)
* ?

=== Use Cases by Reference to Request Document ===

Display booking-relevant information before booking

2018-04-23T12:39:17Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Display booking-relevant information before booking'' == '''Module:''' Hotel == Description == Booking information tha…“

[[Kategorie:UseCases]]

== Use Case: ''Display booking-relevant information before booking'' ==

'''Module:''' Hotel

== Description ==
Booking information that must be confirmed today with action "BC" should be available or displayed at an earlier point in time. They should also be more detailed and for all service elements of the booking. Today's "H" and "HF""BA" actions are being considered.

== Request Data ==

Mandatory parameters:
* booking number

Optional parameters:
* date
* person

== Response Data ==
The result is a display of the bookability or vacancy, including the information relevant for booking.

Use Cases

2018-04-23T12:39:04Z

Perezf: /* Booking Actions */

Later modifications of payment information (credit card)

2018-04-23T12:29:36Z

Perezf: /* Request Data */

´[[Kategorie:UseCases]]

== Use Case: ''Later modifications of payment information (credit card)'' ==

'''Module:''' Hotel / Packages / Flight

== Description ==
After a booking and before full payment of the trip it should be possible to adjust payment information.

== Request Data ==

Mandatory parameters:
* new payment information (e.g. new payer, credit card, valid)

Optional parameters:
*

== Response Data ==

Confirmation of the adjusted payment information

Later modifications of payment information (credit card)

2018-04-23T12:29:15Z

Perezf: Die Seite wurde neu angelegt: „´Kategorie:UseCases == Use Case: ''Later modifications of payment information (credit card)'' == '''Module:''' Hotel / Packages / Flight == Description…“

´[[Kategorie:UseCases]]

== Use Case: ''Later modifications of payment information (credit card)'' ==

'''Module:''' Hotel / Packages / Flight

== Description ==
After a booking and before full payment of the trip it should be possible to adjust payment information.

== Request Data ==

Mandatory parameters:
* new payment information (e.g. new payer, credit card, valid)

Optional parameters:
* format of travel documents (e.g. paper, digital etc.)

== Response Data ==

Confirmation of the adjusted payment information

Use Cases

2018-04-23T12:24:52Z

Perezf: /* Payment Actions */

Choice of the format of the travel documents

2018-04-23T12:23:09Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Choice of the format of the travel documents'' == '''Module:''' Hotel == Description == In the Booking transaction or…“

[[Kategorie:UseCases]]

== Use Case: ''Choice of the format of the travel documents'' ==

'''Module:''' Hotel

== Description ==
In the Booking transaction or a comparable transaction, you can transfer the format of the travel documents in the request.

== Request Data ==

Mandatory parameters:
*

Optional parameters:
* format of travel documents (e.g. paper, digital etc.)

== Response Data ==

Confirmation or rejection of requested format

Use Cases

2018-04-23T12:18:32Z

Perezf: /* Booking Actions */

Check for completeness of data

2018-04-13T14:07:20Z

Perezf: /* Response Data */

[[Kategorie:UseCases]]

== Use Case: ''Check for completeness of data'' ==

'''Module:''' all

== Description ==

For the booking action (B, BA, etc.), the data delivered in the request should be checked for completeness. The missing data is to be named in the response.

== Request Data ==

Mandatory parameters:
* tour operator code
* accommodation and room code(s)
* start and end date of stay(s)
* unambiguos assignment of traveller(s) to requested product(s)

Optional parameters:

* meal plan code(s)
* details about arrival(s) (e.g. arrival airport(s), flight number(s), flight times)
* requested extra(s)

== Response Data ==

List of missing data for complete booking.
This could be passport information, for example.

Check for completeness of data

2018-04-13T14:06:05Z

Perezf: /* Request Data */

Check for completeness of data

2018-04-13T14:04:19Z

Perezf: Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Check for completeness of data'' == '''Module:''' all == Description == For the booking action (B, BA, etc.), the dat…“

Use Cases

2018-04-13T13:58:59Z

Perezf: /* Booking Actions */

Detailed Customer Preferences (Kundenwünsche)

2018-04-13T13:48:47Z

Perezf:

[[Kategorie:UseCases]]

== Use Case: ''Detailed Customer Preferences (Kundenwünsche)'' ==

'''Module:''' Hotel / Package

== Description ==

The possibility to record customer wishes in detail and in relation to the offer

== Request Data ==

Mandatory parameters:
* user defined text (without limitation) for each included offer in request

Optional parameters:
*

== Response Data ==

Confirmation of text (see above)