Difference between revisions of "BBB BUC Prof MngCSetting"

From CDOT Wiki
Jump to: navigation, search
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= '''Manage Meetings''' =
+
= '''Manage Class Settings''' =
  
 
'''Brief Description:'''
 
'''Brief Description:'''
  
User can manage meetings by creating, editing, and excluding them.
+
User can manage class settings by defining preferred properties.
  
  
=='''Scenario 1:''' Create new meeting.==
+
=='''Scenario 1:''' Edit class settings.==
  
 
'''Preconditions:'''
 
'''Preconditions:'''
Line 19: Line 19:
 
! Step# !! Actor !! System !! Data Used
 
! Step# !! Actor !! System !! Data Used
 
|-
 
|-
| style="text-align: center;" | 1 || Clicks on the empty section of a calendar date or clicks the "Create Event" button. || Returns a page with editable fields regarding meeting details. || Database is not affected.
+
| style="text-align: center;" | 1 || Clicks the "Class Settings" button. || Redirects to the "Class Settings" page. || All fields in the 'course' table are used.
 
|-
 
|-
| style="text-align: center;" | 2 || Chooses "Meeting" as type of event from the drop-down list. || Event Type field is set to "Meeting". || Database is not affected.
+
| style="text-align: center;" | 2 || Chooses a class from the drop-down list labeled "Filter by class". || Sets the "Filter by class" field to the respectively chosen class. || All fields in the 'course' and 'section' tables are used.
 
|-
 
|-
| style="text-align: center;" | 3 || Fills in editable fields. || Filled in fields are respectively set. || Database is not affected.
+
| style="text-align: center;" | 3 || Chooses a section from the drop-down list labeled "Section". || Sets the "Section" field to the chosen section, and returns a respective list of changeable settings and a list of students registered in the class. || All fields in the 'student', 'course', and 'section' tables are used.
 
|-
 
|-
| style="text-align: center;" bgcolor="#E0E0E0" | 4 || bgcolor="#E0E0E0" |Optionally, chooses to create a schedule by clicking the "Edit Schedule" button. || bgcolor="#E0E0E0 " | Returns a screen with editable fields regarding schedule details. || bgcolor="#E0E0E0" | Database is not affected.
+
| style="text-align: center;" | 4 || Modifies default or previously edited settings (Allow private chat, Allow multiple user whiteboard, Allow recording, Allow to share camera).|| Modifications are respectively set. || Database is not affected.
 
|-
 
|-
| style="text-align: center;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Fills in editable fields and chooses to save schedule. || bgcolor="#E0E0E0" | Prompts if schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.
+
| style="text-align: center;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Optionally, chooses to edit student information by clicking the "Edit" button in a listed record. || bgcolor="#E0E0E0 " | Returns a screen with editable fields regarding student details. || bgcolor="#E0E0E0" | All fields in the 'student' table are used.
 
|-
 
|-
| style="text-align: center;" bgcolor="#E0E0E0" | 6 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct. || bgcolor="#E0E0E0" | Returns to the page with previously filled in meeting details including updated schedule information. || bgcolor="#E0E0E0" | Database is not affected.
+
| style="text-align: center;" bgcolor="#E0E0E0" | 6 || bgcolor="#E0E0E0" | Fills in editable fields and chooses to save student information. || bgcolor="#E0E0E0" | Validates fields and prompts if student information is correct. || bgcolor="#E0E0E0" | Database is not affected.
 
|-
 
|-
| style="text-align: center;" rowspan="2" bgcolor="#E0E0E0" | 7 || rowspan="2" | (1). Chooses to save meeting, or (2). chooses to cancel meeting creation process. || (1). Persists meeting and schedule details.  || (1). Meeting title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the meeting will be recorded, meeting date, meeting schedule, and attendees white-list definitions are added to the database.
+
| style="text-align: center;" bgcolor="#E0E0E0" | 7 || bgcolor="#E0E0E0" | Confirms whether or not the student updated information is correct.  || bgcolor="#E0E0E0" | Returns to the page that has the previously selected class and its respective section, and includes student updated information on the screen. || bgcolor="#E0E0E0" | Student updated information is saved in the database. All fields in the 'student' table are used.
 
|-
 
|-
| bgcolor="#E0E0E0" | (2). Discards inserted meeting and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
+
| style="text-align: center;"  rowspan="2" bgcolor="#E0E0E0" | 8 || rowspan="2" | (1). Chooses to save class settings, or (2). chooses to cancel class settings editing process. || (1). Persists class settings details.  || (1).  "Allow private chat", "Allow multiple user whiteboard", "Allow recording", and "Allow to share camera" definitions are updated in the database. All fields in the 'course' and 'section' tables are used.
 +
|-
 +
| bgcolor="#E0E0E0" | (2). Discards updated class settings details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
 
|}
 
|}
  
Line 45: Line 47:
 
'''Successful Post-conditions:'''
 
'''Successful Post-conditions:'''
  
* User gets a feedback message informing successful transaction.
+
* User gets a feedback message informing that transaction was successful.
* A new meeting is added to user's calendar.
+
* Updated class settings are now effective.
* On the screen, user has the option to create another meeting, to view the created meeting being shown in the calendar, and to simply return to the calendar page.
+
* User returns to the home page.
 
 
 
 
 
 
=='''Scenario 2:''' Edit meeting.==
 
 
 
 
 
'''Preconditions:'''
 
 
 
* User is authenticated.
 
 
 
* User is accessing the home page.
 
 
 
 
 
{| class="wikitable" border="1" cellpadding="5"
 
|-
 
! Step# !! Actor !! System !! Data Used
 
|-
 
| style="text-align: center;" | 1 || Searches a meeting by using the calendar and clicks the meeting label. || Returns a page with editable fields regarding the respective meeting. || Database is not affected.
 
|-
 
| style="text-align: center;" | 2 || Makes changes in editable fields. || Filled in fields are correspondingly set. || Database is not affected.
 
|-
 
| style="text-align: center;" bgcolor="#E0E0E0" | 3 || bgcolor="#E0E0E0" |Optionally, chooses to modify the schedule by clicking the "Edit Schedule" button. || bgcolor="#E0E0E0 " | Returns a screen with editable fields regarding schedule details. || bgcolor="#E0E0E0" | Database is not affected.
 
|-
 
| style="text-align: center;" bgcolor="#E0E0E0" | 4 || bgcolor="#E0E0E0" | Makes changes in editable fields and chooses to save schedule. || bgcolor="#E0E0E0" | Prompts if edited schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.
 
|-
 
| style="text-align: center;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct.  || bgcolor="#E0E0E0" | Returns to the page with previously filled in meeting details including updated schedule information. || bgcolor="#E0E0E0" | Database is not affected.
 
|-
 
| style="text-align: center;" rowspan="2" | 6 || rowspan="2" | (1). Chooses to save edited meeting, or (2). chooses to cancel meeting editing process. || (1). Persists edited meeting and schedule details.  || (1). Meeting title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the meeting will be recorded, meeting date, meeting schedule, and attendees white-list definitions are updated in the database.
 
|-
 
| bgcolor="#E0E0E0" | (2). Discards edited meeting and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
 
|}
 
 
 
 
 
{| border="1" cellpadding="5"
 
| bgcolor="#E0E0E0" width="21" style="border: 1px solid" |  || <sub>Alternative event flow.</sub>
 
|}
 
 
 
 
 
'''Successful Post-conditions:'''
 
 
 
* User gets a feedback message informing successful transaction.
 
* Meeting has its information updated.
 
* User see updated meeting in the calendar page.
 
 
 
 
 
 
 
=='''Scenario 3:''' Delete meeting.==
 
 
 
 
 
'''Preconditions:'''
 
 
 
* User is authenticated.
 
 
 
* User is accessing the home page.
 
 
 
 
 
 
 
{| class="wikitable" border="1" cellpadding="5"
 
|-
 
! Step# !! Actor !! System !! Data Used
 
|-
 
| style="text-align: center;" | 1 || Searches a meeting by using the calendar and clicks the meeting label. || Returns a page with editable fields regarding the respective meeting. || Database is not affected.
 
|-
 
| style="text-align: center;" | 2 || Chooses to delete meeting by clicking the "Delete" button. || Prompts if meeting shall really be deleted. || Database is not affected.
 
|-
 
| style="text-align: center;" | 3 || Confirms whether or not meeting shall be deleted.  || Deletes meeting and schedule details.  || All meeting data (meeting title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the meeting will be recorded, meeting date, meeting schedule, and attendees white-list definitions) is deleted from the database.
 
|}
 
 
 
 
 
'''Successful Post-conditions:'''
 
 
 
* User gets a feedback message informing successful transaction.
 
* Meeting is deleted.
 
* User see updated calendar page (without meeting).
 

Latest revision as of 14:32, 18 June 2013

Manage Class Settings

Brief Description:

User can manage class settings by defining preferred properties.


Scenario 1: Edit class settings.

Preconditions:

  • User is authenticated.
  • User is accessing the home page.


Step# Actor System Data Used
1 Clicks the "Class Settings" button. Redirects to the "Class Settings" page. All fields in the 'course' table are used.
2 Chooses a class from the drop-down list labeled "Filter by class". Sets the "Filter by class" field to the respectively chosen class. All fields in the 'course' and 'section' tables are used.
3 Chooses a section from the drop-down list labeled "Section". Sets the "Section" field to the chosen section, and returns a respective list of changeable settings and a list of students registered in the class. All fields in the 'student', 'course', and 'section' tables are used.
4 Modifies default or previously edited settings (Allow private chat, Allow multiple user whiteboard, Allow recording, Allow to share camera). Modifications are respectively set. Database is not affected.
5 Optionally, chooses to edit student information by clicking the "Edit" button in a listed record. Returns a screen with editable fields regarding student details. All fields in the 'student' table are used.
6 Fills in editable fields and chooses to save student information. Validates fields and prompts if student information is correct. Database is not affected.
7 Confirms whether or not the student updated information is correct. Returns to the page that has the previously selected class and its respective section, and includes student updated information on the screen. Student updated information is saved in the database. All fields in the 'student' table are used.
8 (1). Chooses to save class settings, or (2). chooses to cancel class settings editing process. (1). Persists class settings details. (1). "Allow private chat", "Allow multiple user whiteboard", "Allow recording", and "Allow to share camera" definitions are updated in the database. All fields in the 'course' and 'section' tables are used.
(2). Discards updated class settings details. (2). Database is not affected.


Alternative event flow.


Successful Post-conditions:

  • User gets a feedback message informing that transaction was successful.
  • Updated class settings are now effective.
  • User returns to the home page.