Home Knowledge Base Coverage-Driven Verification (CDV)

Coverage-Driven Verification (CDV) is the systematic approach to measuring and closing verification completeness using quantitative coverage metrics — ensuring that all critical design scenarios, corner cases, and functional states have been exercised before tapeout, replacing the ad-hoc "run more tests and hope" methodology with data-driven verification management.

Types of Coverage

Code Coverage (automatic, tool-measured):

Functional Coverage (user-defined, intent-specific):

CDV Workflow

1. Coverage Plan: Document lists all scenarios to verify (derived from spec). 2. Covergroup Implementation: Translate plan into SystemVerilog covergroups. 3. Constrained Random Simulation: UVM testbench generates random-but-legal stimulus. 4. Coverage Collection: Simulator records which coverpoints were hit. 5. Coverage Analysis: Identify coverage holes — scenarios not yet exercised. 6. Directed Tests: Write targeted tests to hit remaining coverage holes. 7. Coverage Closure: All coverpoints hit → verification goal met.

Coverage Goals for Tapeout

MetricTypical Threshold
Line coverage> 98%
Branch coverage> 95%
Toggle coverage> 90%
FSM coverage100% states, > 95% transitions
Functional coverage100% (all defined coverpoints hit)

Coverage-driven verification is the industry-standard methodology for verification closure — it transforms verification from an art into a measurable engineering discipline where quantitative coverage metrics determine when a design is ready for silicon.

coverage driven verificationfunctional coveragecode coveragecoverage closureverification coverage

Explore 500+ Semiconductor & AI Topics

From EUV lithography to CUDA optimization — search the full knowledge base or chat with our AI assistant.