| 10 | | * FR1: The SDMS system shall allow user(s) to login. |
| 11 | | * FR1.1: system login shall be accomplished through a login screen |
| 12 | | * FR2: The SDMS system shall maintain user information security. |
| 13 | | * FR2.1: un-authorized user shall not be allowed into the system |
| 14 | | * FR2.2: authorized users shall not be allowed to access other user's information |
| 15 | | * FR3: The SDMS system shall maintain a user date exclusion set, those dates each user cannot attend a meeting. |
| 16 | | * FR3.1: adding of dates to the exclusion set |
| 17 | | * FR3.2: removal of dates from the exclusion set |
| | 10 | * The SDMS system shall allow the creation of system administrators |
| | 11 | * The SDMS system shall allow the modification of system administrators |
| | 12 | * The SDMS system shall allow the deletion of system administrators |
| | 13 | * The SDMS system shall allow system administrators to login into the system |
| | 14 | |
| | 15 | * The SDMS system shall allow the creation of meeting initiators |
| | 16 | * The SDMS system shall allow the modification of meeting initiators |
| | 17 | * The SDMS system shall allow the deletion of meeting initiators |
| | 18 | * The SDMS system shall allow meeting initiators to login into the system |
| | 19 | |
| | 20 | * The SDMS system shall allow the creation of meeting participants |
| | 21 | * The SDMS system shall allow the modification of meeting participants |
| | 22 | * The SDMS system shall allow the deletion of meeting participants |
| | 23 | * The SDMS system shall allow meeting participants to login into the system |
| | 24 | |
| | 25 | * The SDMS system shall allow system administrators to set criteria on the number of failed attempts to login |
| | 26 | * The SDMS system shall allow the creation of client(initiator) criteria....(need to break down) |
| | 27 | * The SDMS system shall maintain user information security. |
| | 28 | * un-authorized user shall not be allowed into the system |
| | 29 | * authorized users shall not be allowed to access other user's information |
| | 30 | * The SDMS system shall maintain a user date exclusion set, those dates each user cannot attend a meeting. |
| | 31 | * adding of dates to the exclusion set |
| | 32 | * removal of dates from the exclusion set |
| 19 | | * FR4: The SDMS system shall maintain a user date preference set, those dated each user prefers to attend a meeting. |
| 20 | | * FR4.1: adding of dates to the preference set |
| 21 | | * FR4.2: removal of dates from the preference set |
| 22 | | * FR4.3: modification of dates in the preference set |
| 23 | | * FR5: The SDMS system shall allow monitoring of the system. |
| 24 | | * FR6: The SDMS system shall plan meetings under the constraints expressed by participants (see domain theory). |
| 25 | | * FR7: The SDMS system shall allow replanning of meetings in support of changing user constraints |
| 26 | | * FR7.1: modification of exclusion set |
| 27 | | * FR7.2: modification of preference set |
| 28 | | * FR7.3: modification of preferred location before a meeting date/location is proposed |
| 29 | | * FR7.4: take into account constrainsts after a meeting date/location has been proposed |
| 30 | | * FR8: The SDMS shall allow the setting of bounds n replanning |
| 31 | | * FR9: The SDMS system shall allow client specified conflict resolution |
| | 34 | * The SDMS system shall maintain a user date preference set, those dated each user prefers to attend a meeting. |
| | 35 | * adding of dates to the preference set |
| | 36 | * removal of dates from the preference set |
| | 37 | * modification of dates in the preference set |
| | 38 | * The SDMS system shall allow monitoring of the system. |
| | 39 | * The SDMS system shall plan meetings under the constraints expressed by participants (see domain theory). |
| | 40 | * The SDMS system shall allow replanning of meetings in support of changing user constraints |
| | 41 | * modification of exclusion set |
| | 42 | * modification of preference set |
| | 43 | * modification of preferred location before a meeting date/location is proposed |
| | 44 | * take into account constrainsts after a meeting date/location has been proposed |
| | 45 | * The SDMS shall allow the setting of bounds n replanning |
| | 46 | * The SDMS system shall allow client specified conflict resolution |
| 33 | | * FR10: The SDMS system shall allow the management of all interactions among participants required during the organization of the meeting: |
| 34 | | * FR10.1: to communicate requests |
| 35 | | * FR10.2: to get replies even from participants not reacting promptly |
| 36 | | * FR10.3: to support the negotiation and conflict resolution processes |
| 37 | | * FR10.4: to make participants aware of what's going on during the planning process |
| 38 | | * FR10.5: to keep participants informed about schedules and their changes |
| 39 | | * FR10.6: to make them confident about the reliability of the communications |
| 40 | | * FR11: The SDMS system shall allow cancelling the meeting |
| 41 | | * FR12: The SDMS system shall allow managing the info of all users such as passwords, email address and so forth |
| 42 | | * FR13: The SDMS system shall do handle the necessary house cleaning once meetings are over |
| 43 | | * FR13.1: make end marks |
| 44 | | * FR13.2: store meeting info or delete it |
| | 48 | * The SDMS system shall allow the management of all interactions among participants required during the organization of the meeting: |
| | 49 | * to communicate requests |
| | 50 | * to get replies even from participants not reacting promptly |
| | 51 | * to support the negotiation and conflict resolution processes |
| | 52 | * to make participants aware of what's going on during the planning process |
| | 53 | * to keep participants informed about schedules and their changes |
| | 54 | * to make them confident about the reliability of the communications |
| | 55 | * The SDMS system shall allow cancelling the meeting |
| | 56 | * The SDMS system shall allow managing the info of all users such as passwords, email address and so forth |
| | 57 | * The SDMS system shall do handle the necessary house cleaning once meetings are over |
| | 58 | * make end marks |
| | 59 | * store meeting info or delete it |
| 49 | | * NFR1: The SDMS system shall be functionally intuitive |
| 50 | | * NFR2: The SDMS system shall be easily used by non-experts |
| 51 | | * NFR3: The SDMS system shall be accurately monitored (IE: held in virtual place, nomadicity) |
| 52 | | * NFR4: The SDMS system shall replan a meeting as dynamically and flexible as possible |
| 53 | | * NFR5: The SDMS system shall keep the amount of interaction among participants as minimal as possible (number and length of messages) |
| 54 | | * NFR6: The SDMS system shall considerably reduce the amount of overhead usually incurred in meeting organization (potential distributed attendees) |
| 55 | | * NFR7: The SDMS system shall reflect, as closely as possible, the way meetings re typically managed |
| 56 | | * NFR9: The SDMS system shall alert attendees as conviently and early as possible of the date and location of the meeting |
| 57 | | * NFR10: The SDMS system shall accomodate decentralized requests as far as possible (any authorized user can request a meeting independently of their whereabouts) |
| 58 | | * 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) |
| 59 | | * NFR12: The SDMS system shall provide an appropriate level of performance |
| 60 | | * * NFR12.1: elapsed time between submission of a meeting request and determination of corresponding date/location shall be minimal |
| 61 | | * * NFR12.2: elapsed time between determination of meeting date/location and communication of meeting information to all participants shall be minimal |
| 62 | | * * 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 |
| 63 | | * NFR13: The SDMS system shall enforce all privacy rules |
| 64 | | * * NFR13.1: non-priviledged particiapnts shall not be allowed to know the constraints stated by other participants |
| 65 | | * NFR14: The SDMS system shall allow customization to professional and private meetings |
| 66 | | * * NFR14.1: different restrictions on the time periods that may be allocated (meeting hours during office hours, private activites during leisure time) |
| 67 | | * NFR15: The SDMS system shall be flexible enough to accomodate evolving data |
| 68 | | * * NFR15.1: varying sets of concerned participants |
| 69 | | * * NFR15.2: address to which participant may be reached may vary |
| 70 | | * NFR16: The SDMS system shall be easily extensible |
| 71 | | * * NFR16.1: handling of explicit priorities among dates in preference sets |
| 72 | | * * NFR16.2: handling of explicit dependencies between meeting date and meeting location |
| 73 | | * * NFR16.3: participation through delegation - a participant may ask another person to represent him/her at the meeting |
| 74 | | * * NFR16.4: variations in the date formats, address formats, interface language, etc |
| 75 | | * * NFR16.5: partial re-use in other contexts (to help establish course schedule) |
| | 64 | * The SDMS system shall be functionally intuitive |
| | 65 | * The SDMS system shall be easily used by non-experts |
| | 66 | * The SDMS system shall be accurately monitored (IE: held in virtual place, nomadicity) |
| | 67 | * The SDMS system shall replan a meeting as dynamically and flexible as possible |
| | 68 | * The SDMS system shall keep the amount of interaction among participants as minimal as possible (number and length of messages) |
| | 69 | * The SDMS system shall considerably reduce the amount of overhead usually incurred in meeting organization (potential distributed attendees) |
| | 70 | * The SDMS system shall reflect, as closely as possible, the way meetings re typically managed |
| | 71 | * The SDMS system shall alert attendees as conviently and early as possible of the date and location of the meeting |
| | 72 | * The SDMS system shall accomodate decentralized requests as far as possible (any authorized user can request a meeting independently of their whereabouts) |
| | 73 | * 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) |
| | 74 | * The SDMS system shall provide an appropriate level of performance |
| | 75 | * elapsed time between submission of a meeting request and determination of corresponding date/location shall be minimal |
| | 76 | * elapsed time between determination of meeting date/location and communication of meeting information to all participants shall be minimal |
| | 77 | * 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 |
| | 78 | * The SDMS system shall enforce all privacy rules |
| | 79 | * non-priviledged particiapnts shall not be allowed to know the constraints stated by other participants |
| | 80 | * The SDMS system shall allow customization to professional and private meetings |
| | 81 | * different restrictions on the time periods that may be allocated (meeting hours during office hours, private activites during leisure time) |
| | 82 | * The SDMS system shall be flexible enough to accomodate evolving data |
| | 83 | * varying sets of concerned participants |
| | 84 | * address to which participant may be reached may vary |
| | 85 | * The SDMS system shall be easily extensible |
| | 86 | * handling of explicit priorities among dates in preference sets |
| | 87 | * handling of explicit dependencies between meeting date and meeting location |
| | 88 | * participation through delegation - a participant may ask another person to represent him/her at the meeting |
| | 89 | * variations in the date formats, address formats, interface language, etc |
| | 90 | * partial re-use in other contexts (to help establish course schedule) |
