| Use Case Name: | Search for concert/performance location |
|---|
| Use Case Id | 5.3 |
| Priority | 5.3 |
| Source | |
| Primary Business Actory | Customer |
| Other Participating Actors | |
| Description | Customer searches for locations of concerts/performances |
| Preconditions | A customer must have an account and be logged in |
| Trigger | |
| Typical Scenario |
- A customer requests the search concert/performance location option
- The system determines the locations of all the concert venues
- The system determines the current date and the customers location.
The system then selects all the concerts/performances for up to 6
months in advance in the country of the user
- The customer can look at the events
- The customer can also specify a certain location
- The customer chooses to look at concerts
|
| Alternative Scenario |
- No concerts/performances available in location specified: The system returns
with an error message & suggests other events
- Filtered locations do not return a search: The systems suggests other events in
nearby locations
- Bygone Date: The customer selects a bygone date. The system outputs and error warning
- The system cannot determine the customers location. The system brings up all events in the same country
|
| Conclusions | A customer is able to search for events in specific locations |
| Post Conditions | Success: A customer can select a concert/perfomance to purchase tickets for etc.
Failure: The system cannot bring up any events for a time period specified and suggests other event dates nearby |
| Business Rules |
- The system will only bring up events 6 months in advance
- The system cannot bring up bygone events
- The system prioritises nearby events for a customer. Determines the customers IP address location
|
| Implementation Constraints | |