| Use Case Name: | Account Log In |
|---|
| Use Case Id | 3 |
| Priority | 1 |
| Level | User Goal |
| Primary Business Actory | Customer |
| Other Participating Actors | System Administrator |
| Description | Customer need to log into their account in order to confirm bookings. |
| Preconditions | Customer must already signed up for an account |
| Stakeholders & Interests |
- Customer:
- Wants to be able to confirm bookings on the Ebundle System
- Company:
- Wants to draw in more customers to increase revenue for the company
- System Administrator:
- Wants to be able to track number of users using the system each day
|
| Typical Scenarios |
- Customer enters the email address
- Customer enters the password
- The system valids the email and password
- The system confirms customer has suceesfully log into their account
|
| Extensions/ Alternative Scenarios |
- Invalid password: customer is asked to re-enter their password.
- Invalid email: customer asked to re-enter their email address
- Account does not exist: customer is asked to sign up for an account.
|
| Conclusion | customer successfully logs into their account |
| Post Conditions | customer can now confirm bookings or purchase concert tickets |
| Business Rules |
- One account per valid email
|
| Implementation Constraints |
- Email address Validation: check if email address match database record
- Password Validation: check if password match database record
|