C2UC18 Maintain User

Version 0.2

Version History

Version	Author	Modification	Date
0.1	Luiz Guilherme / Antonio	Document created and C2UC18 added	01/04
0.2	Luiz Guilherme / Antonio	Added search, update and delete alternative flows	01/04

C2UC18 - Maintain User

1. Brief Description

This use case describes the management of all the users in the system.

2. Actors

2.1 Administrator

3. Preconditions

The administrator must be logged in the system

4. Basic Flow of Events

1. This use case begins when the administrator open the Control Panel in the System.
2. The Control Panel shows list of existant users and the options to Register a new profile, Search for a existant profile, edit a existant profile or disable a existant profile.

5. Register Alternative Flow

1. The Administrator selects the Register New Clinic Profile.
2. The Control Panel shows the form to register a New Profile.
3. The Administrator inserts a profile type (clinic worker or administrator)
4. The Administrator inserts the user complete name.
5. The Administrator inserts a unique username (to sign in).
6. The Administrator inserts a 8-character alphanumeric password.
7. The Administrator inserts a 8-character alphanumeric password confirmation.
8. The Control Panel presents at the end of the form a choice to Register or Cancel the registration.
9. The Administrator selects Register to end the registration.
10. The Control Panel asks if the Administrator is certain of the registration.
11. The Administrator selects Yes.
12. The Control Panel validates the registration and returns to the screen to system list of Clinic Workers and Administrators.
13. The use case ends successfully.

6. Search Alternative flow

1. The Administrator insert a complete user name or username in the search input.
2. The Administrator press the search button.
3. The System shows the users that match the search filter.
4. The use case ends successfully.

7. Update Alternative Flow

1. The Administrator press the update button on a user filled row.
2. The Administrator goes to user details form.
3. The Administrator update a profile type (clinic worker or administrator)
4. The Administrator update the user complete name.
5. The Administrator update a unique username (to sign in).
6. The Administrator update a 8-character alphanumeric password.
7. The Administrator update a 8-character alphanumeric password confirmation.
8. The Control Panel presents at the end of the form a choice to update or cancel the update.
9. The Administrator selects Update to end the registration.
10. The Control Panel asks if the Administrator is certain of the update.
11. The Administrator selects Yes.
12. The Control Panel validates the update and returns to the screen to system list of Clinic Workers and Administrators.
13. The use case ends successfully.

8. Disable Alternative Flow

1. The Administrator press the disable button on a user filled row.
2. The Control Panel asks if the Administrator is certain of the deactivation.
3. The Administrator selects Yes.
4. The Control Panel validates the deactivation and returns to the screen to system list of Clinic Workers and Administrators.
5. The use case ends successfully.

9. Invalid Alternative Flows

9.1. Invalid User Complete Name

If in the step 4 of the Register Alternative Flow or in the Update Alternative Flow, the Administrator entered an invalid user complete name:

1. An error will appear on the screen, telling that the name is invalid.
2. Then the Administrator returns to the Step 4 of Register Alternative Flow or in the Update Alternative Flow.

9.2. Invalid username

If in the step 5 of the Register Alternative Flow or in the Update Alternative Flow, the Administrator entered an invalid username:

1. An error will appear on the screen, telling that the username is invalid.
2. Then the Administrator returns to the Step 5 of Register Alternative Flow or in the Update Alternative Flow.

9.3. Duplicated username

If in the step 5 of the Register Alternative Flow or in the Update Alternative Flow, the Administrator entered an duplicated username:

1. An error will appear on the screen, telling that the username is already registered.
2. Then the Administrator returns to the Step 5 of Register Alternative Flow or in the Update Alternative Flow.

9.4. Invalid password

If in the step 6 of the Register Alternative Flow or in the Update Alternative Flow, the Administrator entered an invalid password:

1. An error will appear on the screen, telling that the password is invalid.
2. Then the Administrator returns to the Step 6 of Register Alternative Flow or in the Update Alternative Flow.

9.5. Password not equal to confirmation password

If in the step 7 of the Register Alternative Flow or in the Update Alternative Flow, the Administrator entered a password that don't match:

1. An error will appear on the screen, telling that the password is not equal to confirmation password.
2. Then the Administrator returns to the Step 6 of Register Alternative Flow or in the Update Alternative Flow.

9.6. Incomplete form information

9.6.1. Missing User Complete Name Information

If in the step 4 of the Register Alternative Flow or in the Update Alternative Flow the Worker didn’t enter with complete name information and the step 12 of Register Alternative Flow or in the Update Alternative Flow is executed:

1. The Administrator returns to the Step 4 of the Register Alternative Flow or in the Update Alternative Flow with an error of missing complete name.

9.6.2. Missing Username information

If in the step 5 of the Register Alternative Flow or in the Update Alternative Flow the Worker didn’t enter with username information and the step 12 of Register Alternative Flow or in the Update Alternative Flow is executed:

1. The Worker returns to the step 5 of the Register Alternative Flow or in the Update Alternative Flow with any error of missing username.

9.6.3. Missing Password information

If in the step 6 the Worker of the Register Alternative Flow or in the Update Alternative Flow didn’t enter with password information and the step 12 of Register Alternative Flow or in the Update Alternative Flow is executed:

1. The Worker returns to the step 6 of the Register Alternative Flow or in the Update Alternative Flow with any error of missing password.

9.3.4. Missing Password Confirmation information

If in the step 7 the Worker of the Register Alternative Flow or in the Update Alternative Flow didn’t enter with password confirmation information and the step 12 of Register Alternative Flow or in the Update Alternative Flow is executed:

1. The Worker returns to the step 7 of the Register Alternative Flow or in the Update Alternative Flow with any error of missing password confirmation.

9.4. The Administrator canceled the registration

If in the step 11 of the Register Alternative Flow or in the Update Alternative Flow the Worker hits Cancel the registration:

1. The use case returns to the step 2 of the Register Alternative Flow or in the Update Alternative Flow and ends.

9.5. The Administrator was not sure of the registration

If in the step 11 of the Register Alternative Flow or in the Update Alternative Flow the Worker decides to not end the registration:

1. The Administrator see all the information previously entered on the screen.

9.6. The Adminitrator searchs for a non-existant user

If in the step 2 of the Search Alternative Flow, the administrator searchs for a non-existant user:

1. The table that list all the users returns a 'empty table error'.

9.7. The Adminitrator was not sure of the deactivation

If in the step 3 of the Disable Alternative Flow, the administrator decides to not end the deactivation:

1. The Administrator see all the information previously entered on the screen.

9.8. There's only a administrator in the system

If in the step 3 of the Disable Alternative Flow, there is only one administrator in the system:

1. The Deactivation is not possible and a error message is displayed.

10. Post-conditions

10.1. Successful Completion

The clinic worker or administrator was successfully registered and the system logs were successfully updated.

10.2. Failure Condition

The logs have been updated accordingly.

11. Special Requirements

[SR:C2UC18-1] - The System shall keep a log with the Administrator that performed the registration, the clinic worker or administrator that was registered, the date and time of the registration. SR: Special Requirement.