 |
VOOZH | about |
|
VOOZH | about |
Inspection and walkthrough are methods of software review with distinct approaches. Inspection is formal, involving detailed group scrutiny to detect defects early, while walkthrough is informal, where an author presents work to peers for feedback. Inspection follows structured phases and roles, using checklists, ensuring thoroughness, while walkthroughs are flexible, focusing on discussion and feedback without predefined steps. Each method offers unique benefits in enhancing software quality through early detection and collaborative improvement processes.
Walkthrough is a method of conducting informal group/individual review. In a walkthrough, author describes and explain work product in a informal meeting to his peers or supervisor to get feedback. Here, validity of the proposed solution for work product is checked. It is cheaper to make changes when design is on paper than at time of conversion. Walkthrough is a static method of quality assurance. Walkthrough are informal meetings but with purpose.
An inspection is defined as formal, rigorous, in depth group review designed to identify problems as close to their point of origin as possible. Inspections improve reliability, availability, and maintainability of software product. Anything readable that is produced during the software development can be inspected. Inspections can be combined with structured, systematic testing to provide a powerful tool for creating defect-free programs. Inspection activity follows a specified process and participants play well-defined roles.
An inspection team consists of three to eight members who plays roles of moderator, author, reader, recorder and inspector.
For example: Designer can acts as inspector during code inspections while a quality assurance representative can act as standard enforcer.
| Aspect | Inspection | Walkthrough |
|---|---|---|
| Formality | It is formal. | It is informal. |
| Initiation | Initiated by project team. | Initiated by author. |
| Participant Composition | A group of relevant persons from different departments participate in the inspection. | Usually team members of the same project take participation in the walkthrough. Author himself acts walkthrough leader. |
| Use of Checklist | Checklist is used to find faults. | No checklist is used in the walkthrough. |
| Process Structure | Inspection processes includes overview, preparation, inspection, and rework and follow up. | Walkthrough process includes overview, little or no preparation, little or no preparation examination (actual walkthrough meeting), and rework and follow up. |
| Formalized Procedure | Formalized procedure in each step. | No formalized procedure in the steps. |
| Time Duration | Inspection takes longer time as list of items in checklist is tracked to completion. | Shorter time is spent on walkthrough as there is no formal checklist used to evaluate program. |
| Meeting Structure | Planned meeting with the fixed roles assigned to all the members involved. | Unplanned |
| Role of Reader | Reader reads product code. Everyone inspects it and comes up with detects. | Author reads product code and his teammate comes up with the defects or suggestions. |
| Role of Recorder | Recorder records the defects. | Author make a note of defects and suggestions offered by teammate. |
| Moderation | Moderator has a role that moderator making sure that the discussions proceed on the productive lines. | Informal, so there is no moderator. |
