UC2::Change Personal Details
Overview
This use-case describes the process whereby a user updates their personal details stored on the system.
Document History
- Current Version:1.2
-
1.1:
odlingsmee
2006-01-01
Initial Revision
-
1.2:
odlingsmee
2006-05-23
Upgraded to version 0.2
Properties
- Trigger:The user's personal information has changed or the user notices that the information held by the system is inaccurate.
- Goal:To allow the user to update their information on the system
- Primary Actor:User
- Pre-Requisites:The user will be Logged On [UC1].
- Success Outcome:The user's details will have been updated on the system.
- Failure Outcome:The user will have been informed of the validation or techinical issues that prevented the update from being successful
- Priority:1
- Complexity:1
- Package:admin
Basic Flow
- The user navigates to personal information screen.
- The system presents the user's personal information to them.
- The user notices that the information is incorrect and selects the "edit" option.
- The presents the user with an editable view of their personal information [RQ8]. The editable fields include: first name [RQ9]; last name [RQ10]and address [RQ11].
- The user edits their details as appropriate
- The user submits the updated details to the system.
- The system validates that the details provide were allowable [RQ12].
- The system saves the new details and presents the updated information back to the user in a read-only view.
- The use-case ends
Alternative Flows
Validation Errors
At step 6 of the Main Flow when the system finds that the new data entered fails validation
- The system presents the user with the details of the one or more validation errors that were encountered.
- The flow of events continues from step 5 of the Main Flow.
Exception Flows
Record Update Error
At step 8 of the Main Flow when there is an error updating the datastore
- The system cannot update the user's record because of an technical issue
- The system informs the user of the issue
- The use-case ends
Specific Requirements
- [RQ8] Personal Information:The system shall store certain personal information about each user on the system. (proposed)
- [RQ9] First Name:The system shall store a first name against each user. (proposed)
- [RQ10] Last Name:The system shall store a last name against each user. (proposed)
- [RQ11] Address:The system shall store an address against each user. (proposed)
- [RQ12] Names fields:Name fields should be at least one character in length. (proposed)