Please enable JavaScript.
Coggle requires JavaScript to display documents.
C6 : Walk through and Inspection (Structured Walk through (Attendees (4…
C6 : Walk through and Inspection
Why Review?
Reason
To avoid and reduce human errors
To find error from a different view point
Points out improvement in work products
Confirm those improvement that are not required
Achieve technical work of more uniform and of a more predictable quality
Act as a control mechanism to reduce errors
Formal Technical Review (FTR)
A
Verification
activities
A class of review
Walkthrough
Inspection
Review is performed on any work products
Work Product
Something that expends effort and has a role in the execution of software projects
Structured Walk through
A review technique
Objective
To ensure high quality work product
To find bugs, misinterpretation, inconsistencies and ambiguities
Anything that is complex or difficult to modify
Deviation from standards
Definitions
A formalization of free discussion
A peer group review
An in-depth technical reviews
A static QA method
An informal meeting but with purposes
Attendees
WP author
Member of QA team
Maintenance expert
Technical secretry
Experienced programmer
4 people recommended
If more time will be wasted on different of opinion but will discover more errors
Inspections
Formal evalution technique
Goals
Requirement, design or code are examined in details by a people other than the author
To detect faults, violation of development standards and other problems
Method
Checklist
View Point
Product Concentration
Roles and Responsibility
Producer (Author)
Responsibilities
Prepared for the inspection
Be objective, focus on issues not on people
Concentrate on problems and offer suggestion
Support moderator
Roles
Focus on technical issues and review
Reviewer (Inspector)
Roles
The one who reviewed is aim to
Responsibilities
Prepare review materials
Support moderator to make meeting arrangement
Resolve all identified issues
Be objective, avoid becoming defensive
Recorder (Scribe)
Responsibilities
Produce final inspection reports
Aware of subject matter being discuss
Roles
Record any required data and all issues
Moderator (Inspection Leader)
Responsibilities
Conduct inspection in an orderly and efficient manner
Communicate inspection result to interested parties
Ensure entry criteria for inspection are met
Roles
Ensure participant interact constructively to produce proper results
Making Review and Inspection Effective
Watts Humphrey
Opportunity to look at entire WP in one go
Make use of combined knowledge and group expertise
Inspection team usually have broader knowledge than author
Take advantage of different view point
Will help to see overlooked problems as you are explaining to others
Improve odd of finding problems
Need to desk check first to remove obvious error because it is distracting
Benefit of Review
Developers
Less time spent performing rework
Increase programming productivity
Learn better technique from other developers
Project Manager
Shortened product development life cycle time
Increase chance of shipping the product on schedule
Improve team work and development effectiveness
QA/QCM
Able to judge test ability of product under development
Shortened system testing life cycle time
Able to use review data when making release decision
Requirement Analyst
Earlier correction of missing and erroneous requirement
Fewer infeasible and un-testable requirement due to input during review
Test Engineer
Ability to focus on finding subtle defect because product is of high initial quality
Fewer defect that block continued testing
Improve test design and test case