| Use Case: | Sing Up | Identifier: | UC_2 | |
| Use Case Level: | Player User | |||
| Priority: | High | Complexity: | Medium | |
| Primary Actor: | Player User | Secondary Actor: | N/A | |
| Objective: | User registration in the database. | |||
| Precondition: | The name an email that the user inserted do not exist in the database. | |||
| Post-condition | Success: | The user accesses the web application with their credentials. | ||
| Failure: | The user does not exist in the database, the credentials are invalid ot his email are not validated | |||
| Normal Course | Alternative Course | |||
| 1. The use case begins when the user enters in the "Sing Up" in "Sing In" view. | __________ | |||
| 2. The system displays the login screen. | __________ | |||
| 3. The user enters their "email", "username" and their "password". | __________ | |||
| 4. The user selects the "Sign up" button. | __________ | |||
| 5. The system searches for matches by password and either name or email in the database. | __________ | |||
| 6.a. "Registration successfull." The System displays a info message: "User already registered. We have sent you an email with a validaton code." | 6.b. "The user already exist." The system checks if the email is validated. | |||
| __________ | 6.b.1. "The email are validated." The System displays a info message: "The user is already registered. If you forgot your user or password, click on the Password Restore option." | 6.b.2. "The email is not validated." The System displays a info message: "Email pendint validation. Look in your email for the message with the validation code or click on the Resend code button." | ||
| End of use case | ||||
| Observations: | ||||
| __________ | ||||