Senior verification work decides what to build, in what order, and when the evidence supports sign-off. A living plan, a deliberate method mix, honest metrics, and explicit risk calls carry a block from specification to done.
SPEC-TO-SIGN-OFF FLOW
Spec → Feature extraction → Risk ranking → Verification plan
│
┌─────────────────────────┤
▼ ▼
Methodology mix Plan review gate
(directed / random / │
formal / emulation) ▼
│ Testbench build
└────────────┬───────────┘
▼
Bring-up → Feature complete
│
▼
Coverage closure + bug-rate convergence
│
▼
Hole analysis → Sign-off review → DONE
▲
(loop back on every spec change)Lesson | What it decides | Path |
|---|---|---|
Feature rows, risk rank, ambiguity log, and review gates. | Required | |
Directed, random, formal, or emulation per feature class and level. | Recommended | |
Phase exits, the weekly dashboard, and audits that keep metrics honest. | Recommended | |
Spec changes, capacity, descoping waivers, and the evidence bundle. | Required |
Path: Required is the core first pass for this topic, Recommended is what most learners should read, and Optional is reference, specialist or revision material you can skip at first.
No. The row names no stimulus and no check. Split it until each row pairs one behavior with one check and one coverage point.