Changes

'''Brief Description:''' This is a template to copy and paste into other pagesThe process of managing users in the system.

=='''Scenario 1:''' Create new meetingSearch for user.==

'''Preconditions:''' Includes anything that has been set up before starting the scenario. It must include what Manage users page the user is on before the scenario starts.

| What the actors doesActor types user name into search box and chooses to search. || What the system System searches db then LDAP for user and returns user information if found. If user does not exist in responsedb and exists in LDAP, system will create records for that user. || The data fields retrievedUser name, addedfirst/last name, removedemail, by the systemdepartment, user type.|}  '''Postconditions:''' Manage users page. '''comments''' =='''Scenario 2:''' View user's meetings/lectures.==  '''Preconditions:''' Manage users page.  {| class="wikitable" border="1" cellpadding="5"

! 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 and exists in LDAP, 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:''' The final results of the scenario running (ex. A record has been created, edited, etc.). It also includes the Manage users page that the user ends on.

=='''Scenario 23:''' Edit meetingCreate user.==

'''Preconditions:''' Includes anything that has been set up before starting the scenario. It must include what Manage users page the user is on before the scenario starts.

| What the actors doesActor chooses to create a user. || What the system does in responseSystem returns page with editable fields related to user info. || The data fields retrievedUser name, first name, last name, email, addeduser type, removeddepartment info, by the systempermissions.

| Actor fills in fields and chooses to save.|| System validates fields, persists data, and writes record to db. System sends email notification to provided email address for password setup. ||

'''Postconditions:''' The final results of the scenario running (exManage users page. '''Comments'''* Do we need system data validation for user information in order to handle user name conflict? ---Gary Deng  =='''Scenario 4:''' Edit user. Actor can ban, change permissions, and assign department heads.==  '''Preconditions:''' Manage users page.  {| class="wikitable" border="1" cellpadding="5"|-! 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 and exists in LDAP, 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.  {| class="wikitable" border="1" cellpadding="5"|-! 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 and exists in LDAP, system will create records for that user. A record has been created|| User name, first/last name, email, editeddepartment, etcuser type|-| Actor chooses to delete user. || System returns prompt asking for confirmation.|| |-| Actor accepts (chooses to delete). It also includes the || System deletes user record from db.|| |}  '''Postconditions:''' Manage users page that the . '''Comments'''* There is no need to create record for user ends onwho doesn't exist in this scenario.---Gary Deng