Engineers with seven or more years are judged on how they verify systems, not on syntax. This part covers the patterns that scale: reusable testbench architecture, checking for multi-outstanding traffic, assertions that track IDs, coverage of real features, and the judgment calls a lead makes.
It assumes Parts 1 to 8. UVM is built from the same patterns; the UVM course shows the library versions.
Topic | Lessons | What it covers | Time |
|---|---|---|---|
5 | Policy classes, abstract BFMs, parameterized interfaces, interface classes and layered stimulus. | 45 min | |
4 | ID-tagged and multi-stream scoreboards, drain and leak accounting, and memory-model checkers. | 40 min | |
5 | Abort operators, recursive properties, let and libraries, ID tracking with local variables, formal-ready assertions. | 45 min | |
4 | Transaction and temporal coverage, filtered bins, assertion-backed covers and closure at scale. | 35 min | |
5 | Spec, environment, checking, coverage, a six-bug hunt and sign-off for an ID-tagged controller. | 60 min | |
5 | Escaped bugs, intermittent failures, misleading metrics, scaling, and system design interviews. | 45 min |
One that only checks that every expected item eventually arrives, in any order. Responses must stay in order within an ID even when IDs interleave. The Checking Out-of-Order Traffic topic builds that scoreboard.