Difference between revisions of "BBB BUC Emp MngMeeting"
| Line 34: | Line 34: | ||
| 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 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. | + | | ''Chooses to cancel meeting creation process. || Discards inserted meeting and schedule details. || Database is not affected.'' |
|} | |} | ||
Revision as of 17:04, 13 June 2013
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 the schedule information is correct and can be stored. | Database is not affected. |
| Confirms whether or not inserted information is correct. | Updates schedule information returning 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: Includes anything that has been set up before starting the scenario. It must include what page the user is on before the scenario starts.
| Actor | System | Data Used |
|---|---|---|
| What the actors does. | What the system does in response. | The data fields retrieved, added, removed, by the system. |
Postconditions: The final results of the scenario running (ex. A record has been created, edited, etc.). It also includes the page that the user ends on.
