The Verification Plan (vplan)
VLSI → Verification Planning & Management
The contract, written before any code
The vplan lists every feature from the spec, the scenarios that exercise it, and the coverage that proves it — all written down before you write a single line of testbench. Everything downstream — tests, coverage, sign-off — traces back to one specific row in this plan.
Why 'how would you verify this block?' really means 'sketch a vplan'
Teams hire DV engineers who can plan, not just code. When an interviewer asks "how would you verify this FIFO?", they're really asking you to produce, on the spot, a small vplan: list 3-4 features (full/empty detection, overflow behavior, back-to-back writes), a scenario for each, and what coverage would prove each scenario happened. That structured answer is what separates a planner from a button-pusher.
Try it — build one vplan row
This one row is what a scoreboard check and a covergroup bin both need to implement — planning first is what makes that implementation obvious instead of improvised.
Completion saves automatically after you read through to the end.
Next lesson →