Download Software Requirements Specification
Transcript
Option 2: Rephrase as "Once a MI specifies a time for the meeting to take place, available rooms will be displayed in the Locations menu. After the MI clicks an available location, the MI can click "save" to schedule the meeting. If no physical rooms appear in the Locations menu, then all the meeting rooms are in use at the MI's specified time and the MI must choose another time for the meeting. A ‘virtual room’ option will always be available in the Locations menu if the MI does not require a physical meeting room.” Solution: Option 2 Rationale: It is more efficient to allow the MI to choose from a list of available meeting rooms rather than click on each one until the meeting is accepted by the WMS. Reference: None 2.3.14 Issue Statements [NFR14.1, NFR24.1, NFR28.1] [NFR14.1] "etc.;" [NFR24.1] "etc.;" [NFR28.1] "etc." Problem: Ambiguity: "Etc." is not an actual requirement and leaves the document open to future interpretation. Option 1: Replace "etc." with a specific requirement or requirements. Option 2: Remove "etc." from the document. Solution: Option 2 Rationale: The requirements of [NFR10.1], [NFR21.1], and [NFR25.1] are already stated and do not need further examples. Reference: None 2.3.15 Issue Statement [NFR15.1] "The system should provide an appropriate level of performance" Problem: The word "should" makes following the requirement optional and it is unclear what "appropriate" means in this context. Option 1: Remove the statement from the document. Option 2: Cleary define the "appropriate level of performance". Ensure it is feasible and measurable. Solution: Option 1 Rationale: The statement is not a measurable requirement. Reference: None 2.3.16 Issue Statement [NFR16.1] "the elapsed time between the submission of a meeting request and the determination of the corresponding date/location should be minimal" Problem: Ambiguity: "Minimal" is not a measurable amount of time and the word "should" makes following the requirement optional. Option 1: Rephrase "The time from when the Meeting Initiator schedules a meeting to the time when the meeting is visible on the PMA's calender shall be no more than three seconds." Option 2: The time from when the Meeting Initiator submits a meeting to the time when the system schedules the meeting will be based on how long it takes participants to respond to the initial request. Set a minimum window of time (24 hours) and allow scheduling even if participants haven't responded. 27