verification plan
A verification plan is the master checklist that turns a chip's specification into a concrete list of 'things we must prove work before we believe this design is correct.' Think of it like a pilot's pre-flight checklist: before the plane leaves the gate, every system — flaps, fuel, hydraulics — gets a tick. The vplan does the same for a digital block, enumerating every feature, corner case, error condition, and mode the design claims to support, and naming exactly which test or coverage point will exercise each one.
Crucially, a good vplan is the bridge between human intent and machine-measurable progress: each line item is linked to a functional coverage point, so a coverage report can automatically tell you '83% of the plan is hit.' That number becomes the project's heartbeat — managers track it, and tape-out is gated on it. Without a vplan, a team writes tests until they run out of time and hopes that was enough; with one, they know precisely what is still unverified.
One row of a vplan linking a spec feature to a test and a coverage point.
A vplan is a living document: when a bug escapes to silicon, the post-mortem almost always adds a new line item so that class of bug can never slip through unverified again.