Software Verification & Validation (V&V) Resources
Table of Contents
V&V Theory
(No resources posted yet)
Test Planning
& Design
(No resources posted yet)
Peer Reviews & Inspections
- Why Should Your Team Conduct Peer Reviews?
- Informal vs. Formal Peer Reviews
- Types of Peer Reviews
- Risk-Based Peer Reviews
Test Execution
(No resources posted yet)
The Westfall Team Posts Software Verification & Validation Resources.
These resources are free to anyone who wants to read or download them. Subscribe to the Software Excellence Academy be notified when new resources are added.
Peer Reviews & Inspections
Pairing Defined
by Linda Westfall
Pairing, also called pair programing, is a development technique where two people collaborate together to create or modify a single software work product. Watch this short video to learn more.
Why Should Your Team Conduct Peer Reviews?
by Linda Westfall
What is a Peer Review?
The IEEE/ISO/IEC Systems and Software Engineering Vocabulary defines a review as “a process or meeting during which a work product, or set of work products, is presented to project personnel, managers, users, customers, or other interested parties for comment or approval.” [IEEE/ISO/IEC 2017]
A peer review is a special type of technical review where one or more of the Author’s peers evaluate a work product to identify defects, obtain a confidence level that the product meets its requirements, and/or identify opportunities to improve that work product. The Author of a work product is the person that either originally produced that work product or the person who is currently responsible for maintaining that work product.
Informal vs. Formal Peer Reviews
by Linda Westfall
What is a Peer Review?
Peer reviews can vary greatly in their level of formality. At the most informal end of the peer review spectrum, a software practitioner can ask a colleague to, “Please take a look at this for me.” These types of informal peer reviews are performed all of the time. It is just good practice to get a second pair of eyes on a work product when the practitioner is having problems or needs a second opinion. As illustrated in the figure above, these informal reviews are done ad hoc with no formal process, no preparation, and no quality records or metrics. Defects are usually reported either verbally or as redlined mark-ups on a draft copy of the work product. Any rework that results from these informal peer reviews is up to the author’s discretion.
Types of Peer Reviews
by Linda Westfall
There are many different types of peer reviews called by many different names in the software industry. Peer reviews go by names such as inspections, team reviews, technical reviews, walk-throughs, pair reviews, pass-arounds, ad-hoc reviews, desk checks, and others. However, I have found that most of these can be classified into one of three major peer review types:
