System use case specification view phytosociological analyses - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
|
|
Identification |
UC20 |
Use case |
View Phytosociological Analyses of a Project |
Actors |
User |
Stakeholders and interests |
Forest Inventory Analyst: Needs to quickly see all analyses under a project to manage their work. Project Manager: Requires an overview of ongoing and completed analyses within their projects. |
Pre-conditions |
User is logged into the system. At least one project is pre-registered in the system. |
Minimum guarantees |
System displays an empty list or a "No analyses found" message if no data exists or matches filters. |
Success guarantees |
A list of Phytosociological Analyses for the selected project is displayed, paginated and sortable. |
Main Success Scenario
User Action |
System Response |
1. This use case begins when the user accesses the projects page. |
2. The system displays a list of projects. |
3. The user selects a project. |
4. The system displays the selected project's details. |
5. The user accesses the "Phytosociological Analyses" tab of the selected project. |
6. The system queries the database and retrieves the list of Phytosociological Analyses associated with that project. |
|
7. The system displays the list of Phytosociological Analyses in a table format, including columns for Title, Description, Status, Sampled Area, and Collection Start Date. |
Special Requirements
- Project Filtering: The list of analyses is always filtered by the currently selected project.
- Displayed Columns: List must include Title, Description, Status, Sampled Area, and Collection Start Date.
- Sorting and Pagination: Results must be sortable by columns and paginated.
Related Documents