Book single Flight: Unterschied zwischen den Versionen
Sandk (Diskussion | Beiträge) (→Response Data) |
Sandk (Diskussion | Beiträge) (→Request Data) |
||
| (2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
| Zeile 4: | Zeile 4: | ||
== Use Case: ''Book single flight'' == | == Use Case: ''Book single flight'' == | ||
| − | ''Book single flight'' | + | ''Book single flight'' means booking a flight without any relation to an other service. |
'''Module:''' Flight | '''Module:''' Flight | ||
| Zeile 17: | Zeile 17: | ||
- Roundtrip flight<br /> | - Roundtrip flight<br /> | ||
A bidirectional flight that has a defined outgoing Leg and a defined return Leg where each Leg may consist of multiple Segments. <br /> | A bidirectional flight that has a defined outgoing Leg and a defined return Leg where each Leg may consist of multiple Segments. <br /> | ||
| − | The origin of the | + | The origin of the outgoing flight is equal to the destination of the return flight. <br /> |
| − | The destination of the | + | The destination of the outgoing flight is equal to the origin of the return flight. <br /> |
(For example: Outgoing: VIE -> FRA -> NYC; Return: NYC -> CDG -> VIE)<br /> | (For example: Outgoing: VIE -> FRA -> NYC; Return: NYC -> CDG -> VIE)<br /> | ||
<br /> | <br /> | ||
- (Double) Openjaw flights<br /> | - (Double) Openjaw flights<br /> | ||
| − | Is a roundtrip flight, where outgoing | + | Is a roundtrip flight, where outgoing Leg and return Leg belong together but one or both of the following statements are true: <br /> |
The origin of the outgoing flight is not equal to the destination of the return flight.<br /> | The origin of the outgoing flight is not equal to the destination of the return flight.<br /> | ||
The destination of the return flight is not equal to the origin of the return flight.<br /> | The destination of the return flight is not equal to the origin of the return flight.<br /> | ||
| Zeile 45: | Zeile 45: | ||
- Departure (Date + Time)<br /> | - Departure (Date + Time)<br /> | ||
- Arrival (Date + Time)<br /> | - Arrival (Date + Time)<br /> | ||
| − | - Reference to a Search Result<br /> | + | - [[Using references to search results in Book|Reference to a Search Result]]<br /> |
- Direction (Outgoing / Return)<br /> | - Direction (Outgoing / Return)<br /> | ||
- Assigned Traveller<br /> | - Assigned Traveller<br /> | ||
Especially it is important to have a reference representing the relationship between Outgoing Leg and its Incoming Leg | Especially it is important to have a reference representing the relationship between Outgoing Leg and its Incoming Leg | ||
| − | |||
== Response Data == | == Response Data == | ||
Aktuelle Version vom 23. November 2016, 15:26 Uhr
Inhaltsverzeichnis
Use Case: Book single flight
Book single flight means booking a flight without any relation to an other service.
Module: Flight
Description
It has to be possible to book various types of flights with or without an other service (like hotel). Possible flight types are:
- Oneway flight
A one directional flight that may have multiple Segments combined to one Leg.
(for Example: VIE -> FRA -> NYC)
- Roundtrip flight
A bidirectional flight that has a defined outgoing Leg and a defined return Leg where each Leg may consist of multiple Segments.
The origin of the outgoing flight is equal to the destination of the return flight.
The destination of the outgoing flight is equal to the origin of the return flight.
(For example: Outgoing: VIE -> FRA -> NYC; Return: NYC -> CDG -> VIE)
- (Double) Openjaw flights
Is a roundtrip flight, where outgoing Leg and return Leg belong together but one or both of the following statements are true:
The origin of the outgoing flight is not equal to the destination of the return flight.
The destination of the return flight is not equal to the origin of the return flight.
- Stopover flights
Is a set of one or more Legs, each Leg consists of multiple Segments.
The Travellers want to stay for more than one night at a location between origin and destination of the Leg.
For example:
Outgoing Leg (with Stopover): VIE -> NYC
01.04.2017 VIE -> FRA
04.04.2017 FRA -> NYC
Return Leg (without Stopover): NYC -> VIE
28.04.2017 NYC -> CDG
29.04.2017 CDG -> VIE
Request Data
A defined Structure that represents the logical structure of the described flights giving access to the main attributes of each Leg and Segment like:
- Origin
- Destination
- Departure (Date + Time)
- Arrival (Date + Time)
- Reference to a Search Result
- Direction (Outgoing / Return)
- Assigned Traveller
Especially it is important to have a reference representing the relationship between Outgoing Leg and its Incoming Leg
Response Data
A reflection of the request structure extended by relevant (optional) data for each Leg and Segment like:
- Price (amount and currency)
- Booking State
