Use Case
- Author: Son Hoang
- Date / Version: 19/02/2024
User roles
- User: The individual interacting with the application in dark mode.
- User 2: Another individual interacting with the application in dark mode.
Prerequisites / Conditions
- Condition which should be fulfilled
- Condition which should be existing
Use Case Diagram
Description of use case -eg. Modify existing request
- User selects Modify Existing Request:
The User initiates the modification process for an existing request in dark mode.
- System prompts for Request Details:
The system prompts the User to provide details for the modification.
- Admin Reviews Modification:
User 2, the second actor, reviews the modification request.
- Validation and Approval:
The system validates the modification and seeks approval from User 2.
- Update Request:
Upon approval, the system updates the existing request with the modified information.
- Confirmation to User:
The User receives a confirmation of the successful modification.
Exceptions
-
E1: Invalid Modification Request:
-
If the modification request is invalid, an error message is displayed.
-
E2: Approval Denied:
-
If User denies approval, the system notifies the User and maintains the current request state.
Result
- The existing request is successfully modified, and all relevant parties are notified of the update.
Use frequency
- The use case is executed whenever a User needs to modify an existing request, depending on the frequency of request modifications.
Additional information
Sources
This wiki-document is based on the The public administration recommendations
Thans to the original authors.