Travel System Re-engineering

Use Case Specification: Pay for Itinerary

 

Brief Description

The Pay for Itinerary use case will allow the customer or travel agent to select an itinerary and pay.

 

Flow of Events

Basic Flow

Other use cases send priced itinerary

System displays the itinerary and pricing

Customer selects pay with credit card

System returns the list of credit cards on file. It only displays the last four digits of credit card, expiration date, and type.

Customer selects the credit card

System sends payment transaction to TransMaster and waits for authorization

System sends email confirmation of successful payment to customers email address once credit authorization is returned

Alternative Flows

Customer not logged in

Before the customer can pay for an itinerary, they must log in with their user id and password. The Log In use case is executed and the system returns the list of itineraries.

Customer Selects Award Travel

Customer selects an existing itinerary.

System displays the itinerary and pricing

Customer selects award travel

System verifies mileage availability and returns confirmation screen

System sends email confirmation of successful award travel to customers email address

Credit Card Authorization Fails

Same as primary flow except email is of failed payment transaction

 

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.

Customer has a priced itinerary

 

Post-Conditions

Paid Itinerary

A paid customer itinerary that contains the city, flight number, date, time, and seat number for each segment of the flight. Email confirmation is sent to customer email address.

 

Uses Points

none