System use case specification maintain enterprise product types - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
| Identification | UC19 |
| Use case | Maintain offered product types |
| Actors | Administrator |
| Stakeholders and interests | Consulting company: Ability to create, read, update, and delete the product types offered by the company for commercial proposal preparation. |
| Pre-conditions | User is logged into the system as an administrator; System has access to relevant product type data storage. |
| Minimum guarantees | System prevents invalid product type entries. |
| Success guarantees | Administrator successfully manages product type information. |
Main Success Scenario
| User Action | System Response |
|---|---|
| 1. This use case begins when the administrator accesses the product types management section | 2. The system displays the list of current product types offered by the company |
| 3. The administrator selects to create a new product type | 4. The system displays the product type registration form |
| 5. The administrator enters the product type name | 6. The system validates the input |
| 7. The administrator saves the changes | 8. The system validates all information and saves the product type data |
| 9. The system confirms the successful registration of the product type |
Alternative Flows
3a Edit product
| User Action | System Response |
|---|---|
| 1. The administrator accesses the option to edit a product type | 2. The system displays the product type name in an editable form |
| 3. The administrator modifies the product type name | 4. The system validates the change |
| 5. The administrator saves the change | 6. The system validates all information and updates the product type data |
| 7. The system confirms the successful update of the product type |
3b Delete product
| User Action | System Response |
|---|---|
| 1. The administrator accesses the option to delete a product type | 2. The system displays a confirmation dialog |
| 3. The administrator confirms the deletion | 4. The system verifies if the product type can be deleted |
| 5. The system removes the product type data | |
| 6. The system confirms the successful deletion of the product type |
3c Administrator cancels the action
| User Action | System Response |
|---|---|
| 1. The administrator cancels the action | 2. The system returns to the product types list without making any changes |
6a Invalid product name
| User Action | System Response |
|---|---|
| 1. The system detects invalid or missing name | |
| 2. The system displays an error message | |
| 3. The administrator corrects the details and resubmits | 4. The system validates the corrected information and returns to step 6 of the Main Success Scenario |
Special Requirements
- Product type Information: Must include name.
- Duplicate Prevention: The system must check for existing product types with similar information before saving.
- Data Validation: All product type information must be validated according to business rules.
- Access Control: Only administrators can modify product type information.
- Audit Trail: The system must maintain a history of all changes made to product type records.
- Search Functionality: The system must provide search and filter capabilities for the product type list.
- Sorting Options: Users must be able to sort products by name.