Describes the system based on events and corresponding actions to accomplish the event
| Event ID | Event | Action | Condition | Required Data | Active/Archived | Questions/Notes |
| 1 | User wants to book a meeting | Application is up and running. | User has access to a terminal which has capable of logging into SMM and the client software is installed on the device that user use. | . | . | . |
| . | . | User selects the date for the meeting | User's calendar is up to date with all the upcoming meetings and reminders | Date of the meeting | . | . |
| . | . | User selects the type of the meeting | The types are loaded according to user's preferences and previous meetings' types (Learned behaviour) | Type of the meeting | . | . |
| . | . | Based on the type SMM proposes a recipient list | People who are attended that type of meeting before are searched on the database | Automaticaly populated attendee list | . | . |
| . | . | User adds or removes attendees | . | Amended attendee list | . | . |
| . | . | SMM checks the availability of the attendees. | A connection exist to the main SMM server | Date and Type of the meeting. Attendee list. Returns a list of suggested dates if the attendees are busy for the initialy proposed time | . | . |
| . | . | User browses through proposed dates by SMM if there is a clash. | A list of proposed dates are returned from the SMM server. | Proposed dates | . | Will be broadly discussed in another Event/Action list |
| . | . | User selects a proper date | No clash with any of the attendees or some minor clashes. | Selected date | . | . |
| . | . | User enters a subject for the meeting | . | . | . | . |
| . | . | User attaches documents to be discussed in meeting | . | Location of the document (link) or the document itself will be attached to the document | . | . |
| . | . | SMM defines whether to send attachment or link to the attendees | Document is available to SMM | A link property or document itself | . | . |
| . | . | User selects a room for the meeting either proposed by SMM or from a list | Rooms data are entered in to the SMM system | Room location, capacity, equipments | . | Will be broadly discussed in another Event/Action list |
| . | . | User clicks SEND button to send the meeting request to attendees. | Meeting's date, time, attendees, subject, attached or linked documents are set. | Attendees profile will be updated to be synchronised or updated when they next login. | . | . |
The "action" column should be the "condition" and vice versa. You did this with your COMP8120 assignment too!
You've also listed "events" in the "action" column. You need to think of "events" as something that stimulates the system to an "action". The "conditions" are simply an indication of what mode/state the system is in when the "event" & "action" combination occur. "User wants to book a meeting" is not an "event" (or at the vary least is ambiguous. What you should describe as an "event" is "User requests a meeting".