Difference between revisions of "BBB BUC SAdmin MngSub"

From CDOT Wiki
Jump to: navigation, search
 
Line 124: Line 124:
  
 
'''Postconditions:''' Manage subjects page.
 
'''Postconditions:''' Manage subjects page.
 
'''Comments:'''
 
This is already in manage professor page, I don't think its needed here
 

Latest revision as of 15:09, 18 June 2013

Brief Description: The process by which an actor manages subjects and their associated professors.


Scenario 1: Add subject.

Preconditions: Manage subjects page.


Actor System Data Used
Actor chooses to add a subject. System returns page with editable fields. Course Code, Course Name.
Actor fills in fields and chooses to save. System persists changes and creates new record in db.


Scenario 2: Edit subject.

Preconditions: Manage subjects page.


Actor System Data Used
Actor types subject code or name into search box and chooses to search. System searches db for subject code or name and returns subject(s) (if found). Subject code, subject name.
Actor selects subject and chooses to edit. System returns page with editable fields populated with chosen subject's details.
Actor fills in fields and chooses to save. System persists changes and creates new record in db.


Scenario 3: Delete subject.

Preconditions: Manage subjects page.


Actor System Data Used
Actor types subject code or name into search box and chooses to search. System searches db for subject code or name and returns subject(s) (if found). Subject code, subject name.
Actor selects subject and chooses to delete. System returns prompt asking for confirmation.
Actor accepts (chooses to delete). System deletes subject record from db.


Postconditions: Manage subjects page.


Scenario 4: Add Section to Subject.

Preconditions: Manage subjects page.


Actor System Data Used
Actor types subject code or name into search box and chooses to search. System searches db for subject code or name and returns subject(s) (if found). Subject code, subject name.
Actor selects subject. System returns section(s) associated with selected subject. Subject code.
Actor chooses to add a section. System returns an editable field. Section letter.
Actor fills out field with section letter and chooses to save. System persists data and adds record to db.


Postconditions: Manage subjects page.


Scenario 5: Delete Subject's Section.

Preconditions: Manage subjects page.


Actor System Data Used
Actor types subject code or name into search box and chooses to search. System searches db for subject code or name and returns subject(s) (if found). Subject code, subject name.
Actor selects subject. System returns section(s) associated with selected subject. Subject code.
Actor selects section and chooses to delete. System returns prompt asking for confirmation. Section letter.
Actor accepts (chooses to delete). System deletes section record from db.


Postconditions: Manage subjects page.


Scenario 6: Add professor to section.

Preconditions: Manage subjects page.


Actor System Data Used
Actor types subject code or name into search box and chooses to search. System searches db for subject code or name and returns subject(s) (if found). Subject code, subject name.
Actor selects subject. System returns section(s) associated with selected subject. Subject code.
Actor selects section and chooses to add professor. System returns field to search for professor. Section letter.
Actor types professor email into search field and chooses to add. System first checks local db for professor, then LDAP. If professor doesn't exist in db, system will search LDAP for professor and create a record if found. Professor email.


Postconditions: Manage subjects page.