Difference between revisions of "BBB BUC Emp MngMeeting"

From CDOT Wiki
Jump to: navigation, search
 
(39 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= '''Manage Meeting''' =
+
= '''Manage Meetings''' =
  
 
'''Brief Description:'''
 
'''Brief Description:'''
Line 17: Line 17:
 
{| class="wikitable" border="1" cellpadding="5"
 
{| class="wikitable" border="1" cellpadding="5"
 
|-
 
|-
! Actor !! System !! Data Used
+
! Step# !! Actor !! System !! Data Used
 
|-
 
|-
| 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 Meeting" button. || Returns a page with editable fields regarding meeting details. || Database is not affected.
 
|-
 
|-
| 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 || Fills in editable fields. || Performs data validation on editable fields. || Database is not affected.
 
|-
 
|-
| Fills in editable fields. || Filled in fields are respectively set. || Database is not affected.
+
| style="text-align: center;" bgcolor="#E0E0E0" | 3 || 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.
 
|-
 
|-
| 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;" bgcolor="#E0E0E0" | 4 || bgcolor="#E0E0E0" | Fills in editable fields and chooses to save schedule. || bgcolor="#E0E0E0" | Validates fields and prompts if schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.
 
|-
 
|-
| 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" | 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.
 
|-
 
|-
| 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" bgcolor="#E0E0E0" | 6 || rowspan="2" | (1). Chooses to save meeting, or (2). chooses to cancel meeting creation process. || (1). Persists meeting and schedule details.  || (1). Meeting title, presenter-only camera, public whiteboard, meeting recorded, meeting date, meeting schedule, and attendees whitelist definitions are added to the database. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
|-
 
| 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.
 
 
|-
 
|-
 
| bgcolor="#E0E0E0" | (2). Discards inserted meeting and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
 
| bgcolor="#E0E0E0" | (2). Discards inserted meeting and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
Line 37: Line 35:
  
  
'''Post-conditions:'''
 
  
* User gets a feedback message informing if transaction was successful.
+
{| 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 that transaction was successful.
 
* A new meeting is added to user's calendar.
 
* A new meeting 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 meeting, to view the created meeting being shown in the calendar, and to simply return to the calendar page.
 +
 +
''' Comments:'''
 +
* Do we need system data validation on step 4?
 +
* It's difficult for me to understand the data used on step 6.-----Gary Deng
  
  
Line 57: Line 65:
 
{| class="wikitable" border="1" cellpadding="5"
 
{| class="wikitable" border="1" cellpadding="5"
 
|-
 
|-
! Actor !! System !! Data Used
+
! Step# !! Actor !! System !! Data Used
 
|-
 
|-
| 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 meeting by using the calendar and clicks the meeting label. || Returns a page with editable fields regarding the respective meeting. || All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
 
|-
 
|-
| 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. || System performs data validation. || Database is not affected.
 
|-
 
|-
| 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" | 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.
 
|-
 
|-
| 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" | Validates fields and prompts if edited schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.
 
|-
 
|-
| 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 meeting details including updated schedule information. || bgcolor="#E0E0E0" | All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
 
|-
 
|-
| 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 meeting, or (2). chooses to cancel meeting editing process. || (1). Persists edited meeting and schedule details.  ||(1). Meeting title, presenter-only camera, public whiteboard, meeting recorded, meeting date, meeting schedule, and attendees whitelist definitions are added to the database. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
 
|-
 
|-
 
| bgcolor="#E0E0E0" | (2). Discards edited meeting and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
 
| bgcolor="#E0E0E0" | (2). Discards edited meeting and schedule details.  || bgcolor="#E0E0E0" | (2). Database is not affected.
Line 75: Line 83:
  
  
'''Post-conditions:'''
+
{| border="1" cellpadding="5"
 +
| bgcolor="#E0E0E0" width="21" style="border: 1px solid" |  || <sub>Alternative event flow.</sub>
 +
|}
  
* User gets a feedback message informing if transaction was successful.
+
 
 +
'''Successful Post-conditions:'''
 +
 
 +
* User gets a feedback message informing that transaction was successful.
 
* Meeting has its information updated.
 
* Meeting has its information updated.
 
* User see updated meeting in the calendar page.
 
* User see updated meeting in the calendar page.
Line 96: Line 109:
 
{| class="wikitable" border="1" cellpadding="5"
 
{| class="wikitable" border="1" cellpadding="5"
 
|-
 
|-
! 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. || All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
 
|-
 
|-
| 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. || All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
 
|-
 
|-
| Chooses to delete meeting by clicking the "Delete" button. || Prompts if meeting shall really be deleted. || Database is not affected.
+
| style="text-align: center;" rowspan="2" | 3 || rowspan="2" | Confirms whether (1) or not (2) meeting shall be deleted. || (1). Deletes meeting and schedule details.  || (1). All meeting data (meeting title, presenter-only camera, public whiteboard, meeting recorded, meeting date, meeting schedule, and attendees whitelist definitions) is deleted from the database. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
 
|-
 
|-
| 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.
+
| bgcolor="#E0E0E0" | (2). Returns to home page.  || bgcolor="#E0E0E0" | (2). Database is not affected.
 
|}
 
|}
  
  
'''Post-conditions:'''
+
'''Successful Post-conditions:'''
  
* User gets a feedback message informing if transaction was successful.
+
* User gets a feedback message informing that transaction was successful.
 
* Meeting is deleted.
 
* Meeting is deleted.
* User see updated calendar page (without meeting).
+
* User see updated calendar page (without the meeting).

Latest revision as of 15:27, 18 June 2013

Manage Meetings

Brief Description:

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


Scenario 1: Create new meeting.

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 Meeting" button. Returns a page with editable fields regarding meeting details. Database is not affected.
2 Fills in editable fields. Performs data validation on editable fields. Database is not affected.
3 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.
4 Fills in editable fields and chooses to save schedule. Validates fields and prompts if 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 meeting details including updated schedule information. Database is not affected.
6 (1). Chooses to save meeting, or (2). chooses to cancel meeting creation process. (1). Persists meeting and schedule details. (1). Meeting title, presenter-only camera, public whiteboard, meeting recorded, meeting date, meeting schedule, and attendees whitelist definitions are added to the database. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
(2). Discards inserted meeting and schedule details. (2). Database is not affected.


Alternative event flow.


Successful Post-conditions:

  • User gets a feedback message informing that transaction was successful.
  • A new meeting 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.

Comments:

  • Do we need system data validation on step 4?
  • It's difficult for me to understand the data used on step 6.-----Gary Deng


Scenario 2: Edit meeting.

Preconditions:

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


Step# Actor System Data Used
1 Searches a meeting by using the calendar and clicks the meeting label. Returns a page with editable fields regarding the respective meeting. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
2 Makes changes in editable fields. System performs data validation. 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. Validates fields and 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 meeting details including updated schedule information. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
6 (1). Chooses to save edited meeting, or (2). chooses to cancel meeting editing process. (1). Persists edited meeting and schedule details. (1). Meeting title, presenter-only camera, public whiteboard, meeting recorded, meeting date, meeting schedule, and attendees whitelist definitions are added to the database. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
(2). Discards edited meeting and schedule details. (2). Database is not affected.


Alternative event flow.


Successful Post-conditions:

  • User gets a feedback message informing that transaction was successful.
  • 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.


Step# Actor System Data Used
1 Searches a meeting by using the calendar and clicks the meeting label. Returns a page with editable fields regarding the respective meeting. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
2 Chooses to delete meeting by clicking the "Delete" button. Prompts if meeting shall really be deleted. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
3 Confirms whether (1) or not (2) meeting shall be deleted. (1). Deletes meeting and schedule details. (1). All meeting data (meeting title, presenter-only camera, public whiteboard, meeting recorded, meeting date, meeting schedule, and attendees whitelist definitions) is deleted from the database. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
(2). Returns to home page. (2). Database is not affected.


Successful Post-conditions:

  • User gets a feedback message informing that transaction was successful.
  • Meeting is deleted.
  • User see updated calendar page (without the meeting).