WEST Presented By 3s. Introduction Project Overview Project Overview Use Case Diagram Use Case...
-
Upload
corey-gibson -
Category
Documents
-
view
222 -
download
3
Transcript of WEST Presented By 3s. Introduction Project Overview Project Overview Use Case Diagram Use Case...
IntroductionIntroduction
• Project OverviewProject Overview
• Use Case DiagramUse Case Diagram
• Domain Model Diagram Domain Model Diagram
• UI for Search Route Use Case UI for Search Route Use Case
• Sequence DiagramSequence Diagram
• State DiagramState Diagram
• Non-Functional Requirement Non-Functional Requirement
• List of Outstanding Issue/ProblemsList of Outstanding Issue/Problems
Project Overview Project Overview
• Current ProblemCurrent Problem– Difficulty for searching travel routesDifficulty for searching travel routes– Not always efficient routesNot always efficient routes– Not always cheapest routesNot always cheapest routes
• Our SolutionOur Solution– Web-Enabled Scheduling of Travel Web-Enabled Scheduling of Travel
(WEST)(WEST)
Search Route Use CaseSearch Route Use Case
• UC2UC2: Search for Route: Search for Route• Overview: Overview: To search for a specific travel route.To search for a specific travel route.• Event: Event: Search route.Search route.• Pre-condition:Pre-condition: It is assumed that the user is It is assumed that the user is
logged in with a valid account.logged in with a valid account.• Post-conditionPost-condition: A route has been found that : A route has been found that
matches the users parameters.matches the users parameters.• System: System: Account management System, Travel Account management System, Travel
Search System, Booking System.Search System, Booking System.• Actors: Actors: User, Travel Information website, Google User, Travel Information website, Google
Maps.Maps.• Related Use Cases: Related Use Cases: Create booking, Modify Create booking, Modify
Booking, Modify Route, LoginBooking, Modify Route, Login
Non-Functional RequirementNon-Functional Requirement• The system should be able to interface with other The system should be able to interface with other
applications. For example Google maps, Greyhound, applications. For example Google maps, Greyhound, Expedia.ca, etc..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 websiteUsers 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 New users to the web should be able to learn how to use the site within a
couple hours. couple hours.
• The application will have a downtime of no more then 2 hours The application will have a downtime of no more then 2 hours a month.a month.
• The application must be able to communicate with the The application must be able to communicate with the Customer Information DatabaseCustomer Information Database
• The system needs to be able to handle 1,000 requests The system needs to be able to handle 1,000 requests simultaneously with a response time of 100ms.simultaneously with a response time of 100ms.
• The application is being developed using PHP and Ajax The application is being developed using PHP and Ajax standards to ensure Travelite employees can maintain it.standards to ensure Travelite employees can maintain it.
List of Outstanding List of Outstanding Issue/ProblemsIssue/Problems
• History of UserHistory of User• Unclear as to what information we will Unclear as to what information we will
need to keep when creating the userneed to keep when creating the user• If a user books twice, it is up to the If a user books twice, it is up to the
employee to decide what to doemployee to decide what to do• Modify Route Use Case update. User can Modify Route Use Case update. User can
modify the current search only.modify the current search only.• Modify Reservation is used when changing Modify Reservation is used when changing
existing reservations.existing reservations.