Difference between Inspections and Walkthroughs - Testing

Difference between Inspections and Walkthroughs.


InspectionWalkthrough
FormalInformal
Initiated by the project teamInitiated by the author
Planned meeting with fixed roles assigned to all the members involvedUnplanned.
Reader reads the product code. Everyone inspects it and comes up with defects.Author reads the product code and his team mate comes up with defects or suggestions
Recorder records the defectsAuthor makes a note of defects and suggestions offered by team mate
Moderator has a role in making sure that the discussions proceed on the productive linesInformal, so there is no moderator


Inspection: is used to verify the compliance of the product with specified standards and requirements. It is done by examining, comparing the product with the designs, code, artefacts and any other documentation available. It needs proper planning and overviews are done on the planning to ensure that inspections are held properly. Lots of preparations are needed, meetings are held to do inspections and then on the basis of the feedback of the inspection, rework is done.
Inspection is deserving method with careful consideration of an organization, which concerns about the quality of the product. The process is being done by the quality control department.

Inspection is a disciplined practice for correcting defects in software artifacts.

Walkthroughs: Author presents their developed artifact to an audience of peers. Peers question and comment on the artifact to identify as many defects as possible. It involves no prior preparation by the audience. Usually involves minimal documentation of either the process or any arising issues. Defect tracking in walkthroughs is inconsistent.

A walk through is an evaluation process which is an informal meeting, which does not require preparation.

The product is described by the produced and queries for the comments of participants. The results are the information to the participants about the product instead of correcting it.
What is the different test plan documents prepared during a project?
Testing - The test plan documents that are prepared during a project are Problem reporting documents, Change Requests documents, Deliverable documents, Test incident documents........
Explain the Phased Waterfall Model - Testing
Testing - Unlike the big bang waterfall model, the phased model is suitable if the work can be grouped into separate units and delivered in steps rather than everything once and together, by different teams.........
Explain the Iterative Model - Testing
Testing - Iterative Model enables the accessing to previous phases and the changes are made accordingly. The final output of the product is revived at the end of the SDLC........
Post your comment
Discussion Board
Software Quality Assurrance
Thank you so much..
info is very helpful for me. :)
Bilal 10-23-2016