1. WEST Presented By 3s

2. Introduction Project Overview Project Overview Use Case Diagram Use Case Diagram Domain Model Diagram Domain Model Diagram UI for Search Route Use Case UI for Search Route Use Case Sequence Diagram Sequence Diagram State Diagram State Diagram Non-Functional Requirement Non-Functional Requirement List of Outstanding Issue/Problems List of Outstanding Issue/Problems

3. Project Overview Current Problem Current Problem –Difficulty for searching travel routes –Not always efficient routes –Not always cheapest routes Our Solution Our Solution –Web-Enabled Scheduling of Travel (WEST)

4. Use Case Diagram

6. Search Route Use Case UC2: Search for Route UC2: Search for Route Overview: To search for a specific travel route. Overview: To search for a specific travel route. Event: Search route. Event: Search route. Pre-condition: It is assumed that the user is logged in with a valid account. Pre-condition: It is assumed that the user is logged in with a valid account. Post-condition: A route has been found that matches the users parameters. Post-condition: A route has been found that matches the users parameters. System: Account management System, Travel Search System, Booking System. System: Account management System, Travel Search System, Booking System. Actors: User, Travel Information website, Google Maps. Actors: User, Travel Information website, Google Maps. Related Use Cases: Create booking, Modify Booking, Modify Route, Login Related Use Cases: Create booking, Modify Booking, Modify Route, Login

7. UI for Search Route

11. State Diagram for something

12. Non-Functional Requirement The system should be able to interface with other applications. For example Google maps, Greyhound, Expedia.ca, etc.. The system should be able to interface with other applications. For example Google maps, Greyhound, Expedia.ca, etc.. The System should be easy to use. The System should be easy to use. –Users familiar with the web should not get lost using the website –New users to the web should be able to learn how to use the site within a couple hours. The application will have a downtime of no more then 2 hours a month. The application will have a downtime of no more then 2 hours a month. The application must be able to communicate with the Customer Information Database The application must be able to communicate with the Customer Information Database The system needs to be able to handle 1,000 requests simultaneously with a response time of 100ms. The system needs to be able to handle 1,000 requests simultaneously with a response time of 100ms. The application is being developed using PHP and Ajax standards to ensure Travelite employees can maintain it. The application is being developed using PHP and Ajax standards to ensure Travelite employees can maintain it.

13. List of Outstanding Issue/Problems History of User History of User Unclear as to what information we will need to keep when creating the user Unclear as to what information we will need to keep when creating the user If a user books twice, it is up to the employee to decide what to do If a user books twice, it is up to the employee to decide what to do Modify Route Use Case update. User can modify the current search only. Modify Route Use Case update. User can modify the current search only. Modify Reservation is used when changing existing reservations. Modify Reservation is used when changing existing reservations.

14. Questions ?

15. Suggestion for Course More Elicitation Sessions More Elicitation Sessions