Skip to content

Feature 03: Use Cases for User Self-Service Profile

Version Date Author Change Description
1.0 2025-09-04 Senior Business Analyst Initial Draft (with password management)
2.0 2025-09-11 Senior Systems Analyst Revised for Google SSO; removed password functionality

1.0 User Stories

  • US-06 (v2.0): As a user, I want to view and edit my profile information so that I can keep my details up-to-date.

2.0 Use Case: View and Edit Profile

This use case details the process of a user viewing their own profile and editing mutable information.

  • Use Case ID: UC-03
  • User Story: US-06
  • Actors:
  • User (any authenticated user)
  • System
  • Trigger: The user navigates to the "My Profile" page from the application's user menu.

2.1 Main Success Scenario

  1. The User clicks on their name in the application header and selects "My Profile" from the dropdown menu.
  2. The System displays the "My Profile" page.
  3. The User can view their profile information, including their email address, display name, account status, and assigned roles/groups. The email, status, roles, and groups are presented as read-only.
  4. The User clicks an "Edit" button.
  5. The "Display Name" field becomes editable.
  6. The User enters a new display name.
  7. The User clicks "Save".
  8. The System validates the new display name (e.g., ensures it is not empty).
  9. The System saves the change and displays a success confirmation message. The "Display Name" on the page updates to the new value.
  10. Postconditions:
  11. The user's display name is updated in the database.
  12. The new display name is reflected in the UI, including the application header.

2.2 Alternative & Exception Flows

  • 2.2a: User Enters Invalid Data
  • At step 6 of the main flow, the user deletes their display name, leaving the field empty.
  • The User clicks "Save".
  • The System detects the validation error and displays an inline message, such as "Display Name cannot be empty." The change is not saved.
  • 2.2b: User Cancels the Edit
  • At step 6 of the main flow, the user changes their display name.
  • Instead of clicking "Save," the User clicks "Cancel".
  • The System discards the changes, and the "Display Name" field reverts to its original, pre-edit value.