Thursday, December 30, 2010

FORMAL TECHNICAL REVIEWS


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;
And
 (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.

 

9 comments:

  1. great explanation

    ReplyDelete
  2. Can you please help me what are the types of FTR...??

    ReplyDelete
    Replies
    1. Type of FTR

      Formal reviews

      In a formal review, the author of the work product or one of the reviewers familiar with the work product introduces it to the rest of the reviewers. The flow of the review is driven by the presentation and issues raised by the reviewers.

      Walkthroughs

      Walkthroughs are usually used to examine source code as opposed to design and requirements documents. The participants do a step-by-step, line-by-line simulation of the code. The author of the code is usually present to answer participants' questions.

      Inspections

      In an inspection, a list of criteria the software must satisfy determines the flow of the review. While walkthroughs and formal reviews are generally biased toward error detection, inspections are often used to establish additional properties such as portability and adherence to standards. A reviewer may be supplied with a checklist of items, or he or she may only be informed of the desired property. Inspections are also used to check for particular errors that have been prevalent in the past.

      Delete
  3. explanation copied from R.Pressman

    ReplyDelete

  4. The FTR is 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. It is one of the secrets to develop the best quality control inspection software.

    ReplyDelete
  5. Some people argue that an FTR should assess programming style as well as correctness. Is this a good idea? Why?

    ReplyDelete