System use case specification request specimen data change - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
|
|
| Identification |
UC30 |
| Use case |
Request Specimen Data Change |
| Actors |
User |
| Stakeholders and interests |
Field Technician: Needs to correct errors or update field data after initial entry. Administrator: Requires oversight and approval of data modifications for integrity. |
| Pre-conditions |
The user is viewing the complete details of a specimen (UC29 has been executed). |
| Minimum guarantees |
System ensures all change requests include a mandatory comment. |
| Success guarantees |
A change request is successfully registered, marked as "Pending" or "For Review," and administrators are notified. |
Main Success Scenario
| User Action |
System Response |
| 1. This use case begins when the user, on the specimen details screen, selects the "Request Change" option. |
2. The system presents a change request form, pre-filled with the current specimen data. Editable fields are: PLOT, SPECIES, HEIGHT (m), CBH (cm). A mandatory "Change Comment" text field is also present. |
| 3. The user modifies the desired fields and adds a detailed comment justifying the alteration. |
4. The user submits the change request. |
|
5. The system validates the input, ensuring the mandatory "Change Comment" is filled. |
|
6. The system registers the change request, assigns it a unique ID, and sets its status to “Pending” or “For Review”. |
|
7. The system notifies relevant Administrators/Moderators about the new change request (via in-system notification or email). |
|
8. The system confirms the change request has been submitted successfully to the user. |
Alternative Flows
5a. Missing Change Comment
| User Action |
System Response |
|
1. If the user attempts to submit the request without filling the "Change Comment" field, the system displays an error message requiring the comment. |
| 6. The user adds the required comment and resubmits. |
7. The system re-validates and proceeds to step 6 of the Main Success Scenario. |
Special Requirements
- Editable Fields: Plot, Species, Height, and CBH are the fields allowed for change requests.
- Mandatory Comment: A "Change Comment" is required for all requests.
- Initial Status: Requests are set to "Pending" or "For Review."
- Administrator Notification: Administrators must be notified of new requests.
Related Documents