Software Quality Assurance

Course code ITEC-4122

Peer Reviews

By,
Ikhlaq.
Agenda
Understanding peer reviews.
Inspection process.
Walkthrough process.
Peer reviews
INSPECTION WALK -THROUGH
 Inspection
An inspection is a rigorous team review of a work
product by peers to detect the errors or anomalies ,in
addition to this it looks for deviations from standards
and specifications.
Confirms that the software product satisfies
Software requirement specifications.
Specified quality attributes.
Adherence to regulations, standards, guidelines, plan.
Inspection pre-conditions
A precise specification must be available.
Team members must be familiar with the organization
standards.
Syntactically correct code or other system
representations must be available.
 An error checklist should be prepared.
Management must accept that inspection will increase
costs early in the software process.
Management should not use inspections for staff
appraisal i.e. finding out who makes mistakes.
Inspection Check lists
 Data faults.
 Control faults.
 Input/output faults.
 Interface faults.
 Storage management faults.
 Exception management faults.
The inspection process
The inspection process
Planning:
Gather review package: work product, checklists,
references, and data sheets and choose team.
Overview:
Educate the inspection team on the work product being
inspected and discuss the review material, processes and
goals.
Preparation:
Involves Planning and scheduling.
Cont…

Inspection meeting:
 Identifies defects before work product is passed into the
next project stage.
Rework:
 Fixes identified defects and resolves any open issues
noted during the inspection procedure.
Follow-up:
Verifies that all defects and open issues have been
adequately fixed, resolved, and closed out.
The ETVX
 Walk-through

 A formal peer review in which usually a designer leads

members of the development team and other interested
parties to go through a software product. The participants
ask questions and make comments about possible errors,
violation of development standards, and other problems
and hence evaluate a quality software product.
 Major objectives:
 Find anomalies.
 Improve the software product.
 Consider alternative implementations.
 Evaluate performance to standards and specs.
 Walk-through roles
Moderator : Coordinates the inspection and leads the
discussion.
Author: Present the software product in the walk-
through.
Reviewer: Checks defects and further improvements.
Recorder: Records problems discussed.
Manager: Supervises the producer.
 Walk-through Outputs
 Recommendations made regarding each anomaly.
 List of actions, due-dates, responsible parties.
 Recommendations how to dispose of unresolved
anomalies.
Thank You