Separate transaction production, measurement selection, and aggregate calculation.
The metric-object pattern
Three responsibilities
- A monitor or other producer publishes transactions through a UVM analysis connection.
- An analyzer's write method selects numeric values from each transaction.
- Named metric objects own measurement storage and aggregate operations.
This separation lets one producer feed latency, data-rate, bandwidth, occupancy, or other domain-specific metrics without putting every calculation into the monitor or scoreboard.
The public example
The repository contains a metric class, a package include list, a top-level usage sketch, expected console output, and an EDA Playground link. It is a teaching example rather than a versioned library with a build system or automated tests.