1. E-Ticket Airline Reservation System (ETRS)
CPSC 461 – Thursday Lab
Group:
Kevin Nuguyen
Brad Rippe
Dhanireddy Sravani
Iris Tam

2. Use Case – High Level

3. Use Case – Request Flights

4. Use Case – Scenario Request flight information
Name
Requests available flight information
Summary
The user provides a destination and dates to the E-Ticket Reservation System (ETRS). The system inquires the airline database about available flights and presents them to the customer.
Basic Events
Customer
System
1. Launches ETRS application
2. Displays UI for user to search available flights.
3. Selects origination city
4. Selects destination city
5. Selects departure date
6. Selects return date
7. Selects one-way or round trip
8. Selects connections or nonstop
9. Submit criteria
10. Validates customer data.
Data is valid if customer enters a start and end cities that the system provides service to and valid dates such that the start date is not prior to the end date and vice versa. Invalid data are empty cities and dates, dates that do not exist, or cities that the system does not provide service to.
10. Shows list of flights that met customer’s criteria.
Alternatives
None
Exceptions
1. If customer data is invalid system displays error message
2. User acknowledges the message.
3. Displays UI with current criteria, allowing user to modify desired flight information; continues at basic event 9.
1. If data is valid and a flight cannot be found, the system displays a messages informing the user that no flights are available that met the current criteria.
Triggers
Customer needs flight information.
Assumptions
The customer knows travel information dates, and available budget.
Preconditions
Customer has available internet connection and ETRS installed.
Postconditions
Customer will have a list of flights that met specified travel criteria.

5. Name
Requests available flight information
Summary
The user provides a destination and dates to the E-Ticket Reservation System (ETRS). The system inquires the airline database about available flights and presents them to the customer.
Basic Events
Customer
System
1. Launches ETRS application
2. Displays UI for user to search available flights.
3. Selects origination city
4. Selects destination city
5. Selects departure date
6. Selects return date
7. Selects connections or nonstop
8. Submit criteria
9. Validates customer data.
Data is valid if customer enters a start and end cities that the system provides service to and valid dates such that the start date is not prior to the end date and vice versa. Invalid data are empty cities and dates, dates that do not exist, or cities that the system does not provide service to.
11. Shows list of flights that met customer’s criteria.
Alternatives
None
Exceptions
1. If customer data is invalid system displays error message
2. User acknowledges the message.
3. Displays UI with current criteria, allowing user to modify desired flight information; continues at basic event 9.
1. If data is valid and a flight cannot be found, the system displays a messages informing the user that no flights are available that met the current criteria.
Triggers
Customer needs flight information.
Assumptions
The customer knows travel information dates, and available budget.
Preconditions
Customer has available internet connection and ETRS installed.
Postconditions
Customer will have a list of flights that met specified travel criteria.

6. Name
Requests available flight information
Summary
The user provides a destination and dates to the E-Ticket Reservation System (ETRS). The system inquires the airline database about available flights and presents them to the customer.
Basic Events
Customer
System
1. Launches ETRS application
2. Displays UI for user to search available flights.
3. Selects origination city
4. Selects destination city
5. Selects departure date
6. Selects return date
7. Selects connections or nonstop
8. Submit criteria
9. Validates customer data.
Data is valid if customer enters a start and end cities that the system provides service to and valid dates such that the start date is not prior to the end date and vice versa. Invalid data are empty cities and dates, dates that do not exist, or cities that the system does not provide service to.
10. Shows list of flights that met customer’s criteria.
Alternatives
None
Exceptions
1. If customer data is invalid system displays error message
2. User acknowledges the message.
3. Displays UI with current criteria, allowing user to modify desired flight information; continues at basic event 9.
1. If data is valid and a flight cannot be found, the system displays a messages informing the user that no flights are available that met the current criteria.
Triggers
Customer needs flight information.
Assumptions
The customer knows travel information dates, and available budget.
Preconditions
Customer has available internet connection and ETRS installed.
Postconditions
Customer will have a list of flights that met specified travel criteria.

7. Use Case – Choose a flight

8. Name
Choose a flight.
Summary
The customer has been presented with options for flights to go to his/her destination. The customer chooses a preferred flight and seat. The application puts the seat(s) on hold, and requests payment information from the user.
Basic Events
Customer
System
1. The customer chooses a preferred flight.
2. The customer chooses a preferred seat.
3. Requests the chosen flight and seat(s) be put on hold from the airline database.
4. Returns confirmation number to the customer
5. Displays UI for the user to input payment information
Alternatives
None
Exceptions
1. If seat is not available, system displays an error message stating that the current seat is unavailable then displays an updated seating chart; continues at basic event 2.
1. If the flight is not longer available system displays an error message stating such and displays an updated list of available flights; continues at basic event 1.
Triggers
Customer wants to a flight and seating on hold.
Assumptions
The customer has input city of origin, city of destination, and dates of travel.
Preconditions
Customer has a list of available flights that meet there criteria.
Postconditions
Customer will have a flight and seating on hold.

9. Name
Choose a flight.
Summary
The customer has been presented with options for flights to go to his/her destination. The customer chooses a preferred flight and seat. The application puts the seat(s) on hold, and requests payment information from the user.
Basic Events
Customer
System
1. The customer chooses a preferred flight.
2. The customer chooses a preferred seat.
3. Requests the chosen flight and seat(s) be put on hold from the airline database.
4. Returns confirmation number to the customer
5. Displays UI for the user to input payment information
Alternatives
None
Exceptions
1. If seat is not available, system displays an error message stating that the current seat is unavailable then displays an updated seating chart; continues at basic event 2.
1. If the flight is not longer available system displays an error message stating such and displays an updated list of available flights; continues at basic event 1.
Triggers
Customer wants to a flight and seating on hold.
Assumptions
The customer has input city of origin, city of destination, and dates of travel.
Preconditions
Customer has a list of available flights that meet there criteria.
Postconditions
Customer will have a flight and seating on hold.

10. Use Case – Book a flight

11. Name
Customer books flight
Summary
The application contacts credit card authorization service for payment authorization. The service books the flight, and return confirmation number to the customer.
Basic Events
Customer
System
1. Display flight on hold and prompts user for payment information.
2. Confirms flight and inputs preferred payment information.
3. Contacts the credit card authorization service.
4. Prompts for final verification.
5. Confirms transaction
5. The application sends the request to purchase the ticket(s).
6. The response indicates success with an authorization number, signed by the payment authority.
7. The application sends a request in order to find out how to cancel the reservation should a problem occur later in the process.
8. The service provides the customer with a confirmation number and displays the customer iternary and wishes them a good flight.
9. Charges are applied to customer’s credit card
Alternatives
None
Exceptions
1. Customer is not satisfied with flight arrangement on hold, he/she will be able to cancel and reschedule. Continue at Use-Case: Request flight information
1. If the application cannot communicate with the authorization service, the application displays a error message informing the customer that communication can’t be made and to try there purchase later; continues at basic event 1.
1. If the customers payment information cannot be validated; the application displays an error message and continues at basic event 1.
Invalid data is empty data, or incorrect/incomplete credit card information.
Triggers
Customer wants to purchase flight and seating arrangements on hold.
Assumptions
The customer has flight on hold.
Preconditions
Customer has placed flight and seating on hold.
Postconditions
Customer has confirmation number and valid e-ticket to travel. Customer’s credit card will reflect the transaction in the next billing statement.

12. Name
Customer books flight
Summary
The application contacts credit card authorization service for payment authorization. The service books the flight, and return confirmation number to the customer.
Basic Events
Customer
System
1. Display flight on hold and prompts user for payment information.
2. Confirms flight and inputs preferred payment information.
3. Contacts the credit card authorization service.
4. Prompts for final verification.
5. Confirms transaction
5. The application sends the request to purchase the ticket(s).
6. The response indicates success with an authorization number, signed by the payment authority.
7. The application sends a request in order to find out how to cancel the reservation should a problem occur later in the process.
8. The service provides the customer with a confirmation number and displays the customer iternary and wishes them a good flight.
9. Charges are applied to customer’s credit card
Alternatives
None
Exceptions
1. Customer is not satisfied with flight arrangement on hold, he/she will be able to cancel and reschedule. Continue at Use-Case: Request flight information
1. If the application cannot communicate with the authorization service, the application displays a error message informing the customer that communication can’t be made and to try there purchase later; continues at basic event 1.
1. If the customers payment information cannot be validated; the application displays an error message and continues at basic event 1.
Invalid data is empty data, or incorrect/incomplete credit card information.
Triggers
Customer wants to purchase flight and seating arrangements on hold.
Assumptions
The customer has flight on hold.
Preconditions
Customer has placed flight and seating on hold.
Postconditions
Customer has confirmation number and valid e-ticket to travel. Customer’s credit card will reflect the transaction in the next billing statement.

13. Use Case Scenarios
That’s it!
Thanks!