System use case specification create new species - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
|
|
| Identification |
UC26 |
| Use case |
Create New Species (in real-time) |
| Actors |
User |
| Stakeholders and interests |
Field Technician: Needs an uninterrupted workflow for data collection, even if a species isn't pre-registered. Administrator: Requires control over the global species database for consistency. |
| Pre-conditions |
The user is adding a new specimen (UC25 is in progress) and the desired species is not found in the existing global species list. |
| Minimum guarantees |
System prevents creation of duplicate species (by scientific name). |
| Success guarantees |
The new species is successfully added to the global species database and is immediately available for selection. |
Main Success Scenario
| User Action |
System Response |
| 1. This use case begins when, during species selection (within UC25), the user opts to "Create New Species" because their desired species is not found. |
2. The system presents a small form to enter the new species details. Fields include: Scientific Name (mandatory), Family (mandatory), and Common Name (optional). |
| 3. The user fills in the required information. |
4. The system validates the uniqueness of the Scientific Name and the completeness of mandatory fields. |
| 5. The user confirms the creation of the new species. |
6. The system adds the new species to the global species register. |
|
7. The system automatically selects this new species for the current specimen being added (in UC25). |
|
8. The system confirms the new species has been created and selected successfully. |
Alternative Flows
4a. Incomplete/Duplicate Data
| User Action |
System Response |
|
1. The system detects either missing mandatory information (Scientific Name or Family) or that the Scientific Name already exists in the database. |
|
2. The system displays an error message (e.g., "Scientific Name already exists" or "Please fill in all mandatory fields"). |
| 5. The user corrects the information and resubmits. |
6. The system re-validates the corrected information and returns to step 4 of the Main Success Scenario. |
Special Requirements
- Mandatory Fields: Scientific Name and Family are mandatory; Common Name is optional.
- Uniqueness: The system must enforce uniqueness of the Scientific Name.
- Administrator Management: Administrators have a dedicated section to manage the species list (add, edit, delete, approve requests from users).
Related Documents