Open main menu

CDOT Wiki β

Difference between revisions of "BBB BUC SAdmin MngUser"

(Scenario 1: Search for user.)
 
(7 intermediate revisions by 3 users not shown)
Line 2: Line 2:
  
  
'''Scenario 1:''' Search for user.
+
=='''Scenario 1:''' Search for user.==
  
  
Line 12: Line 12:
 
! Actor !! System !! Data Used
 
! 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 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.
 
|}
 
|}
  
Line 18: Line 18:
 
'''Postconditions:''' Manage users page.
 
'''Postconditions:''' Manage users page.
  
 +
'''comments'''
  
'''Scenario 2:''' View user's meetings/lectures.
+
=='''Scenario 2:''' View user's meetings/lectures.==
  
  
Line 29: Line 30:
 
! Actor !! System !! Data Used
 
! 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 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.||
 
| Actor chooses to view user's meetings/lectures. || System returns calendar view with selected user's meetings/lectures.||
Line 38: Line 39:
  
  
'''Scenario 3:''' Create user.
+
=='''Scenario 3:''' Create user.==
  
  
Line 48: Line 49:
 
! Actor !! System !! Data Used
 
! 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 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. ||
+
| 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. ||
 
|}
 
|}
  
Line 56: Line 57:
 
'''Postconditions:''' Manage users page.
 
'''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.  
+
 
 +
=='''Scenario 4:''' Edit user. Actor can ban, change permissions, and assign department heads.==
  
  
Line 67: Line 71:
 
! Actor !! System !! Data Used
 
! 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 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 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
Line 78: Line 82:
  
  
'''Scenario 5:''' Delete user.
+
=='''Scenario 5:''' Delete user.==
  
  
Line 88: Line 92:
 
! Actor !! System !! Data Used
 
! 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 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 chooses to delete user. || System returns prompt asking for confirmation.||  
Line 97: Line 101:
  
 
'''Postconditions:''' Manage users page.
 
'''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