Sample Use-Case Descriptions for an Application that Tracks Revisions and Modifications Made to Software Applications

Log into and out of the System

Use case name: Login/ Logout Primary actor: User Stakeholders and interests: Clients employee Wants to log into the system Supervisor - Wants to log into the system Staff Wants to log into the system Brief description: This describes how the users log into the system to view or modify requests, including any attached notes Precondition: The user opens the application log in box Trigger: The user enters their id number and password Relationships: Association: Include: Extend: Normal flow of events: 1. The user enters their login id and password A. If the login and password is valid, a session is opened. i. ii. The security is verified. The menu is loaded. Users ID: 1 Priority: High

Use case type: Detail, essential

B. If the login or password is not valid, an error message is displayed. i. ii. 2. The user clicks an ok button. The user is returned to login screen.

The user clicks the logout button i. ii. The session is terminated. The window is closed.

Display the Menu

Use case name: Display/Select Menu Primary actor: User Stakeholders and interests: Clients employee Wants to be able to select an item from the Menu Supervisor - Wants to be able to select an item from the Menu Staff Wants to be able to select an item from the Menu Brief description: This explains how the user can select from the menu to view, create or modify requests, including any attached notes. Users can display reports from the menu as well. Precondition: A session has been opened successfully Trigger: None Relationships: Association: Include: Extend: Login / Logout DisplayRequest, DisplayReports, Create/ ModifyRequest ID: 2 Priority: High

Use case type: Detail, essential

Normal flow of events: 1. 2. 3. 4. 5. 6. If the user selects Display Request, opens a form asking for a request number. If the user selects Create Request, opens a blank request form. If the user selects Modify Request, opens a form asking for a request number. If the user selects Display Reports, opens a form listing available canned reports. If the supervisor selects Modify Tables, a form listing available tables to edit. If the user selects Logout, the session is closed.

Create and Modify Requests

Use case name: Create/ModifyRequest Primary actor: User Stakeholders and interests: Clients employee Wants to edit or create request Supervisor - Wants to edit or create request Staff Wants to edit or create request Brief description: This use case describes how to create and modify requests. Precondition: Menu is displayed. Trigger: User clicks on Create/Modify request from Display/ Select Menu Relationships: Association: Include: Extend: DisplayNotes, CreateModifyNotes ID: 3 Priority: High

Use case type: Detail, essential

Normal flow of events: 1- If user selects Create Request: A- The system display blank view B- The user enters the information i. If the user clicks save, a request number is assigned and the ability to add notes comes available. ii. If the user clicks cancel, the user is returned to the menu without saving changes.

C- The user clicks close window and returns to Display/Select Menu 2- If user selects Modify Request: A- A screen displays asking for the user to enter the request number B- Enter request number C- Request is displayed and populated with the data for the entered request. i. ii. iii. If the user clicks save, the data is updated in the database. If the user clicks cancel, the user is returned to the menu without saving changes. If the user clicks Notes, the Notes page is displayed.

D- The user clicks close window and returns to Display/Select Menu

Display Requests
Use case name: DisplayRequest Primary actor: User Stakeholders and interests: Clients employee Wants to view request Supervisor - Wants to view request Staff Wants to view request Brief description: This describes how the user can view a request. Precondition: Menu is displayed Trigger: User clicks Display Request from the Menu Relationships: Association: Include: Extend: DisplayNotes, CreateNotes ID: 4 Priority: High

Use case type: Detail, essential

Normal flow of events: 1- A screen displays asking for the user to enter the request number 2- Enter request number 3- Request is displayed and populated with the data for the entered request. A. The user clicks the Notes button to access the Notes OR B. The user clicks close window and returns to Display/Select Menu.

Create Notes
Use case name: CreateNotes Primary actor: User Stakeholders and interests: Clients employee wants to create notes Supervisor - wants to create notes Staff wants to create notes Brief description: This describes how the user can create notes. Precondition: DisplayRequest or Create/ModifyRequest Trigger: User clicks on the Create Note button from the Request View Relationships: Association: Include: Extend: Normal flow of events: 1- The system displays a form with fields to add a note and any notes for the request listed underneath in a new window. 2- User enters field information and clicks add. 3- The user clicks close window and returns to Display/Select Menu ID: 5 Priority: High

Use case type: Detail, essential

Display Reports
Use case name: DisplayReports Primary actor: User Stakeholders and interests: Clients employee Wants to view canned reports Supervisor - Wants to view canned reports Staff Wants to view canned reports Brief description: This describes how the user can view reports. Precondition: Display / Select Menu Trigger: User clicks Display Reports from the Menu to view reports Relationships: Association: Include: Extend: Normal flow of events: 1- A list of available canned reports for the appropriate user group, supervisor, employee client, or staff, are displayed. 2- The system displays selected report. 3- User clicks Return to Main Menu returning to Display/Select Menu or Open another Report retuning user to step 1. ID: 6 Priority: High

Use case type: Detail, essential

Create and Modify Tables

Use case name: Create/ModifyTable Primary actor: Supervisor Stakeholders and interests: Supervisor - Wants to create or modify tables. Brief description: This describes how the Supervisor can create and modify the drop down tables needed for system. Precondition: Supervisor is logged into the system. Trigger: Supervisor selects Create/ Modify Table from the menu Relationships: Association: Include: Extend: Normal flow of events: 1 - Supervisor can choose Create/Modify Tables from the menu. A- The system displays a list of tables that can be modified 2 - Supervisor makes changes to the tables 3 - When finished, returns to menu Supervisor ID: 8 Priority: High

Use case type: Detail, essential