| 15 | | 1. A scheduler, which deals with all scheduling information. |
| 16 | | Goal: is to reduce communication costs and time costs |
| 17 | | 2. Database: which saves the information of all possible users available. |
| 18 | | Data included: calendar, physical rooms data, virtual room data, user information, user preferences (dates they can and can’t attend meetings), scheduled meetings, |
| 19 | | 3. GUI, the interface that the user will interact with. |
| 20 | | |
| 21 | | |
| | 18 | 1. A scheduler, which deals with all scheduling information. |
| | 19 | * Goal: is to reduce communication costs and time costs |
| | 20 | 2. Database: which saves the information of all possible users available. |
| | 21 | * Data included: calendar, physical rooms data, virtual room data, user information, user preferences (dates they can and can’t attend meetings), scheduled meetings, |
| | 22 | 3. GUI, the interface that the user will interact with. |
| 29 | | |
| 30 | | 1. hardware requirements (i.e. explore 6.0, XP…) |
| 31 | | |
| 32 | | |
| 33 | | 2. Information requirements (what information is needed to schedule a meeting) |
| 34 | | |
| 35 | | |
| 36 | | 3. Our system is user-friend |
| 37 | | |
| 38 | | 4. Please respond to the server messages of scheduled meeting ASAP |
| | 30 | 1. hardware requirements (i.e. explore 6.0, XP…) |
| | 31 | 2. Information requirements (what information is needed to schedule a meeting) |
| | 32 | 3. Our system is user-friend |
| | 33 | 4. Please respond to the server messages of scheduled meeting ASAP |
| 47 | | |
| 48 | | 1. Login to www.oursystem.com the system website |
| 49 | | |
| 50 | | |
| 51 | | 2. Create user, by adding all data stated above |
| 52 | | |
| 53 | | |
| 54 | | 3. Wait a few days for the registration to be authorized by us. |
| 55 | | |
| 56 | | |
| 57 | | 4. Registration granted/denied |
| | 42 | 1. Login to www.oursystem.com the system website |
| | 43 | 2. Create user, by adding all data stated above |
| | 44 | 3. Wait a few days for the registration to be authorized by us. |
| | 45 | 4. Registration granted/denied |
| 91 | | |
| 92 | | 1. our server is secure, privacy is guaranteed, so I think we should run this under https??? |
| 93 | | |
| 94 | | |
| 95 | | 2. Our database information will not have any flaw. |
| 96 | | |
| 97 | | |
| 98 | | 3. We assume that all users will respond ASAP (within 24 hours) to the meeting request |
| 99 | | |
| | 65 | 1. Our server is secure, privacy is guaranteed, so I think we should run this under https??? |
| | 66 | 2. Our database information will not have any flaw. |
| | 67 | 3. We assume that all users will respond ASAP (within 24 hours) to the meeting request |
| 108 | | 1. Receives the data from the client |
| 109 | | |
| 110 | | |
| 111 | | 2. Checks if there are any conflicts in the information |
| 112 | | |
| 113 | | |
| 114 | | 3. If there is, respond to the client for rectification, else, send information to the scheduler. |
| | 76 | 1. Receives the data from the client |
| | 77 | 2. Checks if there are any conflicts in the information |
| | 78 | 3. If there is, respond to the client for rectification, else, send information to the scheduler. |
| 139 | | 1. Information for all users |
| 140 | | |
| 141 | | |
| 142 | | -Preferences for meeting time |
| 143 | | |
| 144 | | |
| 145 | | -Current location (real-time update?) |
| 146 | | |
| 147 | | |
| 148 | | -Personal information |
| 149 | | |
| 150 | | |
| 151 | | 2. Physical rooms available |
| 152 | | |
| 153 | | |
| 154 | | 3. Virtual rooms available |
| 155 | | |
| 156 | | |
| 157 | | 4. Scheduled meeting information (there might be cases where rescheduling is being requested even before the server responds to the client, so we need to have information about this) |
| 158 | | |
| 159 | | |
| | 98 | 1. Information for all users |
| | 99 | * Preferences for meeting time |
| | 100 | * Current location (real-time update?) |
| | 101 | * Personal information |
| | 102 | 2. Physical rooms available |
| | 103 | 3. Virtual rooms available |
| | 104 | 4. Scheduled meeting information (there might be cases where rescheduling is being requested even before the server responds to the client, so we need to have information about this) |
| 168 | | 1) Go to the office where the sign up sheet is located.[[BR]] |
| 169 | | 2) Pick several dates and times for a meeting.[[BR]] |
| | 112 | 1. Go to the office where the sign up sheet is located. |
| | 113 | 2. Pick several dates and times for a meeting. |
| | 114 | * Room size |
| | 115 | * Teleconference availability |
| | 116 | 3. Email meeting participants to see who is available when, based on chosen dates and times. |
| | 117 | 4. If all participants available at same date and time, go to step 5, if not repeat from step 1. |
| | 118 | 5. Go back to sign up sheet, if chosen time and date is still available, then sign up and go to step 6, else go to step 1. |
| | 119 | 6. Email all participants the date, time and location of meeting. |
| | 120 | 7. If not using email then visit/call each participant or send memo to tell each participant the date, time and location of meeting. |
| 171 | | * Room size |
| 172 | | * Teleconference availability |
| 173 | | [[BR]] |
| 174 | | 3) Email meeting participants to see who is available when, based on chosen dates and times.[[BR]] |
| 175 | | 4) If all participants available at same date and time, go to step 5, if not repeat from step 1.[[BR]] |
| 176 | | 5) Go back to sign up sheet, if chosen time and date is still available, then sign up and go to step 6, else go to step 1.[[BR]] |
| 177 | | 6) Email all participants the date, time and location of meeting.[[BR]] |
| 178 | | 7) If not using email then visit/call each participant or send memo to tell each participant the date, time and location of meeting.[[BR]] |
| 179 | | |
| 180 | | = José's Brainstorming = |
| 181 | | ---- |
| | 122 | == José's Brainstorming == |
| 184 | | 0) Continue from Russell's step 6-7 but with a added funtion.[[BR]] |
| 185 | | 1) Create meeting with either low, medium, high priorty.[[BR]] |
| 186 | | 2) Priority meanings:[[BR]] |
| | 125 | 0. Continue from Russell's step 6-7 but with a added funtion. |
| | 126 | 1. Create meeting with either low, medium, high priorty. |
| | 127 | 2. Priority meanings: |
| | 128 | * Low-Meeting is considered not urgent at all but required |
| | 129 | * Medium-Meeting is consider semi-urgent and has higher precendence then Low prioirty meetings |
| | 130 | * High-Meeting is consider of the highest urgency and has precedence over all others(such as Low and Medium) |
| | 131 | * '''Note:''' Meetings encountered with the same priority have the same precedence |
| | 132 | 3. Then meeting will be then set up according to date, time and location of meeting and then if all else fails and there is two meetings at the same date,time and location then this is where the meetings priority comes into play. |
| | 133 | 4. Meeting priorty is checked with the other meeting(s) priority. If conflicting meeting has different has different priority then continue to step 5 and if the have the same continue to step 6. |
| | 134 | 5. If created meeting has ''higher priorty'' then prompt user whether it is ok to overwrite current meeting or ask user whether to change the meeting date,time or location depending on the conflicting attribute.If meeting is overwrite then notify the participants of that meeting that the meeting has been changed due to a meeting of higher importance. If meeting being created is ''lower priority'' then inform user that meeting cannot be created. |
| | 135 | 6. If the same then meeting will not be created. |
| | 136 | 7. Email all participants the date, time and location of meeting.(Russell's step) |
| | 137 | 8. If not using email then visit/call each participant or send memo to tell each participant the date, time and location of meeting.(Russell's step) |
| 188 | | * Low-Meeting is considered not urgent at all but required |
| 189 | | * Medium-Meeting is consider semi-urgent and has higher precendence then Low prioirty meetings |
| 190 | | * High-Meeting is consider of the highest urgency and has precedence over all others(such as Low and Medium) |
| | 139 | '''Constraints:'''[[BR]] |
| | 140 | 1. Only allow certain number of users to have the ability to select meetings of high importance such as a CEO.[[BR]] |
| | 141 | 2. Only allow overwriting of meeting(s) over a certain period of time: |
| | 142 | * Low- Never since low priority meetings can't get precedence over any other priority including itself |
| | 143 | * Medium- Created within 5 days or more before actual meeting is going to be held (Note only applicable to Low priority) |
| | 144 | * High- Created within 1 or 2(Not sure yet) days or more before actual meeting is going to be held (Note only applicable to Medium and Low priorities) |
| 192 | | '''Note:'''Meetings encountered with the same priority have the same precedence |
| 193 | | [[BR]] |
| 194 | | 3) Then meeting will be then set up according to date, time and location of meeting and then if all else fails and there is two meetings at the same date,time and location then this is where the meetings priority comes into play.[[BR]] |
| 195 | | 4) Meeting priorty is checked with the other meeting(s) priority. If conflicting meeting has different has different priority then continue to step 5 and if the have the same continue to step 6.[[BR]] |
| 196 | | 5) If created meeting has ''higher priorty'' then prompt user whether it is ok to overwrite current meeting or ask user whether to change the meeting date,time or location depending on the conflicting attribute.If meeting is overwrite then notify the participants of that meeting that the meeting has been changed due to a meeting of higher importance. If meeting being created is ''lower priority'' then inform user that meeting cannot be created.[[BR]] |
| 197 | | 6) If the same then meeting will not be created.[[BR]] |
| 198 | | 7) Email all participants the date, time and location of meeting.(Russell's step)[[BR]] |
| 199 | | 8) If not using email then visit/call each participant or send memo to tell each participant the date, time and location of meeting.(Russell's step) |
| 200 | | [[BR]][[BR]] |
| 201 | | '''Constraints:'''[[BR]] |
| 202 | | 1) Only allow certain number of users to have the ability to select meetings of high importance such as a CEO.[[BR]] |
| 203 | | 2) Only allow overwriting of meeting(s) over a certain period of time:[[BR]] |
| 204 | | * Low - Never since low priority meetings can't get precedence over any other priority including itself |
| 205 | | * Medium- Created within 5 days or more before actual meeting is going to be held (Note only applicable to Low priority) |
| 206 | | * High- Created within 1 or 2(Not sure yet) days or more before actual meeting is going to be held (Note only applicable to Medium and Low priorities) |
| 207 | | |
| 208 | | [[BR]][[BR]] |
| 212 | | 1- Login in case you're in the system. Otherwise create a username and password[[BR]] |
| 213 | | 2- Reserve a date to schedule a meeting. [[BR]] |
| 214 | | 3- Make sure that the meeting room, the time and all people that will attend the meeting are available[[BR]] |
| 215 | | - if conflicts occur, extend the date range or have some participants remove/add some dates or withdraw from the meeting[[BR]] |
| 216 | | - if conflicts do not occur, then reserve the room and pick the participants[[BR]] |
| 217 | | 5- Specify the room requirements (telephone, projectors, etc.)[[BR]] |
| 218 | | 6- Specify the objective of the meeting[[BR]] |
| 219 | | 7- Contact participants[[BR]] |
| 220 | | 8- Confirm your reservation[[BR]] |
| 221 | | 8- Notify the participants[[BR]] |
| 222 | | 9- Send Reminders[[BR]] |
| | 149 | 1. Login in case you're in the system. Otherwise create a username and password |
| | 150 | 2. Reserve a date to schedule a meeting. |
| | 151 | 3. Make sure that the meeting room, the time and all people that will attend the meeting are available |
| | 152 | * if conflicts occur, extend the date range or have some participants remove/add some dates or withdraw from the meeting[[BR]] |
| | 153 | * if conflicts do not occur, then reserve the room and pick the participants |
| | 154 | 5. Specify the room requirements (telephone, projectors, etc.) |
| | 155 | 6. Specify the objective of the meeting |
| | 156 | 7. Contact participants |
| | 157 | 8. Confirm your reservation |
| | 158 | 9. Notify the participants |
| | 159 | 10. Send Reminders |
