Skip to content

Securely authenticate user accounts FEA106

  • Author: Aaro Kolu
  • Date / Version: 13/02/2024

User roles

  1. User
  2. Administrator

Prerequisites / Conditions

  1. Users should be authenticated for secure user experience.
  2. Users able to create accounts.

Use Case Diagram

uml diagram

Description of use case -eg. Modify existing request

  1. User selects the request they want to modify.
  2. User navigates to the modification screen.
  3. User makes changes to the request details.
  4. User confirms the modifications.
  5. System validates the modified request.
  6. System updates the request with the new information.
  7. System notifies the user of successful modification.

Exceptions

  • E1: Invalid modification input provided by the user.
  • E2: System error prevents the modification process.

Result

  • Expected result of the use case: The selected request is successfully modified with the updated information.

Use frequency

  • The frequency of this use case depends on the number of requests that require modification, but it typically occurs multiple times per day.

Additional information

  • User feedback on the modification process is collected periodically for system improvement.

Sources

This wiki-document is based on the The public administration recommendations

Thans to the original authors.