| 179 | |
| 180 | ---- |
| 181 | = Arturo's Brainstorming = |
| 182 | |
| 183 | The high level requirements are: |
| 184 | |
| 185 | • A web based system that allows the scheduling and control of meetings and the required information. |
| 186 | |
| 187 | • A user will be able to start the program, enter the participants email addresses, choose a time period, choose a day, and type any information that the invitees need before and during the meeting. |
| 188 | |
| 189 | • The user will be able to see the other participants schedules if they are already registered on the system and have enter their schedules for the corresponding day. |
| 190 | |
| 191 | • Each user will be able to enter their schedule information so that other users can use this to schedule meetings trying to avoid schedule conflicts for all attendees. |
| 192 | |
| 193 | • Users will be able to designate the meeting’s priority from an available priority scheme. |
| 194 | |
| 195 | • The user will be able to confirm scheduling the meeting by choosing to do so via a confirmation button and then receiving a confirmation email from the program. |
| 196 | |
| 197 | • Once the confirmation from the program is available, the program will send the meeting invitation to the attendees via the email system. |
| 198 | |
| 199 | • The invitation email will contain the meeting details previously mentioned and will allow the attendee to accept, reject or request a change to the meeting. |
| 200 | |
| 201 | • Several meetings can be scheduled for a specific attendee at one same time, it is the attendee’s responsibility to reply to the meetings confirming either acceptance, rejection or requesting a time and date change. |
| 202 | |
| 203 | • The attendee’s response will be delivered to the meeting organizer via a reply email; the organizer will then take the appropriate actions if the meeting must be re-scheduled by changing the time and date and sending confirmation again. |