Brief Description: The process of managing users in the system.
Scenario 1: Search for user.
Preconditions: Manage users page.
| Actor | System | Data Used |
|---|---|---|
| Actor types user name into search box and chooses to search. | System searches db then LDAP for user and returns user information if found. If user does not exist in db, system will create records for that user. | User name, first/last name, email, department, user type |
Postconditions: Manage users page.
comments
- This scenario's successful condition is for searching purpose, I don't think system should create record for that user.
Scenario 2: View user's meetings/lectures.
Preconditions: Manage users page.
| Actor | System | Data Used |
|---|---|---|
| Actor types user name into search box and chooses to search. | System searches db then LDAP for user and returns user information if found. If user does not exist in db, system will create records for that user. | User name, first/last name, email, department, user type |
| Actor chooses to view user's meetings/lectures. | System returns calendar view with selected user's meetings/lectures. |
Postconditions: Manage users page.
Scenario 3: Create user.
Preconditions: Manage users page.
| Actor | System | Data Used |
|---|---|---|
| Actor chooses to create a user. | System returns page with editable fields related to user info. | User name, first name, last name, email, user type, department info, permissions |
| Actor fills in fields and chooses to save. | System persists data and writes record to db. System sends email notification to provided email address for password setup. |
Postconditions: Manage users page.
Scenario 4: Edit user. Actor can ban, change permissions, and assign department heads.
Preconditions: Manage users page.
| Actor | System | Data Used |
|---|---|---|
| Actor types user name into search box and chooses to search. | System searches db then LDAP for user and returns user information if found. If user does not exist in db, system will create records for that user. | User name, first/last name, email, department, user type |
| Actor chooses to edit user. | System returns page populated with chosen user's information. | User name, first name, last name, email, user type, department info, permissions |
| Actor edits user info and chooses to save. | System persists data and updates records. |
Postconditions: Manage users page.
Scenario 5: Delete user.
Preconditions: Manage users page.
| Actor | System | Data Used |
|---|---|---|
| Actor types user name into search box and chooses to search. | System searches db then LDAP for user and returns user information if found. If user does not exist in db, system will create records for that user. | User name, first/last name, email, department, user type |
| Actor chooses to delete user. | System returns prompt asking for confirmation. | |
| Actor accepts (chooses to delete). | System deletes user record from db. |
Postconditions: Manage users page.