Changes

Jump to: navigation, search

BBB BUC Emp MngMeeting

152 bytes removed, 15:27, 18 June 2013
no edit summary
| 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.
|-
| style="text-align: center;" bgcolor="#E0E0E0" | 4 || bgcolor="#E0E0E0" | Fills in editable fields and chooses to save schedule. || bgcolor="#E0E0E0" | Prompts Validates fields and 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.
|-
| 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, if presenter-only camera activation will only be available for the presenter, if a public whiteboard will be used, if the meeting will be 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 inserted meeting and schedule details. || bgcolor="#E0E0E0" | (2). Database is not affected.
* 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.==
| 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.
|-
| style="text-align: center;" | 2 || Makes changes in editable fields. || Filled in fields are correspondingly setSystem performs data validation. || 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 Validates fields and 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" | All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
|-
| 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 presenter-only camera activation will only be available for the presenter, if a public whiteboard will be used, if the meeting will be recorded, meeting date, meeting schedule, and attendees whitelist definitions are updated in 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.
| 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.
|-
| 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, if presenter-only camera activation will only be available for the presenter, if a public whiteboard will be used, if the meeting will be 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.|-| bgcolor="#E0E0E0" | (2). Returns to home page. || bgcolor="#E0E0E0" | (2). Database is not affected.
|}
* Meeting is deleted.
* User see updated calendar page (without the meeting).
 
''' Comments '''
* If actor changes mind and chooses not to delete the meeting on step 3, system should give other options.---Gary Deng

Navigation menu