Topic: Walkthrough,Inspection

Message

   What is walkthrough?

A 'walkthrough' is an informal meeting for evaluation or
informational purposes.  Little or no preparation is usually
required.

What is Inspection?

An inspection is more formalized than a 'walkthrough', typically
with 3-8 people including a moderator, reader, and a recorder to 
take notes. The subject of the inspection is typically a document 
such as a requirements spec or a test plan, and the purpose is to 
find problems and see what's missing, not to fix anything.  Attendees 
should prepare for this type of meeting by reading thru the document; 
most problems will be found during this preparation. The result of the 
inspection meeting should be a written report. Thorough preparation for 
inspections is difficult, painstaking work, but is one of the most cost 
effective methods of ensuring quality.  Employees who are most skilled 
at inspections are like the 'eldest brother' in the parable in 
 'Why is it often hard for organizations 
to get serious about quality assurance?'.
Their skill may have low visibility but they are extremely valuable
to any software development organization, since bug prevention is
far more cost-effective than bug detection.

Author	Message
vidhya Senior Member Joined: 24Mar2007 Online Status: Offline Posts: 114	Topic: Walkthrough,Inspection Posted: 26Mar2007 at 6:01am
	What is walkthrough? A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required. What is Inspection? An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading thru the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost effective methods of ensuring quality. Employees who are most skilled at inspections are like the 'eldest brother' in the parable in 'Why is it often hard for organizations to get serious about quality assurance?'. Their skill may have low visibility but they are extremely valuable to any software development organization, since bug prevention is far more cost-effective than bug detection.
	MBA Examination papers Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged

sairevathi Newbie Joined: 25Sep2008 Location: India Online Status: Offline Posts: 34	Posted: 28Sep2008 at 10:21pm
	walkthrough is informal meeting means without informing check the roles &responsibilites without any intimation Inspection is formal meeting means informing to check the roles &responsibilites with an intimation
	IP Logged

venkataramana Newbie Joined: 16Oct2008 Online Status: Offline Posts: 1	Posted: 22Oct2008 at 5:09am
	vidhya, Which one will be more help full, inspection or walkthrough rgds Venkat
	IP Logged

tossy Groupie Joined: 20Aug2008 Online Status: Offline Posts: 99	Posted: 24Oct2008 at 11:13pm
	Walkthrough: is a formal review: we can discuss/raise the issue at peer level say-- fellow devoloper/tester. Also walkthrough does not have minutes of the meet. can happen at any time and conclude just like that, no schedule as such. But inspection is a formal approach to the requirements/schedule. Atleast 3 - 8 people will sit in the meeting 1-reader 2-writer and 3-moderator + concerned.. Inspection will have a proper schedule which will be intimated via email to the concerned devoloper/tester. It contains a track of the situation, what for we met here?? why it is delayed? / why the resource is free?? how we can complete it? so that the schedule can be successful. So definitely the PL/PM will be part of it, or any Sr.Engg will be part of it on be-half. It contains proof reading. One will read through his work done / proposal for the upcoming task( code/testcase/design) what ever he has done in the time(depends on the frequency of Inspection company to company it may change) writer will note down the issues discussed/ to be done. Moderator(s) have to comment out his/her opinion. That's how inspection happens. As it is purely systematic and well maintained, tracking of the effort done by the individual and the approach can be functionally will not be an issue for the PM.

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Beginners @ OneStopTesting