1
edit
Changes
no edit summary
= '''Brief Description:Manage Meetings''' This is a template to copy and paste into other pages.Manage Meeting=
'''Scenario 1Brief Description:''' Create new meeting
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.
{| 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.
|-
| What the actors doesstyle="text-align: center;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct. ||bgcolor="#E0E0E0" | What Returns to the system does page with previously filled in responsemeeting details including updated schedule information. || The data fields retrieved, added, removed, by the systembgcolor="#E0E0E0" | Database is not affected.
|-
| Clicks on the empty section of a calendar date or clicks the style="text-align: center;" rowspan="2" bgcolor="#E0E0E0" | 6 || rowspan="Create Event2" button| (1). Chooses to save meeting, or (2). chooses to cancel meeting creation process. || Returns a page with editable fields/drop-downs regarding (1). Persists meeting and schedule details. || Database is not affected(1).| Chooses "Meeting" as type of event from the droptitle, presenter-down listonly camera, public whiteboard, meeting recorded, meeting date, meeting schedule, and then fills attendees whitelist definitions are added to the database. All fields in editable fields the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and optionally chooses to create a schedule'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" | || <sub>Alternative event flow.</sub>
|}
'''PostconditionsSuccessful Post-conditions:''' The final results of the scenario running (ex * User gets a feedback message informing that transaction was successful. * A record new meeting is added to user's calendar.* On the screen, user has been the option to create another meeting, to view the createdmeeting being shown in the calendar, edited, etc.)and to simply return to the calendar page. ''' Comments:'''* Do we need system data validation on step 4?* It also includes the page that 's difficult for me to understand the user ends data used onstep 6.-----Gary Deng =='''Scenario 2:''' Edit meeting.==
'''Scenario 2Preconditions:''' Edit meeting
* User is authenticated.
{| 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 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 edited schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.
|-
| What the actors doesstyle="text-align: center;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct. || What bgcolor="#E0E0E0" | Returns to the system does page with previously filled in responsemeeting details including updated schedule information. || The data bgcolor="#E0E0E0" | All fields retrievedin the 'meeting', added'meeting_schedule', removed'meeting_presentation', by the system'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" | || <sub>Alternative event flow.</sub>|} '''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. =='''PostconditionsScenario 3:''' Delete meeting.== '''Preconditions:''' * 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 || 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' The final results of , and '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 scenario running '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. || (ex1). A record has been createdDeletes 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', edited'meeting_attendee', etcand 'meeting_guest' tables are used.|-| bgcolor="#E0E0E0" | (2). It also includes the Returns to 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 user ends onmeeting).