Changes

= '''Brief Description:Manage Meetings''' This is a template to copy and paste into other pages.=

=='''Scenario 1:''' Create new meeting.== '''Preconditions:''' Includes anything  * 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 || 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.|-| style="text-align: center;" | 2 || Fills in editable fields. || Performs data validation on editable fields. || 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.|-| 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.|-| 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, 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 inserted meeting and schedule details. || bgcolor="#E0E0E0" | (2). Database is not affected.|}   {| border="1" cellpadding="5"| bgcolor="#E0E0E0" width="21" style="border: 1px solid" | || _{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 been set up before starting the scenariooption 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 must include what page 's difficult for me to understand the user data used on step 6.-----Gary Deng   =='''Scenario 2:''' Edit meeting.==  '''Preconditions:''' * User is authenticated. * User is on before accessing the scenario startshome page.

! 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.|-| style="text-align: center;" | 2 || Makes changes in editable fields. || System 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.

| What the actors does. style="text-align: center;" bgcolor="#E0E0E0" | 4 ||bgcolor="#E0E0E0" | What the system does Makes changes in responseeditable fields and chooses to save schedule. || The data bgcolor="#E0E0E0" | Validates fields retrieved, added, removed, by the systemand 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, 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.

{| border="1" cellpadding="5"| bgcolor="#E0E0E0" width="21" style="border: 1px solid" | || _{Alternative event flow.}|}  '''PostconditionsSuccessful Post-conditions:''' The final results of the scenario running (ex * User gets a feedback message informing that transaction was successful. A record * Meeting has been created, edited, etcits information updated.). It also includes * User see updated meeting in the calendar page that the user ends on.

! Step# !! Actor !! System !! Data Used

| What style="text-align: center;" | 1 || Searches a meeting by using the actors doescalendar and clicks the meeting label. || What Returns a page with editable fields regarding the system does in responserespective meeting. || The data All fields retrievedin the 'meeting', 'meeting_schedule', added'meeting_presentation', removed'meeting_attendee', by the systemand 'meeting_guest' tables are used.

| 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, 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.|-| bgcolor="#E0E0E0" | (2). Returns to home page. || bgcolor="#E0E0E0" | (2). Database is not affected.

'''PostconditionsSuccessful Post-conditions:''' The final results of the scenario running (ex * User gets a feedback message informing that transaction was successful. A record has been created, edited, etc* Meeting is deleted.). It also includes the * User see updated calendar page that (without the user ends onmeeting).