System use case specification maintain user profile - ESG-Project/documentation GitHub Wiki
← Home / Requirements / System Use Cases / System Use Cases Specification
| Identification | UC01 |
| Use case | Maintain user profile |
| Actors | Administrator, Technician |
| Stakeholders and interests | Consulting company: Ability to keep profile information up to date. |
| Pre-conditions | User is registered in the system. |
| Minimum guarantees | System prevents duplicate records. |
| Success guarantees | User can manipulate their profile information. |
Main Success Scenario
| User Action | System Response |
|---|---|
| 1. This use case begins when the user selects the option to "access my profile" | 2. The system displays the user's profile information |
| 3. The user clicks on the option to edit profile | 4. The system displays the profile information in an editable form |
| 5. The user modifies their profile information | 6. The system validates the changes |
| 7. The user selects the save option | 8. The system validates all information and updates the profile data |
| 9. The system confirms the successful update of the profile |
Alternative Flows
2a Invalid profile information
| 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 |
3a Password change
| User Action | System Response |
|---|---|
| 1. The user enters a new password | 2. The system validates the password strength |
| 3. The system requests password confirmation | |
| 4. The user confirms the new password | 5. The system updates the password |
| 6. The system confirms the password change |
3a.2a Password validation fails
| User Action | System Response |
|---|---|
| 1. The system detects that the password does not meet security requirements | |
| 2. The system displays an error message explaining the password requirements | |
| 3. The system returns to the password change form |
3b User cancels the action
| User Action | System Response |
|---|---|
| 1. The user cancels the action | 2. The system returns to the profile view without making any changes |
Special Requirements
- Profile Information: Must include name, email, contact information, and other relevant personal details.
- Duplicate Prevention: The system must check for existing users with similar information before saving.
- Data Validation: All profile information must be validated according to business rules.
- Access Control: Users can only modify their own profile information.
- Audit Trail: The system must maintain a history of all changes made to profile records.
- Password Security: The system must enforce strong password requirements.
- Email Verification: The system must verify email changes through a confirmation process.
- Two-Factor Authentication: The system must support enabling/disabling two-factor authentication.
- Profile Picture: The system must support uploading and managing profile pictures.
- Notification Preferences: The system must allow users to manage their notification settings.
- Session Management: The system must allow users to view and manage their active sessions.