Travel System Re-engineering

Use Case Specification: Prepare Itinerary

Brief Description

The Prepare Itinerary use case will allow the customer or travel agent to search for and reserve a seat(s) for a round trip or one way flight.

Flow of Events

Basic Flow

Customer enters departure city, departure time, departure date, destination city, return time, return date, and selects round-trip or one-way.

System responds with a list of departure flights and return flights.

Customer selects the departure flight and return flight.

System responds with the selected flight priced and alternative flights if less than selected and within one hour of departure and return times.

Customer selects flights.

System responds with seat availability for selected flights

Customer selects seats

System prices the itinerary and returns the itinerary confirmation window with selected flights

Customer confirms the itinerary

System sends the priced itinerary to Pay for Itinerary Use Case

Alternative Flows

Customer not logged in

Before the customer can confirm the flights and save the itinerary, they must log in with their user id and password. The Log In use case is executed and the system returns the itinerary confirmation window with selected flights.

Customer confirms the itinerary

System sends the priced itinerary to Pay for Itinerary Use Case

Customer not a member

In order to confirm an itinerary, the customer must be a member, so the Create Profile use case is executed and the system returns the itinerary confirmation window with selected flights.

Customer confirms the itinerary

System sends the priced itinerary to Pay for Itinerary Use Case

Special Requirements

Security

All interaction with the customer and the system must be secured with SSL.

Pre-Conditions

Customer Logged In

Customer has successfully logged in with a valid user id and password.

Customer has profile

Customer has an existing profile.

Post-Conditions

Prepared Itinerary

An unpaid customer itinerary that contains the city, flight number, date, time, and seat number for a departure flight; and city, flight number, date, time and seat number for return flight. It could also contain city, flight number, date, time and seat number for each leg of the flight if a lay over is necessary.

Uses Points

Pay for Itinerary

After the customer has selected flights, seats and confirmed the itinerary, the pay for itinerary use case is executed