System use case specification expiration - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
| Identification | UC12 |
| Use case | View summary of upcoming and pending expirations |
| Actors | Administrator, Technician |
| Stakeholders and interests | Consulting company: Ability to quickly view and manage upcoming and pending expirations. |
| Pre-conditions | User is logged into the system as an administrator or technician; Has at least one registered client; Has at least one registered project; Has at least one registered license or craft; Has at least one document with a close or pending expiration. |
| Minimum guarantees | System displays a summary of expirations without errors. |
| Success guarantees | User successfully views a clear and accurate summary of upcoming and pending expirations. |
Main Success Scenario
| User Action | System Response |
|---|---|
| 1. This use case begins when the user selects the option to view the summary of expirations | 2. The system retrieves and processes the relevant expiration data |
| 3. The system displays the summary of upcoming and pending expirations in a clear format | |
| 4. The user reviews the summary |
Alternative Flows
2a No upcoming or pending expirations
| User Action | System Response |
|---|---|
| 1. The system detects that there are no upcoming or pending expirations | |
| 2. The system displays a message informing the user that there are no expirations to show | |
| 3. The user acknowledges the message | 4. The system returns to the main dashboard |
3a System error during data retrieval
| User Action | System Response |
|---|---|
| 1. The system encounters an error while retrieving expiration data | |
| 2. The system displays an error message | |
| 3. The user acknowledges the error | 4. The system returns to the main dashboard |
Special Requirements
- Sorting Options: Users must be able to sort expirations by date, type, and priority.
- Filtering: Users must be able to filter expirations by status (upcoming/pending), type, and client.
- Notification Integration: The system must integrate with the notification system to highlight critical expirations.
- Color Coding: The system must use color coding to indicate the urgency of expirations (e.g., red for critical, yellow for upcoming).
- Search Capability: Users must be able to search for specific expirations by client name or document type.
- Pagination: The system must implement pagination for large sets of expiration data.