Securely authenticate user accounts FEA106
- Author: Aaro Kolu
- Date / Version: 13/02/2024
User roles
- User
- Administrator
Prerequisites / Conditions
- Users should be authenticated for secure user experience.
- Users able to create accounts.
Use Case Diagram
Description of use case -eg. Modify existing request
- User selects the request they want to modify.
- User navigates to the modification screen.
- User makes changes to the request details.
- User confirms the modifications.
- System validates the modified request.
- System updates the request with the new information.
- 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.