Skip to content

Use Cases

Jump to bottom
Laura Casals edited this page Sep 28, 2021 · 4 revisions

Search

  1. Description:
    The user can search for public-level user accounts and their Experiences.

  2. Actors:
    2.1. User
    2.2. System

  3. Preconditions:
    3.1. The user has internet access
    3.2. The website is accessible.

  4. Primary Flow of Events:
    4.1. The user goes to the website.
    4.2. The user enters search criteria.
    4.3. The system will display relevant information.
    4.4. The user can sort only public search results by username, Experience, Path, and Experience-Career relationship.

  5. Alternate Flow: Follower-Only Search
    5.1. The user must initiate Login.
    5.2. The user enters search criteria.
    5.3. The system will display relevant information.
    5.4. The user can sort public and follower-only search results by username, Experience, Path, and site-wide Triple Graph data based on said search results.

Create an account

  1. Description:
    The user will input an email address and unique password to create a new account and secure it.

  2. Actors:
    2.1. User
    2.2. System

  3. Preconditions:
    3.1. The user has internet access
    3.2. The website is accessible.

  4. Primary Flow of Events:
    4.1. The user will input a valid email address.
    4.2. The user will input a unique password. The password must satisfy current best practices for password length and complexity to pass system input validation.
    4.3. The system highlights the data fields in green for valid input.
    4.4. The user clicks on submit.
    4.5. The system will present notice that the user must verify their new account through an automated email.
    4.6. The user clicks the confirmation button in the email and is taken to the website to log in.

  5. Alternate Flow: Invalid Email or Password Format
    5.1. Start at Step 4.2.
    5.2. The user inputs an invalid email address or password.
    5.3. The system highlights the data fields in red containing invalid input and a message to correct input errors. In addition, the system mutes the submit button until the user input is valid.
    5.4. The user inputs correct information.
    5.5. Continue at Step 4.3.

User Login

  1. Description:
    The user will use their email address and password to access their account.

  2. Actors:
    2.1. User
    2.2. System

  3. Preconditions:
    3.1. The user has internet access
    3.2. The website is accessible.

  4. Primary Flow of Events:
    4.1. The user will go to the web website and click the login button.
    4.2. The system will take the user to the login page.
    4.3. The user will input their correct email address and password.
    4.4. The system will highlight the data fields green for proper input formatting.
    4.5. The system will confirm the user input.
    4.6. Finally, the system will take the user to their account.

  5. Alternate Flow:Invalid Email Address or Password Format
    5.1. The system initiates Alternate Flow: Invalid Email Address or Password Format.

  6. Alternate Flow: Invalid Login Combination (Email Address and Password)
    6.1. The system will prompt the user that the email address and password combination are incorrect.
    6.2. The system will also prompt the user to
           6.2.1 Correct their input and try again
           6.2.2 Or to click Reset Password.
    6.3. The user enters the correct email/password combination.
    6.4. Continue with Step 4.5

  7. Alternate Flow: Reset Password
    7.1. The system will take the user to the Reset Password webpage.
    7.2. The system will prompt the user to enter their email address and to click submit.
    7.3. The system will email the user with a unique one-time link to reset the password.
    7.4. The user will click the link in the email.
    7.5. The system will take the user to a webpage to enter a new password.
    7.6. The user will enter a new password twice in two separate data fields.
    7.7. The system will highlight the data fields in green for proper password length and complexity or highlight in red otherwise. (Similar to Steps 5.2-5.4.)
    7.8. The system confirms valid input and sends a confirmation email to the user for the change.

Create a Journey

  1. Description:
    The user will create a workspace called a Journey.

  2. Actors:
    2.1. User
    2.2. System

  3. Preconditions:
    3.1. The user has internet access
    3.2. The website is accessible.

  4. Primary Flow of Events:
    4.1. The user can click the add button to add a Journey to the list in their account.

Create a Path

  1. Description:
    The user will add a Path.

  2. Actors:
    2.1. User
    2.2. System

  3. Preconditions:
    3.1. The user has internet access
    3.2. The website is accessible.

  4. Primary Flow of Events:
    4.1. The user must Create a Journey.
    4.2. The user can click add to place a path into the Journey.

Create an Experience

  1. Description:
    The user will start an experience.

  2. Actors:
    2.1. User
    2.2. System

  3. Preconditions:
    3.1. The user has internet access
    3.2. The website is accessible.

  4. Primary Flow of Events:
    4.1. The user must Create a Journey.
    4.2. The user must Create a Path.
    4.3. The user can click add to place an Experience onto a Path.

This is the footer

Wiki

Milestone 1

Clone this wiki locally