top of page
USE CASES (UML AND TEXT)

Use Cases - Log In System - Sample


Use Cases 1 - External


Use Case 1.1 New Customer - Customer Registration

  • If the user doesn't have a valid login, the user will fill out the New User Registration form and save the information.

  • The system will save this information to a temporary authorization table in the database.

  • The system will display a message that the login is waiting for administration authorization or an instructional error message if the registration was not successful.


Use Case 1.2. Update Existing Customer

  • If the user has a valid login but would like to make a change, the user will fill out the Modify Login form and save the information.

  • The system will save the information to the main database.

  • The system will display a message that the user account has been successfully changed or an instructional error message if the change was not successful.


Use Case 1.3. Remove Existing Customer

  • If the customer wishes to remove their login, they will select a Remove option.

  • The system will set a flag to an inactive flag in the table in the database which will make the log in invisible and inaccessible from the web interface.

  • A message will display indicating that their log in is in process of being removed.

  • If the user attempts to log in with this login after removing it a message will display indicating that it is in the process of being removed or has been removed.


Use Case 1.4. Log In to the System

  • The user will enter their log in name and password and log in to the system.

  • The system will authenticate the log in and password.

  • If they are valid the user will be authorized and logged in.

  • If they are invalid an instructional error message will be displayed.


Use Cases 2 - Internal
Use Case 2.1. New Customer - Administrator Authorization

  • The administrator will display the list of users requiring authorization, set the access level, authorize the user and save the changes.

  • The system will save the information to the main database and clear the temporary authorization database.

  • The system will send an email to each user successfully saved, notifying them that they are now authorized to log in to the system.

  • The system will display the list of users which were saved successfully and a list of users which were not saved successfully with an instructional error message for each user.

 

Use Case 2.2.1. Administrator Removal - Customer initiated

  • The administrator will display the list of users requiring removal, remove them and save the changes.

  • The system will set the flag to a removal flag and save the change to the main database.

  • The system will send an email to each user successfully removed, notifying them that they are now removed from the system.

  • The system will display the list of removals which were saved successfully and a list of removals which were not saved successfully with an instructional error message for each user.


Use Case 2.2.2. Administrator Removal - Administrator initiated

  • The administrator will search for the user requiring removal, remove them and save the changes.

  • The system will set the flag to a removal flag and save the change to the main database.

  • The system will send an email to each user successfully removed, notifying them that they are now removed from the system.

  • The system will display a message indicating the removal was successfully or an instructional error message.


Use Case 2.3. Adminstrator Browse

  • The administrator can browse a complete list of all users.


Use Case 2.4. Administrator Search

  • The administrator can search and display any user both active and inactive.


Use Case 2.5. Administrator Modification

  • The administrator will change the access level or status of any user using an update form and save the change. The system will update the main database.

  • A message will display indicating a successful update or if the update was unsuccessful an instructional error message will display.


Use Case 2.6. Administrator Creation

  • The administrator will create a new user account on behalf of a user who would like a log in using an administrator registration form which includes the ability to set the access level and save it to the main database.

  • The system will authorize the user and save it to the main database.

  • A message will display indicating a successful addition or if the addition was unsuccessful an instructional error message will display.

bottom of page