BBB BUC Emp MngMeeting
Revision as of 10:25, 14 June 2013 by Ystallonne Alves (talk | contribs)
Manage Meeting
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.
| Actor | System | Data Used |
|---|---|---|
| Clicks on the empty section of a calendar date, or clicks the "Create Event" button. | Returns a page with editable fields/drop-downs regarding meeting details. | Database is not affected. |
| Chooses "Meeting" as type of event from the drop-down list. | Event Type field is set to "Meeting". | Database is not affected. |
| Fills in editable fields. | Filled in fields are respectively set. | Database is not affected. |
| Optionally, chooses to create a schedule by clicking the "Edit Schedule" button. | Returns a screen with editable fields/drop-downs regarding schedule details. | Database is not affected. |
| Fills in editable fields and chooses to save schedule. | Prompts if schedule information is correct. | Database is not affected. |
| Confirms whether or not inserted information is correct. | Updates schedule information returning to the page with previously filled in meeting details. | Database is not affected. |
| Chooses to save meeting. | Persists 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 database. |
| Chooses to cancel meeting creation process. | Discards inserted meeting and schedule details. | Database is not affected. |
Post-conditions:
- User gets a feedback message informing if 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.
Scenario 2: Edit meeting.
Preconditions:
- User is authenticated.
- User is accessing the home page.
| Actor | System | Data Used |
|---|---|---|
| Searches a meeting by using the calendar. Clicks the meeting label. | Returns a page with editable fields regarding the respective meeting. | Database is not affected. |
| Makes changes in editable fields. | Filled in fields are correspondingly set. | Database is not affected. |
| Optionally, chooses to modify the schedule by clicking the "Edit Schedule" button. | Returns a screen with editable fields/drop-downs regarding schedule details. | Database is not affected. |
| Makes changes in editable fields and chooses to save schedule. | Prompts if edited schedule information is correct. | Database is not affected. |
| Confirms whether or not inserted information is correct. | Updates schedule information returning to the page with meeting details. | Database is not affected. |
| (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. |
| (2). Discards edited meeting and schedule details. | (2). Database is not affected. |
Post-conditions:
- User gets a feedback message informing if 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.
