UVM · Topic
UVM Testbench Architecture — Env, Agent & Test Layers
How a UVM testbench is assembled — test, environment, agent, driver, monitor and sequencer — and which layer owns which decision.
The layering is not bureaucracy; each boundary exists so one thing can change without the others. An agent knows a protocol and nothing about a test. A test knows what scenario it wants and nothing about how a transfer is driven. Put protocol knowledge in a test and the testbench stops being reusable across projects; put scenario knowledge in a driver and every new test needs driver edits. Most architectural pain in a UVM environment traces back to a decision that was made at the wrong layer.