Mitarbeit

2016-10-31T10:53:37Z

Charitop: Condor hinzugefügt

'''Getting Involved'''

The STRING project is generally open to everyone interested in participating the process of developing a new standard for bookings in the travel industry. Therefore this wiki and its information are open to the public.

The project has several working and decision making levels. The highest institution within this project is the Steering Committee. It consists of the current board members of the users of the DRV data standard and is led by the DRV. Members of the Steering Committee are representatives from the following companies:

* Ameropa
* Condor
* DER Touristik
* FTI
* Olimar
* Peakwork
* Thomas Cook
* TravelTainment
* Travelport
* TUI

The project is led by the DRV and MC Management Consulting, Amadeus and Bewotec have designated further employees to support this project in order to develop the required XSD-schemes. This project team strongly cooperates with an expert group. Experts are members of the tour operators represented in the Steering Committee.

Nevertheless the project team shares its information with the public and would highly appreciate an industry-wide discussion of the projects intermediate and final results on this platform. Therefore all relevant project information published within this wiki are fully accessable to the public, everyone interested can inform him- or herself about the current status of development.

If you would like to actively accompany the project development and support the project team by discussing published results, pls send a short application request including your name, company, working position and eMail-address to [mailto:registration@string.drv.de registration@string.drv.de]. You will then get access data. Please keep in mind: access will only be provided to individuals, not to overall companies. If needed you can of course have several accounts per company. Please consider: all comments published on this platform will always show the author and authors are fully responsible for the content published with their account. Therefore please handle your access data very carefully. In case of misuse of access the project team has the right to eliminate users from this platform (e.g. use of foul language).

For more Information please see [[Berechtigungskonzept]].

Use Cases

2016-10-31T10:49:15Z

Charitop: /* 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.

=== Use Cases by Category ===

==== Flight ====

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

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

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

==== RentalCar ====
==== Cruise ====
==== Handling: Booking administration ====
==== 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
* 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 ===

DRV STRING - Benutzerbeiträge [de]

Mitarbeit

Use Cases