Difference between revisions of "PubMan Func Spec User Management"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
=UC_PM_UM_01 create account user= | ==UC_PM_UM_01 create account user== | ||
A new user should be given an account in the system, i.e. the user gets registered by a user ID. | A new user should be given an account in the system, i.e. the user gets registered by a user ID. | ||
Revision as of 09:22, 22 November 2007
UC_PM_UM_01 create account user[edit]
A new user should be given an account in the system, i.e. the user gets registered by a user ID.
Triggers[edit]
• The user wants to create a new account user.
Actors[edit]
• Local Administrator
Pre-Conditions[edit]
• None
Flow of Events[edit]
- 1. The user chooses to create an account user.
- 2. The system displays a list of all open organizational units and subunits for which the user has the privileges as “Local Administrator”.
- 3. (Optionally) The user chooses to view the organizational unit description.
- 3.1. The system displays the organizational unit description.
- 4. The user selects one organizational unit and confirms the choice.
- 5. The system assigns the account user as a member of the selected organizational unit and displays the account user edit view.
- 6. The user specifies an user-id, the e-mail and optionally a name of the account user and confirms the choice.
- 7. The system checks if an account user with the given user-id already exists.
- a. An account user with the given user-id does not exist in the system.
- b. Otherwise the system displays an error message (MSG_PM_UM_01), continue with 6.
- 5. The system creates and stores a new account user in the state inactive and sets the timestamp of creation. The user preferences are populated with the system defaults. The system creates an e-mail to the new account user with a predefined subject, text and link for the confirmation request. The e-mail of the user who has created the new account user is used as reply-to. The system displays a success message (MSG_PM_UM_02). The use case ends successfully.
Post-Conditions / Results[edit]
• A new account user in the state inactive is created and a confirmation request via e-mail is sent.
UC_PM_UM_02 log on to the system[edit]
A user needs to log on to the system to act according to his privileges as “Account User”.
Triggers[edit]
• The user wants to log on to the system.
Actors[edit]
• User
Pre-Conditions[edit]
• None
Flow of Events[edit]
- 1. The user chooses to log on to the system.
- 2. The system prompts for the user-id and a password.
- 3. The user enters his user-id, the password and confirms the input.
- 4. The system checks whether the combination of user-id and password is valid and the account user is active.
- a. The combination is valid and the account user is active.
- b. Otherwise the system displays an error message (MSG_PM_UM_03), continue with 3.
- 5. The system logs the user on. The use case ends successfully.
Post-Conditions / Results[edit]
• The account user is logged-in.
UC_PM_UM_03 log off from the system[edit]
An account user wants to log off from the system.
Triggers[edit]
• The user wants to log off from the system.
Actors[edit]
• Account User
Pre-Conditions[edit]
• The user is logged in as an account user.
Flow of Events[edit]
- 1. The user chooses to log off from the system.
- 2. The system logs the user off. The use case ends successfully.
Post-Conditions / Results[edit]
• The account user is logged off from the system.