OOP Patterns for Testbenches · SystemVerilog

Part 2 · OOP for Verification · Intermediate

5topics
5lessons

Five hand-built patterns carry most testbench structure. A disciplined transaction, a factory, a shared config, callbacks and a phased hierarchy compose into one environment, and each pattern resurfaces as a UVM standard.

Five patterns pointing at the UVM standards they become.

Each hand-built pattern resurfaces as a UVM standard.

Lesson	What gets built
The Transaction Base Class	Copy, compare, print and pack on one self-contained transaction.
The Factory Pattern from Scratch	A creator registry with explicit registration and test-time overrides.
Singletons and Config Objects	One shared config with protected construction and freeze before build.
Callbacks and Hooks	Driver hooks with stacked callbacks for injection and sampling.
Building a Component Hierarchy by Hand	A named tree with build, connect and run waves.

Check yourself A bench creates transactions through a factory, configures them from a singleton, extends its driver with callbacks and organizes it all in a phased tree. Which UVM pieces has it already reinvented?

The object and factory, the config database, the callback system and the component phases. UVM standardizes these five patterns, and the bench already runs their hand-built versions.

Up nextThe Transaction Base Class

Practice this lesson Report an error

Lesson

What gets built

The Transaction Base Class

Copy, compare, print and pack on one self-contained transaction.

The Factory Pattern from Scratch

A creator registry with explicit registration and test-time overrides.

Singletons and Config Objects

One shared config with protected construction and freeze before build.

Callbacks and Hooks

Driver hooks with stacked callbacks for injection and sampling.

Building a Component Hierarchy by Hand

A named tree with build, connect and run waves.