x Reviews are conducted by stakeholders with
the intent of finding errors, conflicts, incorrect
assumptions, ambiguities, and missing
requirements. Formal inspections and reviews
have been shown to be effective in removing
errors early in the process and thereby reducing
the cost and effort that would have been involved
fixing downstream problems [37,38]. It is
important to have customer and user
representatives as well as developers involved in
the review process so that all perspectives can be
considered. Reviews are useful at all major
milestones in the delivery of the requirements
documents, including completion of the system
definition document, system requirements
document, SRS, and prior to all major baselines.
All reviews should result in a list of identified
problems and a set of agreed upon actions. As
reviews require significant time commitments
they can be costly to conduct, and it can be
beneficial to perform pre-review activities to
identify and handle obvious errors in advance.
Furthermore review documents should be
distributed and read in advance of a meeting so
that all members can arrive well prepared.