Changes

== '''Manage MeetingMeetings'''==

=='''Scenario 1:''' Create new meeting.==

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

| style="text-align: center;" | 1 || Clicks on the empty section of a calendar date, or clicks the "Create EventMeeting" button. || Returns a page with editable fields/drop-downs regarding meeting details. || Database is not affected.

| Chooses style="Meetingtext-align: center;" as type of event from the drop-down list| 2 || Fills in editable fields. || Event Type field is set to "Meeting"Performs data validation on editable fields. || Database is not affected.

| Fills in editable fieldsstyle="text-align: center;" bgcolor="#E0E0E0" | 3 || bgcolor="#E0E0E0" |Optionally, chooses to create a schedule by clicking the "Edit Schedule" button. || Filled in bgcolor="#E0E0E0 " | Returns a screen with editable fields are respectively setregarding schedule details. || bgcolor="#E0E0E0" | Database is not affected.

| style="text-align: center;" bgcolor="#E0E0E0" |Optionally, 4 || bgcolor="#E0E0E0" | Fills in editable fields and chooses to create a save schedule by clicking the "Edit Schedule" button. || bgcolor="#E0E0E0 " | Returns a screen with editable Validates fields/drop-downs regarding and prompts if schedule detailsinformation 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 scheduleConfirms whether or not inserted information is correct. || bgcolor="#E0E0E0" | Prompts if Returns to the page with previously filled in meeting details including updated schedule information is correct and can be stored. || bgcolor="#E0E0E0" | Database is not affected.

| style="text-align: center;" rowspan="2" bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct. 6 || bgcolorrowspan="#E0E0E02" | Updates schedule information returning (1). Chooses to save meeting, or (2). chooses to the page with previously filled in cancel meeting creation process. || (1). Persists meeting and schedule details. || bgcolor="#E0E0E0" | Database is not affected(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.

| Chooses to save meetingbgcolor="#E0E0E0" | (2). || Persists Discards inserted meeting and schedule details. || 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" | Chooses to cancel meeting creation process(2). Database is not affected. |}   {| bgcolorborder="1" cellpadding="#E0E0E05" | Discards inserted meeting and schedule details. || bgcolor="#E0E0E0" width="21" style="border: 1px solid" | Database is not affected || _{Alternative event flow.}

'''Successful Post-conditions:'''

* User gets a feedback message informing if that transaction was successful.

=='''Scenario 2:''' Edit meeting.==

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

| style="text-align: center;" | 1 || Searches a meeting by using the calendar. Clicks and clicks the meeting label. || Returns a page with editable fields regarding the respective meeting. || Database is not affectedAll 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/drop-downs 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 and can be stored. || 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" | Updates schedule information returning Returns to the page with previously filled in meeting detailsincluding updated schedule information. || bgcolor="#E0E0E0" | Database is not affectedAll 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 meetingediting 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 white-list 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" | Chooses to cancel (2). Discards edited meeting creation processand schedule details. || bgcolor="#E0E0E0" | Discards inserted meeting and schedule details(2). Database is not affected. |}  {| border="1" cellpadding="5"| bgcolor="#E0E0E0" width="21" style="border: 1px solid" | Database is not affected || _{Alternative event flow.}

'''Successful Post-conditions:'''

* User gets a feedback message informing if that transaction was successful.* A new Meeting has its information updated.* User see updated meeting in the calendar page.   =='''Scenario 3:''' Delete meeting.==  '''Preconditions:''' * User is added to user's calendarauthenticated. * On 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 screen, user has meeting label. || Returns a page with editable fields regarding the respective meeting. || All fields in the option to create another 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.|-| style="text-align: center;" | 2 || Chooses to view delete meeting by clicking the created "Delete" button. || Prompts if meeting being shown shall really be deleted. || All fields in the calendar'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 simply return to the home page. || bgcolor="#E0E0E0" | (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).