Sprint 2 Scenarios Use Case Diagrams - root-mrrobot/wits-academy GitHub Wiki
| Use Case Name | Registration |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires to create an account on the platform |
| Preconditions | -The user must have access to an internet connection -The user must have access to the platform |
| Postconditions | -The user's details will be stores in the database -The user will be able to login with these credentials. |
Brief Description
The user is prompted to create an account on the platform. They enter their details, it gets validated and the registration is successful
Basic Flow:
User enters details into registration fields The system validates and verifies the details and stores details in a database The system creates an account for the user The user is able to login with these credentials
Exceptions:
The user enters invalid information
The user already has an account
The system is offline
Use Case Diagram:
| Use Case Name | Login |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires to log into platform |
| Preconditions | -The user must have access to an internet connection -The user must have access to the platform |
| Postconditions | -The user's will be redirected to the home landing page -The user will be able to use the platforms services |
Brief Description
The user is prompted to enter their login credentials on the platform. They enter their details, it gets validated and the login is successful
Basic Flow
User enters details into login fields The system validates and verifies the credentials against that in a database The user is redirected to the home landing page
Exceptions:
The user enters invalid credentials The system is offline
Use Case Diagram:
| Use Case Name | Landing Home Page |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires use the platforms services |
| Preconditions | -The user must have access to an internet connection -The user must have access to the platform - The user must be registered and logged in |
| Postconditions | -The user's will have access to either the teacher or student view -The user will be able to use the platforms services in either view |
Brief Description
The user is prompted to between proceeding as a teacher or a student. The decide upon which to proceed as and press the corresponding button, it gets validated and the user is successfully redirected to the homepage of either view.
Basic Flow
User presses the button of which they choose to proceed as (teacher or student) The system validates the clicked button The user is redirected to the homepage of the view that they have selected
Exceptions:
The user does not choose to proceed as either.
The system is offline
Use Case Diagram:
| Use Case Name | Student View |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires to act as a student and have access to services available to students |
| Preconditions | -The user must have access to an internet connection -The user must have access to the platform - The user must be registered and logged in -The user must be in student view |
| Postconditions | -The user's will have access to student view -The user will be able to use the platforms services in student view |
Brief Description
The user has chosen to be a student in student view in this instance. There is a lot of functionality available in the student view. Using the navigation bar you can either be on the homepage viewing all courses, the subscriptions page viewing your subscriptions to the account page viewing your account and being able to change to teacher view. When any button is pressed it gets validated and the user is the successfully redirected to the subsequent page.
Basic Flow
User presses the navigation button of which fragment they wish to view The system validates the clicked button The user is redirected to the correct fragment that they have selected and the user now has access to all functionality of said fragment.
Exceptions:
The system is offline
User is in teacher view
Use Case Diagram:
| Use Case Name | Teacher View |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires to act as a teacher and have access to services available to teachers |
| Preconditions | -The user must have access to an internet connection -The user must have access to the platform - The user must be registered and logged in -The user must be in teacher view |
| Postconditions | -The user's will have access to teacher view -The user will be able to use the platforms services in teacher view |
Brief Description
The user has chosen to be a teacher in teacher view in this instance. There is a lot of functionality available in the teacher view. Using the navigation bar you can either be on the homepage adding a course as a teacher, the courses page viewing the courses you have created to the account page viewing your account and being able to change to student view. When any button is pressed it gets validated and the user is the successfully redirected to the subsequent page.
Basic Flow
User presses the navigation button of which fragment they wish to view The system validates the clicked button The user is redirected to the correct fragment that they have selected and the user now has access to all functionality of said fragment.
Exceptions:
The system is offline
User is in student view
Use Case Diagram:
