Explain and compare FTR and walkthrough

1.3kviews

written 7.3 years ago by

• modified 7.3 years ago

FTR:

A formal technical review is a software quality assurance activity performed by software engineers (and others). The objectives of the FTR are:

i. to uncover errors in function, logic, or implementation for any representation of the software;

ii. to verify that the software under review meets its requirements;

iii. to ensure that the software has been represented according to predefined standards;

iv. to achieve software that is developed in a uniform manner;

v. 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 walkthroughare presented as a representative formal technical review.

Walkthrough:

i. It is not a formal process/review

ii. It is led by the authors

iii. Author guide the participants through the document according to his or her thought process to achieve a common understanding and to gather feedback.

iv. Useful for the people if they are not from the software discipline, who are not used to or cannot easily understand ---software development process.

v. Is especially useful for higher level documents like requirement specification, etc.

The goals of a walkthrough:

i.To present the documents both within and outside the software discipline in order to gather the information regarding the topic under documentation.

ii. To explain or do the knowledge transfer and evaluate the contents of the document

iii. To achieve a common understanding and to gather feedback.

iv. To examine and discuss the validity of the proposed solutions

Difference between FTR and Walkthrough:

FTR	Walkthrough
A formal technical review is a software quality assurance activity performed by software engineers(and others).	It is led by the authors.Author,guide the participants through the document according to his or her,thought process to achieve a common understanding and to gather feedback.
In a review, a work product is examined for defects by individuals other than the person who produced it.	In a Walkthrough,the producer describes the product and asks for comments from the participants.
A Work Product is any important deliverable created during the requirements, design, coding, or testing phase of software development.	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.
It is often performed as a peer review without management participation.	A walkthrough is especially useful for,higher-level documents, such as requirement specifications and architectural,documents.
The FTR is actually a class of reviews that includes walkthroughs, inspections,round-robin reviews and other small group technical assessments of software	Walkthrough is a type of Formal Technical Review

ADD COMMENT EDIT