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


Identification	UC02
Use case	Maintain technicians
Actors	Administrator
Stakeholders and interests	Consulting company: Ability to maintain information about the company's technicians.
Pre-conditions	User is logged into the system as an administrator.
Minimum guarantees	System prevents duplicate records.
Success guarantees	User performs any CRUD manipulation of technicians.
Business rules	BR01.

Main Success Scenario

User Action	System Response
1. This use case begins when the user selects the option to list technicians	2. The system displays the list of registered technicians
3. The user accesses the option to register a new technician	4. The system displays the technician registration form
5. The user fills in the technician's information	6. The system validates the input
7. The user selects the save option	8. The system validates all information and saves the technician data
	9. The system confirms the successful registration of the technician

User Action	System Response
	1. The system detects invalid or missing information
	2. The system displays an error message to the user
3. The user corrects the information and resubmits	4. The system validates the corrected information and returns to step 6 of the Main Success Scenario

User Action	System Response
1. The user accesses the option to edit a technician	2. The system displays the technician information in an editable form
3. The user modifies the technician's information	4. The system validates the changes
5. The user selects the save option	6. The system validates all information and updates the technician data
	7. The system confirms the successful update of the technician

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

User Action	System Response
	1. The system detects that the technician has associated records (e.g., projects, tasks)
	2. The system displays an error message explaining why the technician cannot be deleted
	3. The system returns to the technicians list

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

Technician Information: Must include name, contact information, specialization, certifications, and other relevant professional details.
Duplicate Prevention: The system must check for existing technicians with similar information before saving.
Data Validation: All technician information must be validated according to business rules.
Access Control: Only administrators can modify technician information.
Audit Trail: The system must maintain a history of all changes made to technician records.
Soft Delete: When a technician is deleted, their information should be archived rather than permanently removed.
Search Functionality: The system must provide search and filter capabilities for the technician list.
Export Option: The system must allow exporting technician information to common formats (e.g., PDF, Excel).
Certification Tracking: The system must track technician certifications and their expiration dates.
Availability Management: The system must track technician availability and workload.
Role Assignment: The system must support assigning specific roles and responsibilities to technicians.