Difference between revisions of "BBB BUC SAdmin MngProf"

From CDOT Wiki
Jump to: navigation, search
Line 2: Line 2:
  
  
'''Scenario 1:''' Add subject to professor
+
=='''Scenario 1:''' Add subject to professor.==
  
  
Line 24: Line 24:
  
  
'''Scenario 2:''' Edit professor's subject
+
=='''Scenario 2:''' Edit professor's subject.==
  
  
Line 46: Line 46:
  
  
'''Scenario 3:''' Delete professor's subject
+
=='''Scenario 3:''' Delete professor's subject.==
  
  
Line 67: Line 67:
  
  
'''Scenario 4:''' Add section to professor's subject
+
=='''Scenario 4:''' Add section to professor's subject.==
  
  
Line 86: Line 86:
  
  
'''Scenario 5:''' Delete professor's
+
=='''Scenario 5:''' Delete professor's.==
  
  
Line 105: Line 105:
  
  
'''Scenario 6:''' Upload subject list
+
=='''Scenario 6:''' Upload subject list.==
  
  

Revision as of 14:40, 18 June 2013

Brief Description: The process by which an actor manages a professors subjects and sections.


Scenario 1: Add subject to professor.

Preconditions: Manage professors page.


Actor System Data Used
Actor types professor username into search box and chooses to search. System searches db for username and returns professor's subjects (if found). Otherwise, searches LDAP for username and creates null records in db for professor (if found). Professor username
Actor chooses to add a subject. System returns page with editable fields. Course Code, Course Name
Actor chooses to save changes. System validates fields and persists changes to db.


Postconditions: Manage professors page.


Scenario 2: Edit professor's subject.

Preconditions: Manage professors page.


Actor System Data Used
Actor types professor username into search box and chooses to search. System searches db and LDAP for username and returns professor's subjects (if found). Professor username
Actor chooses to edit a subject. System returns page with editable fields populated with chosen subject's details. Course Code, Course Name
Actor edits fields and chooses to save changes. System validates fields and persists changes to db.


Postconditions: Manage professors page.


Scenario 3: Delete professor's subject.

Preconditions: Manage professors page.


Actor System Data Used
Actor types professor username into search box and chooses to search. System searches db and LDAP for username and returns professor's subjects (if found). Professor username
Actor chooses to delete a subject. System returns prompt asking for confirmation.
Actor accepts (chooses to delete). System deletes subject record from db.


Postconditions: Manage professors page.


Scenario 4: Add section to professor's subject.

Preconditions: Actor is editing a professor's subject. Edit subject page.


Actor System Data Used
Actor chooses to add a section to the subject. System returns a field for entering section letter. Section letter
Actor chooses to save section. System validates field, persists data to db, and returns visual notification indicating that a new section has been added. Section letter


Postconditions: Manage professors page.


Scenario 5: Delete professor's.

Preconditions: Actor is editing a professor's subject. Edit subject page.


Actor System Data Used
Actor chooses to delete a section. System returns prompt asking for confirmation.
Actor accepts (chooses to delete). System delete section record from db.


Postconditions: Manage professors page.


Scenario 6: Upload subject list.

Preconditions: Manage professors page.


Actor System Data Used
Actor chooses to upload list of subjects. System returns prompt for uploading list.
Actor chooses file and accepts. System parses file and updates db with subjects information.


Postconditions: Manage professors page.