System use case specification search phytosociological analysis - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
|
|
Identification |
UC21 |
Use case |
Search Specific Phytosociological Analysis |
Actors |
User |
Stakeholders and interests |
Forest Inventory Analyst: Needs to quickly find a specific analysis without manually Browse long lists. |
Pre-conditions |
The user is viewing the list of Phytosociological Analyses (UC20 has been executed). |
Minimum guarantees |
System responds promptly to search queries. |
Success guarantees |
The list of Phytosociological Analyses is filtered, displaying only analyses that match the search criteria. |
Main Success Scenario
User Action |
System Response |
1. This use case begins when the user types a search term (e.g., title, description, location, or date) in the search bar. |
2. The system filters the displayed list of Phytosociological Analyses in real-time (or after pressing Enter) based on the search term. |
|
3. The system displays only the analyses that contain the search term in their relevant fields (Title, Description, Analysis Location, or Collection Date). |
Alternative Flows
3a. No Results Found
User Action |
System Response |
|
1. If no analyses match the search term after filtering, the system displays the message: "No analysis found for your search." |
Special Requirements
- Searchable Fields: Searchable fields include Title, Description, Analysis Location, and Collection Date.
- Real-time or Confirmed Search: Filtering can occur as the user types (real-time) or after confirmation (Enter).
- No Results Message: A specific message must be displayed if no results are found.
Related Documents