CMC

CS230 project by group Thumb Thumbs at SJU.

Authors

Alex Morales-Garcia, Carter Huberty, John Engh, Jack Young, Nick Larson, and Readyson Vang.

Use Cases

U1: Login

Created by Alex

Name:

U1: Login

Actors:

Customer(Admin or User)

Triggers:

Customer goes to website

Preconditions:

User must be registered

Events:

1. User enters credentials
   1. Username entered
   2. Password enterd
2. User clicks "login"

Post-conditions:

1. User is brought to home page
2. User is logged in and authenticated

Alternate:

1. User has invalid Username and/or Password
   1. Screen displayed
2. User can re-enter password

U2: List Saved Schools

Created by Alex

Name:

U2: List Saved Schools (Extends U1)

Actors:

User (Primary)

Triggers:

User clicks on "manage saved schools" from home page

Preconditions:

1. User is not admin
2. user is logged in

Events:

1. user clicks "Manage Saved Schools"
2. User is brought to "Manage Saved Schools"

Post-conditions:

1. User is brought to "Manage Saved Schools" page

Alternate:

N/a

U3: Manage Profile

Created by John

Name:

U3: Manage profile (Extends U1)

Actors:

User (Admin or User) (Primary)

Triggers:

User clicks manage profile button on home screen

Preconditions:

User is logged in

Events:

1. User clicks manage profile button on home screen
2. Manage profile screen is displayed

Post-conditions:

Manage profile screen is displayed

Alternate:

N/A

U4: Search for Schools

Created by John

Name:

U4: Search for Schools (Extends U1, U11)

Actors:

User (Admin or User) (Primary)

Trigger:

User chooses search for school button

Preconditions:

user is logged in; Search box populated

Events:

1. User chooses search option from home screen
2. User types query into search box
3. User presses search button
4. Include U8: View Search Results

Post-conditions:

User is shown search page relating to search query

Alternate:

1. User presses search button without entering query
   1. User is prompted to enter query and continues with step 3 Post-conditions: none

U5: View Individual School

Created by Jack

Name:

U5: View Individual School (Extends U2, U8)

Actors:

User (Admin || User) (Primary)

Triggers:

1. User clicks on a specific school that they wish to view individually from the search results page.
2. User clicks on a specific school that they wish to view individually from the manage saved schools page.

Preconditions:

1. User is logged in.
2. User is either viewing search results (U8) or managing saved schools (U2).

Events:

1. User clicks on the school that they wish to view individually.
2. Brings user to a page displaying all the school's individual statistics and information.

Post-conditions:

User is shown a page displaying all the school's individual statistics and information.

Alternate:

N/A

U6: Remove Schools from List

Created by Jack

Name:

U6: Remove School from List (Extends U2)

Actors:

User (Primary)

Triggers:

User clicks on “Remove School” Button

Preconditions:

1. User is logged in.
2. User is managing saved schools (U2).
3. School they want to remove is in their saved school list.

Events:

1. User selects the ‘remove’ option next to a school in the manage schools page.
2. The selected school is removed from the list.
3. User stays on the manage schools page and continues to manage schools.

Post-conditions:

1. School is removed from the list.
2. User continues managing saved schools.

Alternate:

N/A

U7: Edit User Information

Created by Nick

Name:

U7: Edit User Information (Extends U3)

Actors:

User (Admin || User) (Primary)

Triggers:

User clicks on box with information they want to edit

Preconditions:

1. User is logged in
2. Information they want to edit is not user type or username

Events:

1. User clicks on box relating to information they would like to edit
2. Information box allows user to type new information relating to what they would like to change
3. User clicks save button
4. Information is now changed and saved successfully

Post-conditions:

User has changed and saved information

Alternate:

1. User updates information but does not save before leaving
   1. Information is not saved

Postconditions: User is brought back to main menu

U8: View Search Results

Created by Carter

Name:

Actors:

Triggers:

Preconditions:

Events:

Post-conditions:

Alternate:

U9: Save School to List

Created by Carter

Name: U9:

Save School to List (Extends U5, U8)

Actors:

User (Primary)

Triggers:

User Clicks “Save” Button

Preconditions:

User is logged in

Events:

1. User is doing U8: View Search Results
   1. User Clicks Save School
   2. User is notified the school is saved
2. User is doing U5: View Individual School
   1. User Clicks Save School
   2. User is notified the school is saved

Post-conditions:

School is Saved to the List

Alternate:

1. School is already in Saved Schools List
   1. User is notified the school is already in the list
   2. Post-Condition: None

U10: Manage Users

Name:

U10: Manage Users. (Extends U1: Login)

Actors:

Admin (Primary)

Triggers:

Admin clicks Manage Users button

Preconditions:

1. User must be admin
2. User must be logged in

Events:

1. User clicks on Manage Users
2. User is brought to page to view users

Post-conditions:

User is brought to Manage Users page

Alternate:

N/A

U11: Manage Universities

Name:

U10: Manage Universities (Extends U1)

Actors:

Admin (Primary)

Triggers:

Admin clicks “manage universities button”

Preconditions:

N/A

Events:

1. Admin clicks “manage universities button”

Post-conditions:

Admin is taken to manage universities page

Alternate:

N/A

U12: Add University

Created by Readyson

Name:

U12: Add University. (Extends U11)

Actors:

Admin (primary)

Triggers:

Admin clicks Add a new University

Preconditions:

1. Admins only
2. Must be logged in
3. Must enter a unique school name

Events:

1. Admin clicks on Add a new University
2. Admin fills out required school information
3. Admin clicks Add School
4. School is added to list of schools

Post-conditions:

There is a new school added to the list.

Alternate:

1. Admin clicks Cancel Changes button
   1. Information entered is deleted
   2. Admin is brought back to Manage Universities menu
   3. Post-Condition: Admin is now at Manage Universities menu
2. Not all information is entered/not entered correctly/Information conflicts with existing university
   1. Admin is given message about what needs to change
   2. Post-Condition: None

U13: Logout

Created by Readyson

Name:

U13: Logout (Extended by U1)

Actors:

Admin (Primary), User (Primary)

Triggers:

User clicks the logout button

Preconditions:

1. User must be registered
2. User must be already logged in

Events:

1. User clicks logout button
2. User is logged out.

Post-conditions:

User is not logged in anymore. User is returned to the log in screen.

Alternate:

N/A

U14: Add User

Name:

U14: Add User

Actors:

Admin (Primary)

Triggers:

User click Add User button

Preconditions:

1. User is logged in
2. User is admin

Events:

1. User clicks on Add User button
2. User enters information necessary for each user
3. User clicks Add User button
4. New user is successfully created

Post-conditions:

1. New user is created
2. Admin is brought back to Manage Users menu

Alternate:

1. User clicks Reset button after filling out partial/all information
   1. Any information that has been entered is deleted
   2. Post-Condition: Admin is left with blank Add User menu
2. User clicks Add User button before all information is entered
   1. Admin is prompted to fill out all information
   2. Post-Condition: None
3. Information about new user conflicts with information about another user/information given does not meet user requirements
   1. Message is given to user about information that needs to change
   2. Post-Condition: None

U15: Edit User

Name:

U15: Edit User (Extends U10)

Actors:

Admin (Primary)

Triggers:

User clicks on Edit User button

Preconditions:

1. User must be admin
2. User must be logged in
3. User must be at U10: Manage Users

Events:

1. User may enter any information they would like to update/change
2. User clicks the Save User Information button

Post-conditions:

1. New user information is saved to the DB
   1. User is notified that the information has been saved successfully
   2. User is brought back to U10: Manage Users

Alternate:

1. User enters invalid Information
   1. User is notified they have entered invalid information
   2. Post-Condition: None

U16: Edit University Information

Name:

U16: Edit University Information (Extends U5)

Actors:

Admin (Primary)

Triggers:

User clicks the Edit University button

Preconditions:

1. User must be admin
2. User must be logged in
3. User must be at U5: View Individual School

Events:

1. User may enter any information they would like to update/change
2. User clicks the Save University Information

Post-conditions:

1. New university information is saved to the School and DB
   1. User is notified that the information has been saved successfully
   2. User is brought back to U5: View Individual School

Alternate:

1. User clicks Cancel Changes
   1. All information is reverted to previous information
   2. Post-Condition: None

U17: Blacklist University

Created by Nick

Name:

U18: Blacklist University (Extends U5)

Actors:

User (Primary)

Triggers:

User Clicks “Blacklist” Button

Preconditions:

N/A

Events:

1. User is doing U5: View Individual School
   1. User Clicks Blacklist School
   2. User is notified that the school is Blacklisted

Post-conditions:

School is Saved to the Blacklist

Alternate:

1. School is already in Blacklist
   1. User is notified the school is already in the list
   2. Post-Condition: None