Changes

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

=='''Scenario 1:''' Create new lecture.== '''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.

! 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 lecture details. || Database is not affected.|-| style="text-align: center;" | 2 || Chooses "Lecture" as type of event from the drop-down list. || "Event Type" field is set to "Lecture". || 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 lecture 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 lecture, or (2). chooses to cancel lecture creation process. || What the system does in response(1). Persists lecture and schedule details. || The data (1). Lecture title, presenter-only camera, public whiteboard, lecture recorded, lecture date, lecture schedule, and attendees whitelist definitions are updated in the database. All fields retrievedin the 'lecture', added'lecture_schedule', removed'lecture_presentation', by the system'lecture_attendance', and 'guest_lecturer' tables are used.

| bgcolor="#E0E0E0" |(2). Discards inserted lecture 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" | || _{Alternative event flow.}|}

'''Scenario 2Successful Post-conditions:''' Edit meeting

  =='''Scenario 2:''' Edit lecture.==  '''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.

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

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

| 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 lecture details including updated schedule information. || bgcolor="#E0E0E0" | All fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.|-| style="text-align: center;" rowspan="2" | 6 || rowspan="2" | (1). Chooses to save edited lecture, or (2). chooses to cancel lecture editing process. || (1). Persists edited lecture and schedule details. || (1). Lecture title, presenter-only camera, public whiteboard, lecture recorded, lecture date, lecture schedule, and attendees whitelist definitions are updated in the database. All fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used|-| bgcolor="#E0E0E0" | (2). Discards edited lecture 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:'''Postconditions * User gets a feedback message informing that transaction was successful.* Lecture has its information updated.* User see updated lecture in the calendar page.   =='''Scenario 3:''' Delete lecture.==  '''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 lecture by using the calendar, and clicks the lecture label. || Returns a page with editable fields regarding the respective lecture. || All fields in the 'lecture', ' The final results of lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.|-| style="text-align: center;" | 2 || Chooses to delete lecture by clicking the scenario running "Delete" button. || Prompts if lecture shall really be deleted. || All fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.|-| style="text-align: center;" rowspan="2" | 3 || rowspan="2" | Confirms whether or not lecture shall be deleted. || Deletes lecture and schedule details. || All lecture data (exlecture title, presenter-only camera, public whiteboard, lecture recorded, lecture date, lecture schedule, and attendees whitelist definitions) is deleted from the database. A record has been createdAll fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', edited'lecture_attendance', etcand 'guest_lecturer' 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.* Lecture is deleted.* User see updated calendar page (without the user ends onlecture).