Sprint 3 Scenarios Use Case Diagrams - Fatima-Essa/Wits-Social-SDP 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 and verify email with first login. |
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. If it is their first time login in, a email validation is first done and then user is successfully logged in.
Basic Flow
User enters details into login fields The system validates and verifies the credentials against that in a database User validated email if logging in for the first time 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 | Navigation Bar |
|---|---|
| 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 all pages in application -The user will be able to use the platforms services |
Brief Description
The user has access to the navigation bar where they can then subsequently choose which page they would like to proceed to.
Basic Flow
User presses the button in nav bar of which they choose to proceed to The system validates the clicked button The user is redirected to the page they have selected
Exceptions:
The user does not choose a button and thus stays on the default homepage.
The system is offline
Use Case Diagram:
| Use Case Name | Add Post Pop-up Page |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires to create a post |
| 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 be able to create a post from this page -The user will be able cancel the request if they like |
Brief Description
The user has access to the post pop-up which has the single functionality of creating a post which contains an image and a caption.
Basic Flow
User navigates to pop-up via nav-bar User can create a post
Exceptions:
The user does not choose to create a post
The system is offline
Use Case Diagram:
| Use Case Name | Homepage |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires use the platforms services namely services available on the homepage |
| 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 all homepage functionality -The user will be able to use the homepages services and view all specific/relevant information |
Brief Description
The user has access to the homepage which has varying functionality. The functionality starts at viewing all posts which a user can inter act with. It then allows the user to view other suggested users and their accounts. This enables the following/unfollowing functionality
Basic Flow
User goes to homepage via nav-bar User can view all posts and interact with them User can view suggested users User can view other users profile pages User can follow/unfollow these account via profile page as well as view their profile specific information. User can save posts at the click of a bookmark button.
Exceptions:
The user does not choose to be on the homepage
The system is offline
Use Case Diagram:
| Use Case Name | Account Profile Page |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires to view account page and all relevant information to the account |
| 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 all account page functionality -The user will be able to use the account pages services and view all account specific information |
Brief Description
The user has access to the account page which has varying functionality such as viewing information such as the amount of following and followers, the users post and the ability to create/update the users profile pic.
Basic Flow
User goes to account profile page via nav bar. User can view all account information. The user can view default bio. The user can view the amount of following and followers they have. User can view their posts and then interact with them. User can view who follows them and who they follow. The user upload a profile pic, view an existing profile pic, or update to a new profile pic.
Exceptions:
The user does not choose to be on the account page
The system is offline
Use Case Diagram:
| Use Case Name | Settings Page |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires use the platforms services namely services available on the settings page |
| 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 all settings page functionality -The user will be able to use the settings page functionality and view all specific/relevant information |
Brief Description
The user has access to the settings page which has varying functionality. The 2 main purposes of the settings page is for the user to change their full name and their bio
Basic Flow
User goes to settings page under profile pic in nav-bar User can change their bio and full name on the settings page
Exceptions:
The user does not choose to be on the settings page
The system is offline
Use Case Diagram:
| Use Case Name | Saved Posts Page |
|---|---|
| Initiating Actor | User |
| Triggering Event | User desires use the platforms services namely services available on the saved page |
| 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 all saved posts -The user will be able to use the saved posts pages functionality and view all specific/relevant information |
Brief Description
The user has access to the saved posts page which has varying functionality. The functionality starts at viewing all posts which a user has saved. Her the user can view/interact with their various saved posts
Basic Flow
User goes to saved posts via nav-bar User can view all saved posts and interact with them
Exceptions:
The user does not choose to be on the saved posts page
The user does not have any saved posts
The system is offline
Use Case Diagram:
