| 21 | | * NFR1: The SDMS system shall be functionally intuitive. |
| 22 | | * NFR2: The SDMS system shall be easily used. |
| 23 | | * NFR3: The SDMS system shall be |
| | 25 | * NFR1: The SDMS system shall be functionally intuitive |
| | 26 | * NFR2: The SDMS system shall be easily used by non-experts |
| | 27 | * NFR3: The SDMS system shall be accurately monitored (IE: held in virtual place, nomadicity) |
| | 28 | * NFR4: The SDMS system shall replan a meeting as dynamically and flexible as possible |
| | 29 | * NFR5: The SDMS system shall keep the amount of interaction among participants as minimal as possible (number and length of messages) |
| | 30 | * NFR6: The SDMS system shall considerably reduce the amount of overhead usually incurred in meeting organization (potential distributed attendees) |
| | 31 | * NFR7: The SDMS system shall reflect, as closely as possible, the way meetings re typically managed |
| | 32 | * NFR9: The SDMS system shall alert attendees as conviently and early as possible of the date and location of the meeting |
| | 33 | * NFR10: The SDMS system shall accomodate decentralized requests as far as possible (any authorized user can request a meeting independently of their whereabouts) |
| | 34 | * NFR11: The SDMS system shall not allow physical constraints to be broken, (a person cannot attend two or more different meetings at the same time, a meeting room cannot be scheduled for two or meetings at the same time, etc) |
| | 35 | * NFR12: The SDMS system shall provide an appropriate level of performance |
| | 36 | * * NFR12.1: elapsed time between submission of a meeting request and determination of corresponding date/location shall be minimal |
| | 37 | * * NFR12.2: elapsed time between determination of meeting date/location and communication of meeting information to all participants shall be minimal |
| | 38 | * * NFR12.3: a lower bound shall be fixed between the time at which the meeting date is determined and the time at which the meeting is actually taking place |
| | 39 | * NFR13: The SDMS system shall enforce all privacy rules |
| | 40 | * * NFR13.1: non-priviledged particiapnts shall not be allowed to know the constraints stated by other participants |
| | 41 | * NFR14: The SDMS system shall allow customization to professional and private meetings |
| | 42 | * * NFR14.1: different restrictions on the time periods that may be allocated (meeting hours during office hours, private activites during leisure time) |
| | 43 | * NFR15: The SDMS system shall be flexible enough to accomodate evolving data |
| | 44 | * * NFR15.1: varying sets of concerned participants |
| | 45 | * * NFR15.2: address to which participant may be reached may vary |
| | 46 | * NFR16: The SDMS system shall be easily extensible |
| | 47 | * * NFR16.1: handling of explicit priorities among dates in preference sets |
| | 48 | * * NFR16.2: handling of explicit dependencies between meeting date and meeting location |
| | 49 | * * NFR16.3: participation through delegation - a participant may ask another person to represent him/her at the meeting |
| | 50 | * * NFR16.4: variations in the date formats, address formats, interface language, etc |
| | 51 | * * NFR16.5: partial re-use in other contexts (to help establish course schedule) |
