A formal technical review (FTR) is a software quality control activity performed by software engineers (and others) The objectives of an FTR are: To uncover errors in function, logic, or implementation; for any representation of the software To verify that the software under review meets its requirements To ensure that the software has been represented according to predefined standards To achieve software that is developed in a uniform manner To make projects more manageable During the FTR, a reviewer (the recorder) actively records all issues that have been raised. These are summarized at the end of the review meeting, and a reviewed issues list is produced. In addition, a formal technical review summary report is completed. Steps in FTR The review meeting. Review reporting and record keeping. Review guidelines. Guideline for review may include following things Concentrate on work product only. That means review the product not the producers. Set an agenda of a review and maintain it. When certain issues are raised then debate or arguments should be limited. Reviews should not ultimately results in some hard feelings. Find out problem areas, but don’t attempt to solve every problem noted. Take written notes (it is for record purpose) Limit the number of participants and insists upon advance preparation. Develop a checklist for each product that is likely to be reviewed. Allocate resources and time schedule for FTRs in order to maintain time schedule. Conduct meaningful trainings for all reviewers in order to make reviews effective. Reviews earlier reviews which serve as the base for the current review being conducted.
