Reject Requirement
Rejecting
a requirement requires the reviewer to clearly indicate the reason the
requirement is being rejected. A requirement that has errors can still
be accepted pending correction of the identified errors. By contrast, a
rejected requirement is altogether incorrect.
Since determining whether or
not a requirement should be corrected or removed altogether is a
subjective process, rationale for removal will be necessary. In
addition to rationale for removing the requirement from the SRS, the
reviewer should note any requirements that might be affected by removal
of this requirement due to dependency relationships or derivation
relationships. If the requirement is a user requirement that came
directly from the customer organization, then it is recommended that
the development group seek concurrence from the customer organization
before officially removing the requirement.