DRV STRING - Benutzerbeiträge [de]

Hotel on Request

2017-01-02T16:49:15Z

Stibbeb: text-change

[[Kategorie:UseCases]]

== Use Case: ''Hotel On Request'' ==

'''Module:''' Hotel / Package / Handling: Booking administration

== Description ==
The hotel-room is only bookable on request. The reservation could be only done without "Reservation in Option".

== Request Data ==
A flag in the request indicates, that reservations on RQ are

* generally not accepted (then the Request generates an error-message in case of an RQ),
* generally accepted (then no error-message is created in case of an RQ)
* only accepted after confirmation (with error-message in case of missing confirmation while trying to book). Confirmation of the request should then be assignable to the RQ-Hotel.

== Response Data ==
Status-Information, which hotel-line is only bookable on RQ.
Error-Messages:
* RQ not accepted: Response creates always an error-message in case of a Hotel on RQ
* RQ- always accepted: No error-message in Response (only Status-Information confirmed RQ)
* RQ accepted by confirmation: No error-message for price-check (only Status-Information confirmed/unconfirmed RQ), error-message for booking in case of unconfirmed RQ-Hotel

Use Cases

2017-01-02T16:46:37Z

Stibbeb: New Link

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

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

==== Hotel ====

* [[Hotel on Request]]

==== 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
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]
* BC
* 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 ====

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

Hotel on Request

2017-01-02T16:45:23Z

Stibbeb: Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''Hotel On Request'' == '''Module:''' Hotel / Package / Handling: Booking administration == Description == The hotel-r…“

[[Kategorie:UseCases]]

== Use Case: ''Hotel On Request'' ==

'''Module:''' Hotel / Package / Handling: Booking administration

== Description ==
The hotel-room is only bookable on request. The reservation could be done without "Reservation in Option".

== Request Data ==
A flag in the request indicates, that reservations on RQ are

* generally not accepted (then the Request generates an error-message in case of an RQ),
* generally accepted (then no error-message is created in case of an RQ)
* only accepted after confirmation (with error-message in case of missing confirmation while trying to book). Confirmation of the request should then be assignable to the RQ-Hotel.

== Response Data ==
Status-Information, which hotel-line is only bookable on RQ.
Error-Messages:
* RQ not accepted: Response creates always an error-message in case of a Hotel on RQ
* RQ- always accepted: No error-message in Response (only Status-Information confirmed RQ)
* RQ accepted by confirmation: No error-message for price-check (only Status-Information confirmed/unconfirmed RQ), error-message for booking in case of unconfirmed RQ-Hotel

Stops on outbound- and inbound-flight

2017-01-02T16:10:23Z

Stibbeb: Change to correct example-airport-code

[[Kategorie:UseCases]]

== Use Case: ''Package with outbound HAM-FRA-FLL, inbound FLL-FRA-HAM '' ==

'''Module:''' Package / Flight

== Description ==
Standard-hotel combined with a flight HAM-FLL, with stop in FRA, different machines and carriers for HAM-FRA and FRA-FLL(passenger changes the machine), flight ends on the same day for inbound and for outbound (no overnight-flight). For HAM-FRA there exists (after the booking) an external Amadeus-booking-reference, FRA-FLL is booked internally (charter-flight).

== Request Data ==
Flight-package HAM-FLL / FLL-HAM could be delivered full-specified (including a tour-operator-identifier or detailed attributes for all parts of the flight like booking-class, flight-number, flight-times, transport-class, routing-information), partly specified or unspecified (only start-date and airports)

== Response Data ==
Response includes the full-specified flight: touroperator-system is able to select on its own a flight which matches the specifications. In the Response it is important that the routing-information is delivered in a full-structured way. In case of a fulfilled reservation also the external booking-references should be assigned in detail (Amadeus-booking-reference for HAM-FRA and FRA-HAM). Internal tour-operator-identifiers are included in the Response to reuse them in the following requests.

Use Cases

2017-01-02T16:09:03Z

Stibbeb: New Link

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

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

==== Hotel ====
==== 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
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]
* BC
* 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 ====

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

Stops on outbound- and inbound-flight

2017-01-02T16:07:44Z

Stibbeb: Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''Package with outbound HAM-FRA-FLL, inbound FLL-FRA-HAM '' == '''Module:''' Package / Flight == Description == Standa…“

[[Kategorie:UseCases]]

== Use Case: ''Package with outbound HAM-FRA-FLL, inbound FLL-FRA-HAM '' ==

'''Module:''' Package / Flight

== Description ==
Standard-hotel combined with a flight HAM-BKK, with stop in FRA, different machines and carriers for HAM-FRA and FRA-BKK (passenger changes the machine), flight ends on the same day for inbound and for outbound (no overnight-flight). For HAM-FRA there exists (after the booking) an external Amadeus-booking-reference, FRA-FLL is booked internally (charter-flight).

== Request Data ==
Flight-package HAM-FLL / FLL-HAM could be delivered full-specified (including a tour-operator-identifier or detailed attributes for all parts of the flight like booking-class, flight-number, flight-times, transport-class, routing-information), partly specified or unspecified (only start-date and airports)

== Response Data ==
Response includes the full-specified flight: touroperator-system is able to select on its own a flight which matches the specifications. In the Response it is important that the routing-information is delivered in a full-structured way. In case of a fulfilled reservation also the external booking-references should be assigned in detail (Amadeus-booking-reference for HAM-FRA and FRA-HAM). Internal tour-operator-identifiers are included in the Response to reuse them in the following requests.

Use Cases

2017-01-02T15:35:07Z

Stibbeb: New Link

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

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

==== Hotel ====
==== Package ====

* [[Flight Availability (Gerätevakanz)]]
* [[Package included direct flight, no stops]]

==== 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
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]
* BC
* 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 ====

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

Package included direct flight, no stops

2017-01-02T15:32:47Z

Stibbeb: Die Seite wurde neu angelegt: „ Kategorie:UseCases == Use Case: ''Package with direct flight, no stops, flight unspecified'' == '''Module:''' Package / Flight == Description == Stand…“

[[Kategorie:UseCases]]

== Use Case: ''Package with direct flight, no stops, flight unspecified'' ==

'''Module:''' Package / Flight

== Description ==
Standard-hotel combined with a standard-flight, no stops during the flight, flight ends on the same day for inbound and for outbound (no overnight-flight).

== Request Data ==
Unspecified flight: Start-Date, Departure Airport, Arrival Airport, no carrier, no booking-class, no transport-class, no stops, all passengers assigned

== Response Data ==
Specified flight: touroperator-system is able to select a flight which matches the low-specifications on ist own.

Use Cases

2016-12-29T10:07:21Z

Stibbeb: Link to new use case

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

=== Use Cases by Category ===

==== Flight ====

* [[Flight Availability (Gerätevakanz)]]

==== Hotel ====
==== Package ====

* [[Flight Availability (Gerätevakanz)]]

==== 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
* HF
* HK
* C
* CF
* CK

==== Actions for the Differentiation of an Offer ====

* HW
* KW
* HO
* HU
* MW
* KG/VA

==== Booking Actions ====

* B
[[Book_single_Flight|Book Flight]]

[[Shopping cart functionality]]

[[Using references to search results in Book]]
* BC
* 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 ====

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

One-entry-code for a complete package

2016-12-29T09:57:19Z

Stibbeb: Use-case: One-entry-code

[[Kategorie:UseCases]]

== Use Case: ''One-entry-code for a complete package'' ==

'''Module:''' Handling: Booking administration

== Description ==
Touroperator provides an one-entry-code which is used to create a complete booking with flight-lines, hotel-lines, extra-service-lines and insurance-lines. The agent only needs to type in this code with the number of passengers, the start-date and an optional duration in the request. Tour-operator internally creates the related booking-lines (flight, hotel, extras, insurance) in the response.

== Request Data ==
The booking includes an one-entry-code with a start-date, optional duration, passenger-assignment

== Response Data ==
The one-entry-code is expanded to the regular package included fligth-lines, hotel-lines, extra-service-lines and insurance-lines. Ideally there exists a comment-line in the response where it is visible that the response is based on a special one-entry-code.

Handling-Preferences (Kundenwünsche)

2016-12-01T18:01:21Z

Stibbeb: New UseCase "Add Preferences to the reservation"

[[Kategorie:UseCases]]

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

''How to add Kundenwünsche and assign them to passenger, to the basket line, to the package, to the reservation''

'''Module:'''
''Flight, Hotel, Extra-Service, Package''

== Description ==
The interface needs a way how to add preferences into the reservation.
Examples:
- Vegetarain meal is necessary (assigned to the flight or the hotel-line)
- Promotion-code of the hotel-chain (assigned to the hotel)
- Reference to a second reservation-number to have rooms near together (assigned to the hotel)
- Preference of a special room in the hotel (assigned to the hotel)
- Information to the hotel about a special handicap of the guest (assigned to the hotel or the passenger)
- Freetext information to tour-operator, hotel or carrier (assigned to basket line or passenger)
...

Possibility to assign different (more than one) preferences to the same passenger or basket-line.

== Request Data ==

== Response Data ==