what is review and walkthrough?

Question Posted / abhishek_comp

3 Answers
7067 Views
I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

what is review and walkthrough?..

Answer / vijay

Review: The need of this is to cover the missed
out/slippages in the document and this can be performed in
the various stages / phases. This is one of the best
practice to enhance the quality of the product. One of this
is Peer-to-peer review(BRS, SRS, FDS, DSD, Test plan / Test
Design, Test condition, Test script, Test data). This can
be done in the team (Eg. Testing team by doing peer to
peer). This should be done by the experience person like
(BA's, PM's, Senior developers, Test lead, Senior testers,
Test Analyst)

Walkthrough : It is step by step simulation of the
execution of a procedure, as when walking through code line
by line, with an imagined set of inputs. The term has been
extended to the review of material that is not procedural,
such as data descriptions, reference manuals,
specifications,

Is This Answer Correct ?

1 Yes

0 No

what is review and walkthrough?..

Answer / giridhar

review: " it will conducts between the team people or with
the other team.

Walkthrough: "here checking the processing of the
development, is it regards to requirements are not.

Is This Answer Correct ?

1 Yes

1 No

what is review and walkthrough?..

Answer / ravi v v

In a review , a work product is examined for defects by
individuals other than the person who produced it. A Work
Product is any important deliverable created during the
requirements, design, coding, or testing phase of software
development.

Research shows that reviews are one of the best ways to
ensure quality requirements, giving you as high as a 10 to
1 return on investment. Reviews help you to discover
defects and to ensure product compliance to specifications,
standards or regulations

Software Inspections are a disciplined engineering practice
for detecting and correcting defects in software artifacts,
and preventing their leakage into field operations.

Software Inspections are a reasoning activity performed by
practitioners playing the defined roles of Moderator,
Recorder, Reviewer, Reader, and Producer.

Moderator: Responsible for ensuring that the inspection
procedures are performed through out the entire inspection
process. The responsibilities include

Verifying the work products readiness for inspection

Verifying that the entry criteria is met

Assembling an effective inspection team

Keeping the inspection meeting on track

Verifying that the exist criteria is met

Recorder: The Recorder will document all defects that arise
from the inspection meeting. This documentation will
include where the defects was found. Additionally, every
defect is assigned a defect category and type.

Reviewer: All of the Inspection Team individuals are also
considered to play the Reviewer role, independent of other
roles assigned. The Inspector role is responsible for
analyzing and detecting defects within the work product.

Reader: The reader is responsible for leading the
Inspection Team through the inspection meeting by reading
aloud small logical units, paraphrasing where appropriate

Producer: The person who originally constructed the work
product. The individual that assumes the role of Producer
will be ultimately responsible for updating the work
product after the inspection.

In a Walkthrough, the producer describes the product and
asks for comments from the participants. These gatherings
generally serve to inform participants about the product
rather than correct it.

Is This Answer Correct ?

0 Yes

0 No

Post New Answer