System use case specification maintain enterprise products - ESG-Project/documentation GitHub Wiki


Identification	UC14
Use case	Maintain offered products
Actors	Administrator
Stakeholders and interests	Consulting company: Ability to create, read, update, and delete the products 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 data storage.
Minimum guarantees	System prevents invalid product entries.
Success guarantees	Administrator successfully manages product information.

Main Success Scenario

User Action	System Response
1. This use case begins when the administrator accesses the products management section	2. The system displays the list of current products offered by the company
3. The administrator selects to create a new product	4. The system displays the product registration form
5. The administrator enters the product details (name, type, value, deliverable)	6. The system validates the input
7. The administrator saves the changes	8. The system validates all information and saves the product data
	9. The system confirms the successful registration of the product

User Action	System Response
1. The administrator accesses the option to edit a product	2. The system displays the product information in an editable form
3. The administrator modifies the product details	4. The system validates the changes
5. The administrator saves the changes	6. The system validates all information and updates the product data
	7. The system confirms the successful update of the product

User Action	System Response
1. The administrator accesses the option to delete a product	2. The system displays a confirmation dialog
3. The administrator confirms the deletion	4. The system verifies if the product can be deleted
	5. The system removes the product data
	6. The system confirms the successful deletion of the product

User Action	System Response
1. The administrator cancels the action	2. The system returns to the products list without making any changes

User Action	System Response
	1. The system detects invalid or missing information
	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

Product Information: Must include name, type, value, and deliverable details.
Duplicate Prevention: The system must check for existing products with similar information before saving.
Data Validation: All product information must be validated according to business rules.
Access Control: Only administrators can modify product information.
Audit Trail: The system must maintain a history of all changes made to product records.
Search Functionality: The system must provide search and filter capabilities for the product list.
Sorting Options: Users must be able to sort products by name, type, and value.