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


Identification	UC19
Use case	Create New Phytosociological Analysis from an Existing Project
Actors	User, Administrator
Stakeholders and interests	Forest Inventory Analyst: Needs to initiate new forest inventories and organize them under specific projects. Project Manager: Requires a clear overview of all analyses linked to their projects.
Pre-conditions	User is logged into the system and has permission to create Phytosociological Analyses. At least one Project is registered in the system to which the analysis will be linked.
Minimum guarantees	System prevents creation of analyses without a valid project or with invalid mandatory data.
Success guarantees	A new Phytosociological Analysis is registered in the system with the status "Pending" or "In Collection" and linked to the selected Project.

Main Success Scenario

User Action	System Response
1. This use case begins when the user selects an existing project.	2. The system displays the project's details, including a section for phytosociological analyses.
3. The user navigates to the phytosociological analyses tab.	4. The system displays a list (possibly empty) of existing analyses for that project, along with an option to create a new one.
5. The user clicks the "New Analysis" button.	6. The system displays a form for basic Phytosociological Analysis information. Fields include: Title, Location, Description (optional), Collection Start Date, Number of Plots, Plot Area (ha), Total Area (m²), Sampled Area (ha).
7. The user fills in the mandatory and optional information.	8. The system automatically calculates "Sampled Area" based on "Number of Plots" × "Plot Area" but allows manual override with justification.
9. The user confirms the creation of the analysis.	10. The system validates the entered data.
	11. The system registers the new Phytosociological Analysis with an initial status of “Pending” or “In Collection”, associating it with the selected Project.
	12. The system confirms the analysis has been created successfully.

User Action	System Response
	1. If the user attempts to proceed without a valid project selected (e.g., direct URL access or error in prior navigation), the system displays an error message.
	2. The system redirects the user to the project selection or creation page.

User Action	System Response
	1. The system detects invalid or missing information in mandatory fields (Title, Location, Collection Start Date, Plot Data).
	2. The system displays specific error messages next to the problematic fields, requesting correction.
10. The user corrects the information and resubmits.	11. The system re-validates the corrected information and proceeds to step 10 of the Main Success Scenario.

User Action	System Response
1. The user cancels the action (e.g., clicks "Cancel" button).	2. The system discards all entered information and returns to the previous screen (e.g., the analyses list for the project) without saving.

Project Association: Every analysis must be associated with an existing project.
Mandatory Fields: Title, Location, Collection Start Date, Number of Plots, Plot Area, Total Area, and Sampled Area are mandatory.
Automatic Calculation with Override: Sampled Area must be auto-calculated but editable with justification.
Location Coordinates: The Location field can optionally include geographical coordinates.
Initial Status: New analyses start with "Pending" or "In Collection" status.
Field Validation: All fields must be validated with clear messages.
Cancel Operation: Users can cancel the creation at any time.