A formal technical review is a software quality assurance activity performed by software
engineers (and others). The objectives of the FTR are
(1) to uncover errors in function, logic, or implementation for any representation of the software;
(2) to verify that the software under review meets its requirements;
(3) to ensure that the software has been represented according to predefined standards; (4) to achieve software that is developed in a uniform manner;
(5) to make projects more manageable.
In addition, the FTR serves as a training ground, enabling junior engineers to observe different approaches to software analysis, design, and implementation. The FTR also serves
to promote backup and continuity because a number of people become familiar with
parts of the software that they may not have otherwise seen.
The FTR is actually a class of reviews that includes walkthroughs, inspections,
round-robin reviews and other small group technical assessments of software. Each
FTR is conducted as a meeting and will be successful only if it is properly planned,
controlled, and attended. In the sections that follow, guidelines similar to those for a
walkthrough are presented as a representative formal technical review.