Travel System Re-engineering

Use Case Specification: Change Itinerary

Brief Description

The Change Itinerary use case will allow the customer or travel agent to search for an itinerary and change flight.

Flow of Events

Basic Flow

Customer selects change itinerary from menu

System presents a list of itineraries

Customer selects the itinerary to change

System returns the selected itinerary, which includes each segment of the itinerary.

Customer selects the segment to change. In order to change, the segment is deleted and the Prepare Itinerary Use Case is executed.

Alternative Flows

none

Special Requirements

Security

All interactions 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

A 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