Reviewing the Specification

The review process follows an iterative cycle until all problems have been resolved. That is, when errors are discovered, their corrections are reviewed and, if necessary, the specification looked at again to ensure none of the corrections introduced new problems. This iteration continues until you stop finding errors. We recommend you keep a record of discarded requirements to prevent their accidental reintroduction and to monitor which kinds of requirements are being rejected. This kind of documentation might prevent the reappearance of the unwanted requirements in future projects. The types of errors you discover in this review suggest what you need to do to improve your requirements process.

A seriously flawed specification or indications that the costs and the risks outweigh the benefits are almost always indications that you need to consider project euthanasia.

This review gives you an ideal opportunity to reassess your earlier decision on whether to go ahead with the project. A seriously flawed specification or indications that the costs and the risks outweigh the benefits are almost always indications that you need to consider project euthanasia.