Changes between Version 12 and Version 13 of RequirementsPage

Timestamp:

09/06/2007 06:15:36 AM (17 years ago)

Author:

russell

Comment:

--

RequirementsPage

@@ -9 +9 @@
 
  * FR1: The SDMS system shall allow user(s) to login.
+    * FR1.1: system login shall be accomplished through a login screen
  * FR2: The SDMS system shall maintain user information security.
+    * FR2.1: un-authorized user shall not be allowed into the system
+    * FR2.2: authorized users shall not be allowed to access other user's information
  * FR3: The SDMS system shall maintain a user date exclusion set, those dates each user cannot attend a meeting.
+    * FR3.1: adding of dates to the exclusion set
+    * FR3.2: removal of dates from the exclusion set
+    * modificcation of dates in the exclusion set
  * FR4: The SDMS system shall maintain a user date preference set, those dated each user prefers to attend a meeting.
+    * FR4.1: adding of dates to the preference set
+    * FR4.2: removal of dates from the preference set
+    * FR4.3: modification of dates in the preference set
  * FR5: The SDMS system shall allow monitoring of the system.
  * FR6: The SDMS system shall plan meetings under the constraints expressed by participants (see domain theory).
- * FR7: The SDMS system shall allow replanning of meeting in support of changinf user constraints (modification of exclusion set, preference set and/or preferred location before a meeting date/location is proposed, take into account constrainsts after a meeting date/location has been proposed.) Need bounds on replanning.
- * FR9: The SDMS system shall support conflict resolution (according to conflict resolution policies stated by client.
+ * FR7: The SDMS system shall allow replanning of meetings in support of changing user constraints
+    * FR7.1: modification of exclusion set
+    * FR7.2: modification of preference set
+    * FR7.3: modification of preferred location before a meeting date/location is proposed
+    * FR7.4: take into account constrainsts after a meeting date/location has been proposed
+ * FR8: The SDMS shall allow the setting of bounds n replanning
+ * FR9: The SDMS system shall allow client specified conflict resolution
+    * according to policies entered by client(s)
  * FR10: The SDMS system shall allow the management of all interactions among participants required during the organization of the meeting:
- * * FR10.1: to communicate requests
- * * FR10.2: to get replies even from participants not reacting promptly
- * * FR10.3: to support the negotiation and conflict resolution processes
- * * FR10.4: to make participants aware of what's going on during the planning process
- * * FR10.5: to keep participants informed about schedules and their changes
- * * FR10.6: to make them confident about the reliability of the communications
-
-Complements:[[BR]]
-FR11: The SDMS system shall allow cancelling the meeting[[BR]]
-FR12: The SDMS system shall allow managing the info of all users such as passwords, email address and so forth[[BR]]
-FR13: The SDMS system shall do something if some meetings are over(make end marks, store the whole meeting info or delete it ,or whatever)[[BR]]
+    * FR10.1: to communicate requests
+    * FR10.2: to get replies even from participants not reacting promptly
+    * FR10.3: to support the negotiation and conflict resolution processes
+    * FR10.4: to make participants aware of what's going on during the planning process
+    * FR10.5: to keep participants informed about schedules and their changes
+    * FR10.6: to make them confident about the reliability of the communications
+  * FR11: The SDMS system shall allow cancelling the meeting
+  * FR12: The SDMS system shall allow managing the info of all users such as passwords, email address and so forth
+  * FR13: The SDMS system shall do handle the necessary house cleaning once meetings are over
+    * FR13.1: make end marks
+    * FR13.2: store meeting info or delete it
 
 == Non-Functional Requirements ==