Book single Flight

Use Case: Book single flight

Book single flight

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 data like:
- Price (amount and currency)
- Booking State