Advantages and Objectives of Walkthrough

Following are some of the objectives of the walkthrough.

• To detect defects in developed software products.
• To fully understand and learn the development of software products.
• To properly explain and discuss the information present in the document.
• To verify the validity of the proposed system.
• To give suggestions and report them appropriately with new solutions and ideas.
• To provide an early “proof of concept”.

Prerequisite:

• What is software engineering?
• What is the difference between an Inspection and Walkthrough?
   

The walkthrough is a review meeting process but it is different from the  Inspection, as it does not involve any formal process i.e. it is a nonformal process. Basically, the walkthrough [review meeting process] is started by the Author of the code.

In the walkthrough, the code or document is read by the author, and others who are present in the meeting can note down the important points or can write notes on the defects and can give suggestions about them. The walkthrough is an informal way of testing, no formal authority is been involved in this testing.

As there is an informal way of testing involved so there is no need for a moderator while performing a walkthrough. We can call a walkthrough an open-ended discussion, it does not focus on the documentation. Defect tracking is one of the challenging tasks in the walkthrough.