Study guide

3.2 Design Review & Verification

Certified Quality Engineer CQE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Management and Leadership

1.1 Quality Philosophies & Foundations 1.2 Leadership & Organizational Systems 1.3 ASQ Code of Ethics & Professional Standards 1.4 Strategic Planning & Deployment 1.5 Management Infrastructure & Project Management 1.6 Quality Information Systems & Communication 1.7 Financial & Cost of Quality

2 Chapter 2: The Quality System

2.1 Quality Management System Elements & Standards 2.2 Quality Documentation Architecture 2.3 Quality Auditing Principles & Types 2.4 Audit Planning, Execution & Reporting 2.5 Corrective Action & Preventive Action Systems 2.6 Supplier Quality Management 2.7 Customer Relations & Customer Value 2.8 Quality Training Program Design & Effectiveness

3 Chapter 3: Product, Process, and Service Design

3.1 Design Input & Requirements 3.2 Design Review & Verification 3.3 Failure Mode and Effects Analysis 3.4 Design of Experiments Foundations 3.5 Robust Design & Taguchi Methods 3.6 Reliability & Maintainability Concepts 3.7 Reliability Modeling & System Evaluation 3.8 Technical Drawings, Specifications & GD&T

4 Chapter 4: Product and Process Control

4.1 Statistical Process Control Principles 4.2 Variable Control Charts 4.3 Attribute Control Charts 4.4 Process Capability & Performance Analysis 4.5 Acceptance Sampling Plans & Standards 4.6 Metrology, Calibration & Measurement Uncertainty 4.7 Measurement System Analysis (MSA) 4.8 Material Control, Traceability & MRB

5 Chapter 5: Continuous Improvement

5.1 Continuous Improvement Methodologies 5.2 Classic Quality Tools 5.3 Management & Planning Tools 5.4 Lean Tools & Waste Elimination 5.5 Problem-Solving Methodologies & Root Cause Analysis 5.6 Risk Management & Assessment 5.7 Change Management & Team Facilitation

6 Chapter 6: Quantitative Methods and Tools

6.1 Descriptive Statistics & Data Summarization 6.2 Probability Concepts & Distributions 6.3 Sampling Distributions & Central Limit Theorem 6.4 Point & Interval Estimation 6.5 Hypothesis Testing Fundamentals 6.6 Specific Statistical Tests 6.7 Regression & Correlation Analysis

7 Chapter 7: Risk Management & Advanced Quality Engineering

7.1 Risk Identification & Hazard Analysis 7.2 Quantitative Risk Analysis & Modeling 7.3 Risk Mitigation & Control Planning 7.4 Special Process Control & Advanced SPC 7.5 Advanced Statistical Design & Analysis 7.6 Computer Applications & Quality Engineering Software

3.2 Design Review & Verification

Key Takeaways Explain This Topic AI

Design Verification answers 'Did we design the product right?' by evaluating outputs against quantitative technical design inputs through testing, inspection, calculations, and alternative design analysis.

Design Validation answers 'Did we design the right product?' by proving the final product fulfills specified user needs and intended uses under actual or simulated operational end-use conditions.

The Phase Gate Process imposes formal review gates (e.g., Concept, Detailed Design, Pilot Build, Launch) between project phases, preventing costly downstream revisions by requiring strict milestone sign-offs.

Design review stages (Conceptual, Preliminary/PDR, Final/Critical/CDR, Post-Implementation) require multi-disciplinary participation, documented action item logs, and objective evidence to confirm readiness.

Last updated: July 2026

Loading diagram... Design Controls Lifecycle V-Model

3.2 Design Review & Verification

Quality engineering during product development relies on structured evaluation mechanisms to prevent design flaws from reaching production. Regulated industries (such as medical devices under FDA 21 CFR 820.30 and ISO 13485, or aerospace under AS9100) enforce strict design controls. Central to design governance are Phase Gate Processes , Formal Design Reviews , Design Verification , and Design Validation .

1. The Phase Gate Development Process

The Phase Gate Process (also called a Stage-Gate framework) divides product development into discrete, sequential stages separated by formal evaluation checkpoints called Gates . +---------+ +--------+ +---------+ +--------+ +---------+ +--------+ +------------+

  • | Stage 1 |--> | Gate 1 |--> | Stage 2 |--> | Gate 2 |--> | Stage 3 |--> | Gate 3 |--> | Stage 4 |
  • | Concept | | Review | | Design | | Review | | Pilot | | Review | | Production |
  • +---------+ +--------+ +---------+ +--------+ +---------+ +--------+ +------------+

At each gate, a cross-functional governance board evaluates project deliverables against predefined exit criteria. The gate review yields one of four decisions:

Go: Project meets all criteria and proceeds to the next phase.

Kill: Project is canceled due to technical failure, excessive cost, or market unfeasibility.

Hold: Project is paused pending external factors or resource availability.

Recycle / Redo: Project remains in the current stage until specific action items or missing criteria are completed.

2. Stages of Formal Design Review

A Design Review is a documented, comprehensive, and systematic examination of a design to evaluate its capability to meet requirements and identify potential problems. Formal design reviews occur at critical milestones:

Design Review Stage Primary Focus Key Deliverables & Entrance Criteria

Conceptual Design Review Architectural feasibility, concept trade-offs, initial VOC alignment Product concept proposals, high-level feasibility analysis, preliminary cost models

Preliminary Design Review (PDR) Subsystem architectures, schematic completeness, risk assessments System specs, preliminary DFMEA, draft CAD models, initial test plans

Critical / Final Design Review (CDR) Final design freeze, detailed drawings, tolerance stack-ups, manufacturing readiness Released engineering drawings, completed DFMEA, prototype test data, tooling specs

Post-Implementation / Launch Review Initial production yield, field performance, lessons learned Production yield metrics, initial customer feedback, process capability studies ( C p k C_{pk} C p k ​ )

Multi-Disciplinary Team Composition

According to ISO 9001 and FDA regulations, design reviews MUST include representatives from all functions affected by the design stage being reviewed (Design, Quality, Manufacturing, Regulatory, Reliability, Field Support) AND at least one independent reviewer who is not directly responsible for the design stage under review.

3. Design Verification vs. Design Validation

One of the most frequently tested concepts on the ASQ CQE exam is the fundamental distinction between Verification and Validation . +-----------------------------------------------------------------------------------+

  • | DESIGN CONTROLS |
  • +-----------------------------------------+-----------------------------------------+
  • | DESIGN VERIFICATION | DESIGN VALIDATION |
  • +-----------------------------------------+-----------------------------------------+
  • | "Did we design the product RIGHT?" | "Did we design the RIGHT product?" |
  • | Evaluates: Output vs. Input Specs | Evaluates: Output vs. User Needs |
  • | Focus: Quantitative engineering specs | Focus: Qualitative user operating needs |
  • | Environment: Laboratory / Test bench | Environment: Actual / Simulated field |
  • | Units: Prototypes, subassemblies, code | Units: Production-equivalent units |
  • +-----------------------------------------+-----------------------------------------+
  • Detailed Comparison Table

Dimension Design Verification Design Validation

Core Question Did we design the product right? Did we design the right product?

Reference Baseline Design Inputs & Engineering Specifications User Needs, Intended Use, & Operational Environment

Primary Objective Prove outputs meet objective specifications Prove product functions effectively for the end user

Typical Methods Lab testing, dimensional inspection, FEA stress modeling, schematic analysis Clinical trials, simulated user trials, field trials, human factors testing

Test Units Engineering prototypes, breadboards, coupons Final production-equivalent units under actual operating conditions

4. Test Plan Development & Statistical Protocol

Quality engineers lead the development of Verification and Validation Test Plans . A robust test plan must specify:

Test Objective: Clear statement of the feature or spec being verified.

Acceptance Criteria: Unambiguous quantitative limits (e.g., "Tensile strength ≥ 450 MPa \ge 450 \text{ MPa} ≥ 450 MPa at 23 ∘ C 23^\circ\text{C} 2 3 ∘ C ").

Sample Size & Statistical Rationale: Sample sizes must be statistically justified based on risk, confidence levels ( 1 − α 1 - \alpha 1 − α ), and reliability targets ( 1 − β 1 - \beta 1 − β ).

Environmental Conditions: Operating temperature, humidity, vibration, and thermal shock parameters.

Traceability Matrix: Mapping every test protocol back to specific design input requirements.

Statistical Sample Size Rationale Example

For a verification test evaluating a continuous normal variable with unknown variance, the required sample size n n n to estimate a parameter within margin of error E E E at confidence level Z 1 − α / 2 Z_{1-\alpha/2} Z 1 − α /2 ​ is: n = ( Z 1 − α / 2 ⋅ s E ) 2 n = \left( \frac{Z_{1-\alpha/2} \cdot s}{E} \right)^2 n = ( E Z 1 − α /2 ​ ⋅ s ​ ) 2

Where s s s is the estimated standard deviation from historical prototype data. If test sample size is restricted, tolerance intervals or binomial success-run formulas ( n = ln ⁡ ( 1 − C ) ln ⁡ ( R ) n = \frac{\ln(1 - C)}{\ln(R)} n = l n ( R ) l n ( 1 − C ) ​ ) are used to prove reliability R R R at confidence C C C .

5. CQE Exam Tips & Key Pitfalls

Important

Remember the exact definitions for the exam: Verification compares Design Output to Design Input (engineering specifications). Validation compares Design Output to User Needs and Intended Use. Always ensure that validation testing is performed on production-equivalent units under actual or simulated operating environments.