http://string.drv.de/wiki/api.php?action=feedcontributions&user=Roesnern&feedformat=atomDRV STRING - Benutzerbeiträge [de]2024-03-29T10:22:54ZBenutzerbeiträgeMediaWiki 1.26.3http://string.drv.de/wiki/index.php?title=Use_Cases&diff=207Use Cases2017-01-16T10:32:28Z<p>Roesnern: /* Hotel */</p>
<hr />
<div>[[Kategorie:UseCases]]<br />
<br />
This is the main page for our collection of use cases.<br />
<br />
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.<br />
<br />
<createarticle><br />
type=createarticle<br />
preload=Template:UseCases<br />
buttonlabel=Create Use Case<br />
align=left<br />
default=Please add title<br />
</createarticle><br />
<br />
== Why Use Cases? ==<br />
<br />
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.<br />
<br />
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).<br />
<br />
The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.<br />
<br />
See [[Flight Availability (Gerätevakanz)]] for an example of what we need.<br />
<br />
=== Use Cases by Category ===<br />
<br />
==== Flight ====<br />
<br />
* [[Flight Availability (Gerätevakanz)]]<br />
<br />
==== Hotel ====<br />
<br />
* [[Hotel on Request]]<br />
<br />
* [[Book an Accommodation]]<br />
<br />
==== Package ====<br />
<br />
* [[Flight Availability (Gerätevakanz)]]<br />
* [[Package included direct flight, no stops]]<br />
* [[Stops on outbound- and inbound-flight]]<br />
<br />
==== RentalCar ====<br />
==== Cruise ====<br />
==== Handling: Booking administration ====<br />
<br />
* [[Message Queue]]<br />
* [[Handling-Preferences (Kundenwünsche)]]<br />
* [[One-entry-code for a complete package]]<br />
<br />
==== Handling: Payment ====<br />
<br />
=== Use Cases by Action ===<br />
<br />
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.<br />
<br />
Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.<br />
<br />
==== Actions for the Display of Examples ====<br />
<br />
* B?<br />
<br />
==== Vacancies ====<br />
<br />
* '''G''' [[Flight Availability (Gerätevakanz)]]<br />
* GF<br />
* GK<br />
* GZ<br />
* H<br />
* HF<br />
* HK<br />
* C<br />
* CF<br />
* CK<br />
<br />
==== Actions for the Differentiation of an Offer ==== <br />
<br />
* HW<br />
* KW<br />
* HO<br />
* HU<br />
* MW<br />
* KG/VA<br />
<br />
==== Booking Actions ====<br />
<br />
* B<br />
[[Book_single_Flight|Book Flight]]<br />
<br />
[[Shopping cart functionality]]<br />
<br />
[[Using references to search results in Book]]<br />
* BC<br />
* BR<br />
* BA<br />
* BK<br />
* BQ<br />
* BW<br />
* BM<br />
* BT<br />
* O<br />
* OC<br />
* OR<br />
* OA<br />
* OQ<br />
* BS<br />
* RF<br />
* PB<br />
* RS<br />
* CM<br />
* ZL<br />
* ZW<br />
* KV<br />
* KS<br />
<br />
==== Actions for the Display of a Reservation ====<br />
<br />
* D<br />
* DR<br />
* CR<br />
<br />
==== Actions for the Modification of a Reservation ====<br />
<br />
* F<br />
* FR<br />
* OV<br />
* U<br />
* UR<br />
* UC<br />
* UQ<br />
* S<br />
* SR<br />
* SA<br />
* W<br />
<br />
==== Payment Actions ====<br />
<br />
* DI<br />
* DZ<br />
* KU<br />
* KX<br />
* KE<br />
<br />
==== Actions for Printing of Vouchers ====<br />
<br />
* RA<br />
<br />
==== Display of Reservation Lists ====<br />
<br />
* V<br />
<br />
==== Information ====<br />
<br />
* I<br />
* IP<br />
* BI<br />
* DD<br />
* AI<br />
* AG<br />
<br />
==== Test Actions ====<br />
<br />
* TB<br />
* TD<br />
* TF<br />
* TO<br />
* TS<br />
* TU<br />
<br />
==== Service Actions ====<br />
<br />
* +/- (Paging)<br />
* ?<br />
<br />
=== Use Cases by Reference to Request Document ===</div>Roesnernhttp://string.drv.de/wiki/index.php?title=Use_Cases&diff=206Use Cases2017-01-16T10:31:33Z<p>Roesnern: /* Hotel */</p>
<hr />
<div>[[Kategorie:UseCases]]<br />
<br />
This is the main page for our collection of use cases.<br />
<br />
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.<br />
<br />
<createarticle><br />
type=createarticle<br />
preload=Template:UseCases<br />
buttonlabel=Create Use Case<br />
align=left<br />
default=Please add title<br />
</createarticle><br />
<br />
== Why Use Cases? ==<br />
<br />
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.<br />
<br />
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).<br />
<br />
The same applies for all proposed extensions of the ''"Anforderungsdefinition"''.<br />
<br />
See [[Flight Availability (Gerätevakanz)]] for an example of what we need.<br />
<br />
=== Use Cases by Category ===<br />
<br />
==== Flight ====<br />
<br />
* [[Flight Availability (Gerätevakanz)]]<br />
<br />
==== Hotel ====<br />
<br />
* [[Hotel on Request]]<br />
<br />
* [[Book_an_Accommodation]]<br />
<br />
==== Package ====<br />
<br />
* [[Flight Availability (Gerätevakanz)]]<br />
* [[Package included direct flight, no stops]]<br />
* [[Stops on outbound- and inbound-flight]]<br />
<br />
==== RentalCar ====<br />
==== Cruise ====<br />
==== Handling: Booking administration ====<br />
<br />
* [[Message Queue]]<br />
* [[Handling-Preferences (Kundenwünsche)]]<br />
* [[One-entry-code for a complete package]]<br />
<br />
==== Handling: Payment ====<br />
<br />
=== Use Cases by Action ===<br />
<br />
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.<br />
<br />
Several action codes might be linked to the same use case when their functionality will be bundled into the same request/response.<br />
<br />
==== Actions for the Display of Examples ====<br />
<br />
* B?<br />
<br />
==== Vacancies ====<br />
<br />
* '''G''' [[Flight Availability (Gerätevakanz)]]<br />
* GF<br />
* GK<br />
* GZ<br />
* H<br />
* HF<br />
* HK<br />
* C<br />
* CF<br />
* CK<br />
<br />
==== Actions for the Differentiation of an Offer ==== <br />
<br />
* HW<br />
* KW<br />
* HO<br />
* HU<br />
* MW<br />
* KG/VA<br />
<br />
==== Booking Actions ====<br />
<br />
* B<br />
[[Book_single_Flight|Book Flight]]<br />
<br />
[[Shopping cart functionality]]<br />
<br />
[[Using references to search results in Book]]<br />
* BC<br />
* BR<br />
* BA<br />
* BK<br />
* BQ<br />
* BW<br />
* BM<br />
* BT<br />
* O<br />
* OC<br />
* OR<br />
* OA<br />
* OQ<br />
* BS<br />
* RF<br />
* PB<br />
* RS<br />
* CM<br />
* ZL<br />
* ZW<br />
* KV<br />
* KS<br />
<br />
==== Actions for the Display of a Reservation ====<br />
<br />
* D<br />
* DR<br />
* CR<br />
<br />
==== Actions for the Modification of a Reservation ====<br />
<br />
* F<br />
* FR<br />
* OV<br />
* U<br />
* UR<br />
* UC<br />
* UQ<br />
* S<br />
* SR<br />
* SA<br />
* W<br />
<br />
==== Payment Actions ====<br />
<br />
* DI<br />
* DZ<br />
* KU<br />
* KX<br />
* KE<br />
<br />
==== Actions for Printing of Vouchers ====<br />
<br />
* RA<br />
<br />
==== Display of Reservation Lists ====<br />
<br />
* V<br />
<br />
==== Information ====<br />
<br />
* I<br />
* IP<br />
* BI<br />
* DD<br />
* AI<br />
* AG<br />
<br />
==== Test Actions ====<br />
<br />
* TB<br />
* TD<br />
* TF<br />
* TO<br />
* TS<br />
* TU<br />
<br />
==== Service Actions ====<br />
<br />
* +/- (Paging)<br />
* ?<br />
<br />
=== Use Cases by Reference to Request Document ===</div>Roesnernhttp://string.drv.de/wiki/index.php?title=Book_an_Accommodation&diff=205Book an Accommodation2017-01-16T10:18:14Z<p>Roesnern: first draft</p>
<hr />
<div><br />
[[Kategorie:UseCases]]<br />
<br />
== Use Case: ''Book an Accommodation'' ==<br />
<br />
<br />
'''Module:''' Hotel<br />
<br />
Request availability and pricing for specific accommodation(s), room(s), meal plan(s), stay(s), traveller(s).<br />
<br />
In case of a booking request not only a pricing is requested but the creation of a firm reservation in the addressed tour operator system.<br />
<br />
== Description ==<br />
<br />
'''Use case 1:'''<br />
Absolute standard: Two persons share the same room, same meal plan and all together one and the same travel times.<br />
<br />
<br />
'''Use case 2:'''<br />
4 persons, same arrival by plane, same hotel<br />
* all rooms without catering<br />
* 1 person in standard single room<br />
* 1 person in a superior single room with breakfast as an extra<br />
* 2 persons in a standard double room with breakfast as extra; one person has birthday ...<br />
* 1 airport transfer for all as an extra<br />
<br />
<br />
'''Use case 3:'''<br />
2 persons, same hotel, 2 rooms, different / overlapping periods of stay<br />
* 1 person travels earlier, then together<br />
* different catering/meal plans<br />
<br />
<br />
'''Use case 4:'''<br />
2 persons together in 2 different hotels at different times and another hotel for one of the persons<br />
* 1 person stays one day longer in a 3rd hotel<br />
<br />
<br />
'''Use case 5:'''<br />
8 persons in an apartment / holiday flat,<br />
* No catering/supplies<br />
* Car hire available as extra<br />
* Transfer available as extra<br />
<br />
<br />
'''Use case 6:'''<br />
4 persons, same hotel, but different arrivals and travel times<br />
* 1 party (2 persons) arrives 7 days later and stays 3 days longer<br />
* various catering<br />
* Hotel transfers as extra<br />
<br />
<br />
'''Use case 7:'''<br />
3 persons each in the same hotel, in 2 rooms, for 2 different periods<br />
* "Interrupted" non-continuous stay<br />
* same meal plan/catering (e.g. half board)<br />
* Transfers to hotel and to the airport included as extras<br />
<br />
<br />
== Request Data ==<br />
<br />
'''Mandatory''' parameters:<br />
* tour operator code<br />
* accommodation and room code(s)<br />
* start and end date of stay(s)<br />
* unambiguos assignment of traveller(s) to requested product(s)<br />
<br />
'''Optional''' parameters:<br />
* meal plan code(s)<br />
* details about arrival(s) (e.g. arrival airport(s), flight number(s), flight times)<br />
* requested extra(s)<br />
<br />
<br />
== Response Data ==<br />
<br />
In case of an availability and pricing request the positive result will be a list of the requested accommodations with prices and descriptions of the booked stay(s), room(s), meal plan(s), traveller(s), extra(s).<br />
<br />
In case of a booking request the response contains a reservation number and a state of the reservation (e.g. confirmed, on request, on option,...).</div>Roesnern