System use case specification edit phytosociological analysis information - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
|
|
| Identification |
UC22 |
| Use case |
Edit Phytosociological Analysis Information |
| Actors |
User |
| Stakeholders and interests |
Forest Inventory Analyst: Needs to correct errors or update analysis details as field work or data processing evolves. Project Manager: Requires updated and accurate information about project analyses. |
| Pre-conditions |
The Phytosociological Analysis to be edited exists. The user has permission to edit it. |
| Minimum guarantees |
System prevents saving invalid data. |
| Success guarantees |
The information of the Phytosociological Analysis is successfully updated in the system. |
Main Success Scenario
| User Action |
System Response |
| 1. This use case begins when the user selects a Phytosociological Analysis from the list for editing. |
2. The system displays a form pre-filled with the current information of the Analysis. |
| 3. The user modifies the desired fields. Editable fields include: Title, Description, Location, Collection Date, Number of Plots, Plot Area (ha), Total Area (m²), Sampled Area (ha), and List of Observations. |
4. The system automatically recalculates "Sampled Area" if relevant fields change, allowing manual override with justification. |
| 5. The user confirms the alterations. |
6. The system validates the modified data, reapplying the same validations as during creation (RN001). |
|
7. The system saves the updates to the Phytosociological Analysis in the database. |
|
8. The system confirms the successful update of the analysis information. |
Alternative Flows
5a. Incomplete/Invalid Information
| User Action |
System Response |
|
1. The system detects invalid or missing information in mandatory fields after user modification. |
|
2. The system displays specific error messages next to the problematic fields, requesting correction. |
| 6. The user corrects the information and resubmits. |
7. The system re-validates the corrected information and proceeds to step 6 of the Main Success Scenario. |
5b. User Cancels Editing
| User Action |
System Response |
| 1. The user cancels the action (e.g., clicks "Cancel" button). |
2. The system discards all unsaved changes and returns to the previous screen (e.g., the analysis details or list) without updating the analysis. |
Special Requirements
- Editable Fields: Specific fields are editable: Title, Description, Location, Collection Date, Number of Plots, Plot Area, Total Area, Sampled Area, and List of Observations.
- Reapply Validations: All validations from creation (BR03) must be reapplied during editing.
- Explicit Confirmation: Changes require explicit user confirmation.
- Cancellation: Users can cancel the editing process at any time.
Related Documents