Use Case Name: | Search transport |
Use Case Id | 7 |
Priority | 7 |
Source | |
Primary Business Actory | Customer |
Other Participating Actors | |
Description | Customer searches for ltransport |
Preconditions | A customer must have an account and be logged in |
Trigger | |
Typical Scenario |
- A customer requests search for transport option
- The system determines the customers location & brings up different
forms of transport nearby
- The system requests the user to enter the date and location of departure & arrival
- The system finds all different forms of transport with the corresponding costs, times
on that date doing fitting as close as possible with the customer's requirements
- The customer chooses a form of transport
|
Alternative Scenario |
- No transport available in location specified: The system returns
with the nearest available transport to the specified location
- Filtered locations do not return a search: The systems suggests other events in
nearby locations
- The system cannot determine the customers location
- The customer chooses not to purchase a transport option
|
Conclusions | A customer is able to search for events on a specified date |
Post Conditions | A customer can book transport |
Business Rules |
- The system will only bring up events 6 months in advance
- The system cannot bring up bygone events
|
Implementation Constraints | |