A formal review of the Software Requirements Specification (SRS) should be conducted prior to a major investment in the design or code. All of the many parties that have a stake in the success of a product should be involved in the review: users, marketing personnel, developers, testers, and so on. Everyone should be contributing to the correctness and completeness of the SRS.
Barry Boehm provides some advice on how to go about reviewing a SRS. In short, you want to determine if it is:
- complete
- consistent
- feasible
- testable
Related software development principles that can help with the SRS:
Reference:
Boehm, B., "Verifying and Validating Software Requirements and Design Specifications," IEEE Software, January 1984.
