System use case specification delete phytosociological analysis - ESG-Project/documentation GitHub Wiki


Identification	UC23
Use case	Delete Phytosociological Analysis
Actors	User
Stakeholders and interests	Forest Inventory Analyst: Needs to remove incorrect, duplicate, or obsolete analyses from the system.
Pre-conditions	The Phytosociological Analysis to be deleted exists. The user has permission to delete it.
Minimum guarantees	System prevents deletion of analyses with critical dependencies.
Success guarantees	The Phytosociological Analysis and all its associated data (specimens, calculation results) are permanently removed from 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 deletion.	2. The system displays a confirmation dialog, alerting the user about the irreversibility of the action and the deletion of all related data (specimens, results, etc.).
3. The user explicitly confirms the deletion.	4. The system performs checks to ensure the analysis can be deleted (e.g., not "Finalized" or "Approved" status, no linked compensation data).
	5. The system removes the Phytosociological Analysis and all its associated records from the database.
	6. The system confirms the successful deletion of the analysis.

User Action	System Response
1. The user cancels the deletion action (e.g., clicks "Cancel" button in the dialog).	2. The system closes the confirmation dialog and returns to the analyses list, keeping the analysis intact.

User Action	System Response
	1. The system detects that the Phytosociological Analysis has dependencies that prevent deletion (e.g., status "Finalized" or "Approved", or linked compensation data).
	2. The system displays an informative error message explaining the reason for non-deletion (e.g., "Cannot delete analysis. It is either finalized, approved, or has linked compensation data.") and suggests alternative actions (e.g., "Consider archiving the analysis instead.").
	3. The system returns to the analyses list without deleting the analysis.

Irreversibility: Deletion is permanent and requires explicit user confirmation.
Deletion Constraints: An analysis cannot be deleted if its status is "Finalized" or "Approved," or if it has linked compensation data.
Reason for Non-deletion: If deletion is not permitted, the system must explain the reason and suggest alternatives.
Cascade Deletion: All associated data (specimens, calculation results) must be deleted along with the analysis.