Formal Technical Reviews (Peer Reviews)

Formal Technical  Reviews (Peer  Reviews):

•  The focus of FTR is on a work product that is requirement specification, a detailed component design, a source code listing for a component.
• The individual who has developed the work product i.e, the producer informs the project leader that the work product is complete and that a review is required.
• The project leader contacts a review leader, who evaluates the product for readiness, generates a copy of product material and distributes them to two or three review members for advance preparation.
• Each reviewer is expected to spend between one and two hours reviewing the product, making notes 
• The review leader also reviews the product and establish an agenda for the review meeting
• The review meeting is attended by the review leader, all reviewers and the producer. One of the reviewers acts as a recorder,who notes down all important points discussed in the meeting.
• The meeting(FTR) is started by introducing the agenda of the meeting and then the producer introduces his product. Then the producer “walkthrough” the product, the reviewers raise issues which they have prepared in advance.If errors are found the recorder notes down

Objectives:

• Useful to uncover error in logic, function and implementation for any representation of the software.
• The purpose of FTR is to verify that the software meets specified requirements.
• To ensure that software is represented according to predefined standards.
• It helps to review the uniformity in software that is developed in a uniform manner.
• To make the project more manageable.