Changes between Version 4 and Version 5 of RequirementsPage

Timestamp:

09/04/2007 06:28:42 AM (17 years ago)

Author:

russell

Comment:

--

RequirementsPage

@@ -2 +2 @@
 
 == Functional Requirements ==
-(NOTE: Functional Requirements will begin with FR#:)
+(NOTE: Functional Requirements will begin with FR#:, these will need to be refined, broken down, and more added.)
 
- * FR1:
+ * FR1: The SDMS system shall allow user(s) to login.
+ * FR2: The SDMS system shall maintain user information security.
+ * FR3: The SDMS system shall maintain a user date exclusion set, those dates each user cannot attend a meeting.
+ * FR4: The SDMS system shall maintain a user date preference set, those dated each user prefers to attend a meeting.
+ * 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.
+ * 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.
 
 == Non-Functional Requirements ==
-(NOTE: Non-Functional Requirements will begin with NFR#:)
+(NOTE: Non-Functional Requirements will begin with NFR#:, these will need to be refined, broken down, and more added)
 
- * NFR1:
+ * NFR1: The SDMS system shall be functionally intuitive.
+ * NFR2: The SDMS system shall be easily used.
+ * NFR3: The SDMS system shall be