Below you can find the UML Diagram for the Use Cases of Britizen! As can be noted, all the main actions require the User to be previously logged into the system. Otherwise, it is possible to create an account following the corresponding link.
Use Case UML Diagram of Britizen
Users can manage the requests they recieve, create new ones, browse information about themselves or their friends, and create, edit, share or delete posts.
Keep visiting the blog to find more information coming soon. New UML Diagrams will be available in the following days!
You can find here the different Use Case Scenarios that describe the main functionalities and interactions of Britizen. For each scenario, we include the necessary pre-conditions, the steps taken by the user, the results, and the possible alternative paths that can be taken.
User creates an account on mobile without Facebook integration
Pre-requisites:
User has a smartphone
User is aged 15+
User is a British Citizen with a National Insurance Number
User has downloaded the app
Process:
User opens app on smartphone and is shown the login/create account page
User clicks create account
User inputs First Name, Last Name, Date of Birth, Address, National Insurance, Email Address
User clicks create
User is sent confirmation email to very email
Result:
The User has created a new account and can access the features of the system from any device.
Alternative Paths:
The data introduced by the user is invalid. The user is requested to repeat the process inputting valid data.
User creates an account on desktop/laptop without Facebook integration
Pre-requisites:
User has access to a desktop/laptop
User is aged 15+
User is a British Citizen with a National Insurance Number
Process:
User navigates to Britizen home page
User clicks create an account
User inputs First Name, Last Name, Date of Birth, Address, National Insurance, Email Address
User clicks create
User is sent confirmation email to very email
Result:
The User has created a new account and can access the features of the system from any device
Alternative Paths:
The data introduced by the user is invalid. The user is requested to repeat the process inputting valid data
User checks Britizen Score on Mobile
Pre-requisites:
User owns a smartphone with Britizen app downloaded
User has a Britizen account
User is not currently logged in
Process:
User opens application and is shown the home page
User either logs in via facebook or enters their email address and password
User presses “My Britizen Score” page and is shown their score page
Result:
The user has successfully checked his/her Britizen score
Alternative Paths:
The data introduced by the user to Log In is invalid. The user is requested to repeat the process inputting valid data
User checks Britizen Score on desktop/laptop
Pre-requisites:
User has access to a desktop/laptop
User has a Britizen account
User is not currently logged in
Process:
User navigates to Britizen website
User logs in via facebook or entering their email and password
User is shown their news feed
User selects “My Britizen Score” and is shown their score
Result:
The user has successfully checked his/her Britizen score
Alternative Paths:
The data introduced by the user to Log In is invalid. The user is requested to repeat the process inputting valid data
User joins a group
Pre-requisites:
User has a Britizen account
User is logged in and on the home page
Process:
User navigates to the group’s page by searching
User clicks request to join
Group admin is notified of request and makes a decision about it
Result:
The admin of the group accepts the request and the user has successfully joined the group. User is notified
Alternative Paths:
The admin of the group declines the request to join. User is notified
User sends a friend request
Pre-Requisites:
User has a britizen account
User is logged in and on the home page
User has a friend they want to send a request to
Process:
User searches for their friend
User finds their friend’s profile
User clicks send a friend request button
Potential friend is notified of request and makes a decision about it
Result:
The potential friend accepts the request and the user is now his friend. User is notified
Alternative Paths:
The potential friend declines the friend request. User is not notified about this for privacy reasons
User checks friends score
Pre-requisites:
User has a Britizen Account
User has a friend on Britizen
Process:
User searches for their friend on Britizen
User views their friend’s profile which includes their score
Result:
User has successfully checked his friends score.
Alternative Paths:
No alternative paths as scores will be public for any friend.
User writes and shares a post
Pre-requisites:
User has a Britizen Account
User has logged in to the system.
Process:
User writes the contents of the new post in the correspondent text box. The user can include references and links to other websites or videos.
User clicks on the Post button.
Result:
User has created a new post and now it is available for all his friends.
Alternative Paths:
User decides to not create the post and clicks the Cancel button. The content of the post is deleted.
