Train Availability (Bahnauskunft): Unterschied zwischen den Versionen
Aus DRV STRING
Perezf (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „Kategorie:UseCases == Use Case: ''Train Availibiltiy'' == '''Module:''' Train == Description == In the first step, appropriate train connections are to…“) |
Perezf (Diskussion | Beiträge) (→Response Data) |
||
| Zeile 29: | Zeile 29: | ||
== Response Data == | == Response Data == | ||
The response should to display the different prices and give the possibility to select them for transfer to a booking action. | 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 | In a second stage of development the result is a graphical seating plan with possible seats | ||
Aktuelle Version vom 24. April 2018, 08:41 Uhr
Inhaltsverzeichnis
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
