---
title: "Formal Technique Review (FTR)"  
description: "FTR is a quality assurance activity performed by software engineers.It involves the analysis of final product (Software) by a group of technically ski"  
author: "Hemant Patel"  
published: 2017-01-24  
updated: 2018-03-17  
canonical: https://www.mindstick.com/blog/11284/formal-technique-review-ftr  
category: "products"  
tags: ["software development"]  
reading_time: 2 minutes  

---

# Formal Technique Review (FTR)

FTR is a [quality assurance](https://www.mindstick.com/forum/211/quality-assurance-in-testing) activity performed by [software engineers](https://yourviews.mindstick.com/view/88552/best-claude-prompts-for-software-engineers).It involves the analysis of final product (Software) by a group of technically skilled people following a specified and documented process.\

## The objective of FTR:-

**a.** To uncover errors in function logic or [implementation](https://www.mindstick.com/forum/33764/how-to-implementation-of-class-in-c-sharp) for any representation of software.FTR is an effective way.\

**b.** FTR is done to verify that the software being reviewed meets its requirements.

**c.** It ensures that software is represented according to relevant standards.

**d.** It helps to achieve uniform [software development](https://www.mindstick.com/services/erp-software-development) and make projects more manageable.FTR’s include walk-through code inspections and other small group software assessments.

**FTR include following stages.**

1. [Preparation](https://www.mindstick.com/articles/23237/spit-roast-preparation).\

2.Meeting.

3.Review [reporting](https://www.mindstick.com/articles/12967/portable-reporting-systems-and-mobile-device-management) and recording.

## Walk-through:-

Walk-through can be considered same an inspection without formal preparation. During the Walk-through meeting,the presentation or producer or [developer](https://www.mindstick.com/articles/157260/variation-between-web-designer-and-web-developer) introduces the material to all the participants in order to make them familiar. Even when they walk-through can help in finding potential bugs(error). They are used for knowledge sharing or [communication](https://www.mindstick.com/articles/126321/5-fails-and-fixes-of-the-office-communication) purpose.\

## Members in Walk-through:-

1.Representative of software.\

2.Client representative.

3.Senior [technical](https://www.mindstick.com/articles/12830/a-look-at-the-technical-features-and-specifications-of-type-c-hub) staff.

4.Representative of SQA group.

## Two methods in Walk-through are:-

a.Participant driven\

b. Document driven

## Code inspection:-

Code inspection is a type of review, which is more in details than the Walk-through. It includes the team, which are follows:-\

1. Moderator\

2. Designer

3. Implementor

4. Tester

## It also included five stages:-

**a. Overview:-** In this phase all the important documents such as SRS,Design,Documents,code,plans are reviewed.\

**b. Preparation:-**In this phase, we understand the documents in detail.

**c. Inspection:-** In this phase, we Walk-through the document and ensured that each item is converted and finally the [team leader](https://www.mindstick.com/forum/157606/how-can-you-effectively-handle-a-bulk-team-of-employees-under-you-as-a-team-leader) produces a report.

**d. Rework:-** Resolve all faults and problems.

**e. Followup:-** Moderator must insure that every issue has been resolved in a systematic way.

If there are a large number of faults then the code inspection team suggests redesigning.

---

Original Source: https://www.mindstick.com/blog/11284/formal-technique-review-ftr

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.