BBB BUC Emp MngMeeting

From CDOT Wiki
Jump to: navigation, search

Manage Meetings

Brief Description:

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.


Step# Actor System Data Used
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.
2 Fills in editable fields. Performs data validation on editable fields. Database is not affected.
3 Optionally, chooses to create a schedule by clicking the "Edit Schedule" button. Returns a screen with editable fields regarding schedule details. Database is not affected.
4 Fills in editable fields and chooses to save schedule. Validates fields and prompts if schedule information is correct. Database is not affected.
5 Confirms whether or not inserted information is correct. Returns to the page with previously filled in meeting details including updated schedule information. Database is not affected.
6 (1). Chooses to save meeting, or (2). chooses to cancel meeting creation process. (1). Persists 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.
(2). Discards inserted meeting and schedule details. (2). Database is not affected.


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, 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.-----Gary Deng


Scenario 2: Edit meeting.

Preconditions:

  • User is authenticated.
  • User is accessing the home page.


Step# Actor System Data Used
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.
2 Makes changes in editable fields. System performs data validation. Database is not affected.
3 Optionally, chooses to modify the schedule by clicking the "Edit Schedule" button. Returns a screen with editable fields regarding schedule details. Database is not affected.
4 Makes changes in editable fields and chooses to save schedule. Validates fields and prompts if edited schedule information is correct. Database is not affected.
5 Confirms whether or not inserted information is correct. Returns to the page with previously filled in meeting details including updated schedule information. All fields in the 'meeting', 'meeting_schedule', 'meeting_presentation', 'meeting_attendee', and 'meeting_guest' tables are used.
6 (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.
(2). Discards edited meeting and schedule details. (2). Database is not affected.


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.

Preconditions:

  • User is authenticated.
  • User is accessing the home page.


Step# Actor System Data Used
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.
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.
3 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.
(2). Returns to home page. (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).