Summary

3.4 Summary

Reviews take on many forms. Each review has a specific purpose, objective, audience, and cast of participants.

Informal, in-process peer reviews generally occur during the execution of each SDLC phase. They concentrate on single products or even small parts of single products. It is the intention of in-process reviews to detect defects as quickly as possible after their insertion into the product.

Formal, phase-end reviews usually occur at the ends of the SDLC phases and establish the baselines for work in succeeding phases. They also serve as points in the development when the decision to continue (go) or terminate (no go) a project can be made. The phase-end reviews are much broader in scope than in-process reviews. They cover the entire family of products to be prepared in each major SDLC phase, as well as the various documented plans for the project.

Formal project completion audits include the FA and PA. These assess readiness to ship or deliver the software. The PIR assesses the success of the software in meeting its goals and objectives once the software is in place and has been used for a time.

Documentation reviews and audits, both formal and informal, are applicable to each of the software documents. The most basic of the reviews is the peer walk-through. Another basic document review is the format review. This can be either formal or informal. Requirements reviews are intended to show that the problem to be solved is completely spelled out. Design reviews verify that the evolving design is both correct and traceable back to the approved requirements. Test documentation is reviewed to assure that the test program will find defects and will test the software against its requirements. The reviews of the user documentation are meant to determine that the documentation meets the criteria that have been discussed.

Other documents are often produced during the SLC and must be reviewed as they are prepared. Reviews of all of these documents concentrate on the basic criteria and on the completeness of the discussions of the specific areas covered.

Design and code reviews held during the course of the various phases are usually in the form of walk-throughs and inspections. These generally informal reviews are held to get an early start on eliminating defects in the products being examined.

Test reviews are much the same as code reviews, covering the test program products rather than the software products.

Implementation reviews are conducted just prior to implementing the software system into full use.

Reviews take place throughout the SLC and verify that the products of each phase are correct with respect to its phase inputs and activities.



Practical Guide to Software Quality Management
Practical Guide to Software Quality Management (Artech House Computing Library)
ISBN: 1580535275
EAN: 2147483647
Year: 2002
Pages: 137
Authors: John W. Horch

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net