Modularity, Scalability, Reusability, Configurability Interoperability

UVM
, , , ,
1

Hello everyone,

I have now already successfully used UVM for a verification project, but I’d like to get some general background information about the methodology itself.

Could please someone explain me in just like one line, what makes a testbench really modular, scalable, reusable, configurable and interoperable?

Probably some of you here have more knowledge about that topic compared to someone like me, which has just started using it.

In chapter 5 Base Classes of the UVM Class Reference Manual it is said that the UVM library facilitates those features, but I’d just like to know, on a high and abstract level, how this can be reached.

Really appreciate your support and many thanks in advance,
René

2

In reply to RenéPi:

See The Art of Separation of Concerns · Aspiring Craftsman and Separation of Concerns | DevIQ

3

In reply to RenéPi:

A few different words to the Dave’s link:
(1) Modularity: - seperating test form testbench
- using an agent-based approach
(2) Scalability: - usage of parameters,
- instantiation of thge same agent several times
(3) reusabality: - plug-and-play reuse
- reusing components without modifications in another project (providing only a
link to the existing agent)
(4) Configurability: - UVM provides different mechanism for configuration
- factory
- uvm_config_db
- configuration objects
(5) Interoperability: Because of the UVM base-class library and the OOP mechanism your components
are compatible to each other of the same type.