Difference between revisions of "BBB BUC Prof MngLecture"

From CDOT Wiki
Jump to: navigation, search
Line 1: Line 1:
= '''Manage Meeting''' =
+
= '''Manage Lecture''' =
  
 
'''Brief Description:'''
 
'''Brief Description:'''
  
User can manage meetings by creating, editing, and excluding them.
+
User can manage lectures by creating, editing, and excluding them.
  
  
=='''Scenario 1:''' Create new meeting.==
+
=='''Scenario 1:''' Create new lecture.==
  
 
'''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 on the empty section of a calendar date or clicks the "Create Event" button. || Returns a page with editable fields regarding lecture details. || Database is not affected.
 
|-
 
|-
| 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 "Lecture" as type of event from the drop-down list. || Event Type field is set to "Lecture". || Database is not affected.
 
|-
 
|-
 
| style="text-align: center;" | 3 || Fills in editable fields. || Filled in fields are respectively set. || Database is not affected.
 
| style="text-align: center;" | 3 || Fills in editable fields. || Filled in fields are respectively set. || Database is not affected.
Line 29: Line 29:
 
| 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" | 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" | 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" | Confirms whether or not inserted information is correct.  || bgcolor="#E0E0E0" | Returns to the page with previously filled in lecture details including updated schedule information. || 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;"  rowspan="2" bgcolor="#E0E0E0" | 7 || rowspan="2" | (1). Chooses to save lecture, or (2). chooses to cancel lecture creation process. || (1). Persists lecture and schedule details.  || (1). Lecture title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the lecture will be recorded, lecture date, lecture schedule, and attendees white-list definitions are added to the database.
 
|-
 
|-
| bgcolor="#E0E0E0" | (2). Discards inserted meeting and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
+
| bgcolor="#E0E0E0" | (2). Discards inserted lecture and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
 
|}
 
|}
  
Line 46: Line 46:
  
 
* User gets a feedback message informing successful transaction.
 
* User gets a feedback message informing successful transaction.
* A new meeting is added to user's calendar.
+
* A new lecture is added to user's calendar.
* 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.
+
* On the screen, user has the option to create another lecture, to view the created lecture being shown in the calendar, and to simply return to the calendar page.
  
  
  
=='''Scenario 2:''' Edit meeting.==
+
=='''Scenario 2:''' Edit lecture.==
  
  
Line 65: Line 65:
 
! Step# !! Actor !! System !! Data Used
 
! 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;" | 1 || Searches a lecture by using the calendar and clicks the lecture label. || Returns a page with editable fields regarding the respective lecture. || 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;" | 2 || Makes changes in editable fields. || Filled in fields are correspondingly set. || Database is not affected.
Line 73: Line 73:
 
| 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" | 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;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct.  || bgcolor="#E0E0E0" | Returns to the page with previously filled in lecture 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.
+
| style="text-align: center;" rowspan="2" | 6 || rowspan="2" | (1). Chooses to save edited lecture, or (2). chooses to cancel lecture editing process. || (1). Persists edited lecture and schedule details.  || (1). Lecture title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the lecture will be recorded, lecture date, lecture 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.
+
| bgcolor="#E0E0E0" | (2). Discards edited lecture and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
 
|}
 
|}
  
Line 89: Line 89:
  
 
* User gets a feedback message informing successful transaction.
 
* User gets a feedback message informing successful transaction.
* Meeting has its information updated.
+
* Lecture has its information updated.
* User see updated meeting in the calendar page.
+
* User see updated lecture in the calendar page.
  
  
  
=='''Scenario 3:''' Delete meeting.==
+
=='''Scenario 3:''' Delete lecture.==
  
  
Line 109: Line 109:
 
! Step# !! Actor !! System !! Data Used
 
! 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;" | 1 || Searches a lecture by using the calendar and clicks the lecture label. || Returns a page with editable fields regarding the respective lecture. || 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;" | 2 || Chooses to delete lecture by clicking the "Delete" button. || Prompts if lecture 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.
+
| style="text-align: center;" | 3 || Confirms whether or not lecture shall be deleted.  || Deletes lecture and schedule details.  || All lecture data (lecture title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the lecture will be recorded, lecture date, lecture schedule, and attendees white-list definitions) is deleted from the database.
 
|}
 
|}
  
Line 120: Line 120:
  
 
* User gets a feedback message informing successful transaction.
 
* User gets a feedback message informing successful transaction.
* Meeting is deleted.
+
* Lecture is deleted.
* User see updated calendar page (without meeting).
+
* User see updated calendar page (without the lecture).

Revision as of 15:45, 14 June 2013

Manage Lecture

Brief Description:

User can manage lectures by creating, editing, and excluding them.


Scenario 1: Create new lecture.

Preconditions:

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


Step# Actor System Data Used
1 Clicks on the empty section of a calendar date or clicks the "Create Event" button. Returns a page with editable fields regarding lecture details. Database is not affected.
2 Chooses "Lecture" as type of event from the drop-down list. Event Type field is set to "Lecture". Database is not affected.
3 Fills in editable fields. Filled in fields are respectively set. Database is not affected.
4 Optionally, chooses to create a schedule by clicking the "Edit Schedule" button. Returns a screen with editable fields regarding schedule details. Database is not affected.
5 Fills in editable fields and chooses to save schedule. Prompts if schedule information is correct. Database is not affected.
6 Confirms whether or not inserted information is correct. Returns to the page with previously filled in lecture details including updated schedule information. Database is not affected.
7 (1). Chooses to save lecture, or (2). chooses to cancel lecture creation process. (1). Persists lecture and schedule details. (1). Lecture title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the lecture will be recorded, lecture date, lecture schedule, and attendees white-list definitions are added to the database.
(2). Discards inserted lecture and schedule details. (2). Database is not affected.


Alternative event flow.


Successful Post-conditions:

  • User gets a feedback message informing successful transaction.
  • A new lecture is added to user's calendar.
  • On the screen, user has the option to create another lecture, to view the created lecture being shown in the calendar, and to simply return to the calendar page.


Scenario 2: Edit lecture.

Preconditions:

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


Step# Actor System Data Used
1 Searches a lecture by using the calendar and clicks the lecture label. Returns a page with editable fields regarding the respective lecture. Database is not affected.
2 Makes changes in editable fields. Filled in fields are correspondingly set. Database is not affected.
3 Optionally, chooses to modify the schedule by clicking the "Edit Schedule" button. Returns a screen with editable fields regarding schedule details. Database is not affected.
4 Makes changes in editable fields and chooses to save schedule. Prompts if edited schedule information is correct. Database is not affected.
5 Confirms whether or not inserted information is correct. Returns to the page with previously filled in lecture details including updated schedule information. Database is not affected.
6 (1). Chooses to save edited lecture, or (2). chooses to cancel lecture editing process. (1). Persists edited lecture and schedule details. (1). Lecture title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the lecture will be recorded, lecture date, lecture schedule, and attendees white-list definitions are updated in the database.
(2). Discards edited lecture and schedule details. (2). Database is not affected.


Alternative event flow.


Successful Post-conditions:

  • User gets a feedback message informing successful transaction.
  • Lecture has its information updated.
  • User see updated lecture in the calendar page.


Scenario 3: Delete lecture.

Preconditions:

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


Step# Actor System Data Used
1 Searches a lecture by using the calendar and clicks the lecture label. Returns a page with editable fields regarding the respective lecture. Database is not affected.
2 Chooses to delete lecture by clicking the "Delete" button. Prompts if lecture shall really be deleted. Database is not affected.
3 Confirms whether or not lecture shall be deleted. Deletes lecture and schedule details. All lecture data (lecture title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the lecture will be recorded, lecture date, lecture schedule, and attendees white-list definitions) is deleted from the database.


Successful Post-conditions:

  • User gets a feedback message informing successful transaction.
  • Lecture is deleted.
  • User see updated calendar page (without the lecture).