Open main menu

CDOT Wiki β

Changes

BBB BUC DAdmin MngMeeting

5,065 bytes added, 15:32, 14 June 2013
no edit summary
= '''Brief Description:Manage Meeting''' This is a template to copy and paste into other pages.=
'''Brief Description:'''
'''Scenario 1:''' Create new meetingUser can manage meetings by creating, editing, and excluding them.
=='''Scenario 1:''' Create new meeting.== '''Preconditions:''' Includes anything that has been set up before starting the scenario * User is authenticated. It must include what page the user  * User is on before accessing the scenario startshome 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 Event" button. || Returns a page with editable fields regarding meeting details. || Database is not affected.|-| style="text-align: center;" | 2 || Chooses "Meeting" as type of event from the drop-down list. || Event Type field is set to "Meeting". || Database is not affected.|-| style="text-align: center;" | 3 || Fills in editable fields. || Filled in fields are respectively set. || Database is not affected.|-| style="text-align: center;" bgcolor="#E0E0E0" | 4 || 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" | 5 || bgcolor="#E0E0E0" | Fills in editable fields and chooses to save schedule. || bgcolor="#E0E0E0" | Prompts if schedule information is correct. || bgcolor="#E0E0E0" | Database is not affected.|-| style="text-align: center;" bgcolor="#E0E0E0" | 6 || 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.
|-
| What the actors doesstyle="text-align: center;" rowspan="2" bgcolor="#E0E0E0" | 7 || rowspan="2" | (1). Chooses to save meeting, or (2). chooses to cancel meeting creation process. || What the system does in response(1). Persists meeting and schedule details. || The data fields retrieved(1). Meeting title, addedif camera activation will only be available for the presenter, if a whiteboard will be used, if the meeting will be recorded, meeting date, removedmeeting schedule, by and attendees white-list definitions are added to the systemdatabase.
|-
| bgcolor="#E0E0E0" |(2). Discards inserted meeting and schedule details. | |bgcolor="#E0E0E0" |(2). Database is not affected.
|}
'''Postconditions{| border="1" cellpadding="5"| bgcolor="#E0E0E0" width="21" style="border:''' The final results of the scenario running (ex. A record has been created, edited, etc.). It also includes the page that the user ends on1px solid" | || <sub>Alternative event flow.</sub>|}
'''Scenario 2Successful Post-conditions:''' Edit meeting
* User gets a feedback message informing successful transaction.
* A new meeting is added to user's calendar.
* On the screen, 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.
  =='''Scenario 2:''' Edit meeting.==  '''Preconditions:''' Includes anything that has been set up before starting the scenario * User is authenticated. It must include what page the user  * User is on before accessing the scenario startshome page.
{| class="wikitable" border="1" cellpadding="5"
|-
! 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 fields retrieved, added, removed, by the systemDatabase is not affected.
|-
| style="text-align: center;" |2 | |Makes changes in editable fields. || Filled in fields are correspondingly set. || 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 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" | Database is not affected.|-| 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 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 updated in the database.|-| 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>|}  '''PostconditionsSuccessful Post-conditions:''' The final results of  * User gets a feedback message informing successful transaction.* Meeting has its information updated.* User see updated meeting in the scenario running calendar page.   =='''Scenario 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. || 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. || Database is not affected.|-| style="text-align: center;" | 3 || Confirms whether or not meeting shall be deleted. || Deletes meeting and schedule details. || All meeting data (ex. A record has been createdmeeting 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, editedmeeting schedule, etcand attendees white-list definitions) is deleted from the database.|}  '''Successful Post-conditions:''' * User gets a feedback message informing successful transaction.)* Meeting is deleted. It also includes the * User see updated calendar page that the user ends on(without meeting).