Deep Structured Walk-Through
Deep Structured Walk-Through
A structured walkthrough, a static testing technique performed in an organized manner between a group of peers to review and discuss the technical aspects of the software development process. The main objective in a structured walkthrough is to find defects in order to improve the quality of the product.
Structured walkthroughs are usually NOT used for technical discussions or to discuss the solutions for the issues found. As explained, the aim is to detect errors and not to correct errors. When the walkthrough is finished, the author of the output is responsible for fixing the issues.There, the various the participants in Structured Walkthrough are mentioned below:
Author
The author of the work product is responsible for requesting the walkthrough when a meaningful portion of the product has been developed and is free of casual errors or defects. The author attends the walkthrough as an observer and answers the reviewer’s general questions.
Presenter
They usually develop the agenda for the walkthrough and present the work product that is being reviewed. The presenter should be familiar with the work product and should be a member of the project team.
Moderator
The main responsibility of the moderator is to facilitate the walkthrough session and ensure that the walkthrough agenda is followed. Moderators also encourage the participation of all reviewers. Moreover, the moderator can also be the scribe.
Reviewers
Evaluate the work product to determine if it is technically accurate. The reviewers also assess whether the project guidelines or standards are being followed, the project requirements are met, and whether the product is properly prepared.
Scribe
The scribe takes notes during the walkthrough. Their responsibility is to record the errors that are identified and any other technical comments, suggestions, and unresolved questions. Also, a scribe cannot be a reviewer.
