1. E-Ticket Reservation System CPSC 461 – Software Engineering Professor Holliday

2. Agenda Application Overview Application Overview Class Diagrams Class Diagrams Use Case Scenarios / Sequence Diagrams (if needed) Use Case Scenarios / Sequence Diagrams (if needed) Request Available Flights Request Available Flights Choose Flight or Flights Choose Flight or Flights Book Flight or Flights Book Flight or Flights Demo Demo

3. Application Overview Language – Java 1.4.1 Language – Java 1.4.1 Swing Swing JDBC/ODBC JDBC/ODBC Database – Microsoft Access Database – Microsoft Access Used JavaDoc comments on all public methods Used JavaDoc comments on all public methods Used Suns Coding Convention Used Suns Coding Convention http://java.sun.com/docs/codeconv/ http://java.sun.com/docs/codeconv/ http://java.sun.com/docs/codeconv/

4. Application Overview The application allows users to search for available flights, choose flights, and book flights. The application allows users to search for available flights, choose flights, and book flights. The application credit card validation based on month and 16- digit credit card number The application credit card validation based on month and 16- digit credit card number The application returns a unique confirmation number with the users flight information. The application returns a unique confirmation number with the users flight information. There are eight airport with two hubs: There are eight airport with two hubs: PHX – Phoenix, AZ (HUB) services: PHX – Phoenix, AZ (HUB) services: SLC - Salt Lake City, UT SLC - Salt Lake City, UT LAX – Los Angeles, CA LAX – Los Angeles, CA COS – Colorado Springs, CO COS – Colorado Springs, CO ATL – Atlanta, GA (HUB) services: ATL – Atlanta, GA (HUB) services: ALB – Albany, NY ALB – Albany, NY BOS – Boston, MA BOS – Boston, MA MIA – Miami, FL MIA – Miami, FL

5. 918 1122 927 174 1715 687 229 853 625 319 1222 158 210 798 Numbers denote Available Flight Numbers

6. Class Diagrams Scaled Down Version - Bare Bones Scaled Down Version - Bare Bones Nine of the Main Classes Nine of the Main Classes file://C:\projects\461\docs\ETRSClassDiagram2.gif file://C:\projects\461\docs\ETRSClassDiagram2.gif file://C:\projects\461\docs\ETRSClassDiagram2.gif Complete Version Complete Version Fairly big Fairly big File://C:\projects\461\docs\CompleteClassDiagram2.gif File://C:\projects\461\docs\CompleteClassDiagram2.gif File://C:\projects\461\docs\CompleteClassDiagram2.gif JavaDoc for the project JavaDoc for the project File://C:\projects\461\docs\api\index.html File://C:\projects\461\docs\api\index.html File://C:\projects\461\docs\api\index.html

7. What does it look like?

10. Use Case Scenarios – Request Available Flights NameRequests available flight information SummaryThe 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 EventsCustomerSystem 1. Launches ETRS application2. Displays UI for user to search available flights. 3. Selects origination city 4. Selects destination city 5. Selects type of flight (round trip or one-way) 6. Selects direct or nonstop flights 7. Selects flexible or specific dates of travel 8. Selects departure date 9. Selects departure time range

11. Use Case Scenarios – Request Available Flights 10. Selects return date 11. Select return time range 12. Submit criteria 13. 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. System only provides cities that it services 11. Shows list of flights that met customers criteria.

12. Use Case Scenarios – Request Available Flights ExceptionsCustomerSystem 1. If search criteria is invalid system displays error message. Invalid data is return dates before departure dates and/or the same departure airport and arrival airports 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.

13. Use Case Scenarios – Request Available Flights 2. User acknowledges the message. 3. Displays UI with current criteria, allowing user to modify desired flight information; continues at basic event 9. TriggersCustomer needs flight information. AssumptionsThe customer knows travel information dates, and available budget. Application will display Airports by Airport Code, City and State. Application provides valid dates, like 28 days in February, 31 days in December, January, etc. PreconditionsCustomer has ETRS application installed. PostconditionsCustomer will have a list of flights that met specified travel criteria.

15. Use Case Scenarios – Choose Flights NameChoose a flight. SummaryThe customer has been presented with options for flights to go to his/her destination and a list of returning flights (if round trip travel is selected). The customer chooses a preferred flight. The application puts the seat(s) on hold, and payment information becomes available for the user once flights are on hold. Basic EventsCustomerSystem 1. The customer chooses a preferred flight or flights. Flights are chosen by checking the flights check box to hold a seat on the flight 2. Requests the chosen flight and seat(s) be put on hold while the application is running. Note: that seats are held by decreasing the capacity for selected flights

16. Basic Events3. Displays UI for the user to input payment information once a flight or flights are put on hold. This is done by enabling the payment tab for the customer to input payment information. AlternativesUser doesn't like the flight or flights, user can change the criteria of the schedule (Continue at Use- Case: Request flight information) ExceptionsCustomerSystem 1. Customer closes application after flights are held. 2. Upon closing the application releases seats on held flights Triggers Customer wants hold flights for travel. AssumptionsNone PreconditionsCustomer has a list of available inbound and outbound flights that meet there criteria. User received a list of flights with available seats. All flights remain available while the user decides which flights to select for travel. PostconditionsCustomer will have a flight and seating on hold.

18. Use Case Scenarios – Book Flights NameCustomer books flight or flights SummaryThe application contacts credit card authorization service for payment approval. The service books the flight or flights on hold, and returns a confirmation number to the customer with a brief summary of travel information. Basic EventsCustomerSystem 1. Displays flight(s) on hold and enables the payment form. 2. Confirms flight(s) through a held flight view and inputs preferred payment information. 3. Prompts for final purchase verification. 4. Confirms purchase5. The application sends the request to purchase the ticket(s) (Updates database).

19. Basic Events6. The application provides the customer with a confirmation number and displays the customers iternary and wishes them a good flight. AlternativesNone ExceptionsCustomerSystem 1. Customer is not satisfied with flight arrangement on hold, he/she will be able to cancel and reschedule. Continue at Use- Case: Request available flights Use Case Scenarios – Book Flights

20. 1. If the customers payment information is declined; the application displays an error message and continues at basic event 1. Invalid data are empty data, or incorrect/incomplete credit card information. All credit cards with 16 digit numbers and expiration dates later than the current date are approved. TriggersCustomer wants to purchase flight or flights and seating arrangements on hold. AssumptionsCredit Card authorization is 100% reliable PreconditionsCustomer has placed flight and seating on hold. PostconditionsCustomer has confirmation number and valid e-ticket to travel. Customers credit card will reflect the transaction in the next billing statement.

22. Demo