Difference between revisions of "BBB BUC SAdmin MngUser"

From CDOT Wiki
Jump to: navigation, search
(Created page with ''''Brief Description:''' This is a template to copy and paste into other pages. '''Scenario 1:''' Create new meeting '''Preconditions:''' Includes anything that has been set …')
 
(→‎Scenario 1: Search for user.)
 
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
'''Brief Description:''' This is a template to copy and paste into other pages.
+
'''Brief Description:''' The process of managing users in the system.
  
  
−
'''Scenario 1:''' Create new meeting
+
=='''Scenario 1:''' Search for user.==
  
  
−
'''Preconditions:''' Includes anything that has been set up before starting the scenario. It must include what page the user is on before the scenario starts.
+
'''Preconditions:''' Manage users page.
  
  
Line 12: Line 12:
 
! Actor !! System !! Data Used
 
! Actor !! System !! Data Used
 
|-
 
|-
−
| What the actors does. || What the system does in response. || The data fields retrieved, added, removed, by the system.
+
| 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.
 +
|}
 +
 
 +
 
 +
'''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 page that the user ends on.
+
'''Postconditions:''' Manage users page.
  
  
−
'''Scenario 2:''' Edit meeting
+
=='''Scenario 3:''' Create user.==
  
  
−
'''Preconditions:''' Includes anything that has been set up before starting the scenario. It must include what page the user is on before the scenario starts.
+
'''Preconditions:''' Manage users page.
  
  
Line 31: Line 49:
 
! Actor !! System !! Data Used
 
! Actor !! System !! Data Used
 
|-
 
|-
−
| What the actors does. || What the system does in response. || The data fields retrieved, added, removed, by the system.
+
| 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 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 (ex. A record has been created, edited, etc.). It also includes the page that the user ends on.
+
'''Postconditions:''' Manage 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.|| 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.
 +
 
 +
'''Comments'''
 +
* There is no need to create record for user who doesn't exist in this scenario.---Gary Deng

Latest revision as of 14:13, 28 June 2013

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 and exists in LDAP, system will create records for that user. User name, first/last name, email, department, user type.


Postconditions: Manage users page.

comments

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 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: 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 validates fields, persists data, and writes record to db. System sends email notification to provided email address for password setup.


Postconditions: Manage 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.


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.


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 delete user. System returns prompt asking for confirmation.
Actor accepts (chooses to delete). System deletes user record from db.


Postconditions: Manage users page.

Comments

  • There is no need to create record for user who doesn't exist in this scenario.---Gary Deng
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=BBB_BUC_SAdmin_MngUser&oldid=97069"