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 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.

| Clicks on the empty section of a calendar date or clicks the style="Create Eventtext-align: center;" bgcolor="#E0E0E0" | 4 || bgcolor=" button#E0E0E0" | Fills in editable fields and chooses to save schedule. || Returns a page with editable bgcolor="#E0E0E0" | Validates fields/drop-downs regarding meeting detailsand prompts if schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.

| Chooses style="Meetingtext-align: center;" bgcolor="#E0E0E0" as type of event from | 5 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct. || bgcolor="#E0E0E0" | Returns to the drop-down list, and then fills page with previously filled in editable fieldsmeeting details including updated schedule information. || |bgcolor="#E0E0E0" | Database is not affected.

| Optionally style="text-align: center;" rowspan="2" bgcolor="#E0E0E0" | 6 || rowspan="2" | (1). Chooses to save meeting, or (2). chooses to create a schedule by clicking the "Edit Schedule" button cancel meeting creation process. || (1). Persists meeting and schedule details. || 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 databasebgcolor="#E0E0E0" | (2). Database is not affected.

System{| border="1" cellpadding="5"| bgcolor="#E0E0E0" width="21" style="border: Returns 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 with editable fields/drop, 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.-----downs regarding schedule details.Gary Deng  

Actor=='''Scenario 2: Fills in editable fields and chooses to save schedule''' Edit meeting.==

Actor'''Preconditions: Accepts.'''

System: Returns page with previously filled in meeting details* User is authenticated.Alternative Events Flow

* User gets {| 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 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 feedback message informing 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" | Validates fields and prompts if transaction was successfuledited schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.* A new meeting |-| style="text-align: center;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is added correct. || bgcolor="#E0E0E0" | Returns to userthe page with previously filled in meeting details including updated schedule information. || bgcolor="#E0E0E0" | All fields in the 's calendarmeeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.* On the screen|-| style="text-align: center;" rowspan="2" | 6 || rowspan="2" | (1). Chooses to save edited meeting, user has the option or (2). chooses to create another cancel meeting editing process. || (1). Persists edited meeting and schedule details. ||(1). Meeting title, presenter-only camera, public whiteboard, meetingrecorded, meeting date, meeting schedule, and attendees whitelist definitions are added to view the created meeting being shown database. All fields in the calendar'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and to simply return to '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.}|}  '''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.==

'''Scenario 2:''' Edit meeting* User is authenticated.

! 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).