Multiple scoreboards in UVM TB framework

Hi,

Is it good idea to define each scoreaboard for each output interface in TB architecture?.

regards,
nivas.

Designing scoreboards is probably the most complex activity when building a testbench. The scoreboard keeps track of various transactions across the entire system and sign-off the correctness of the behavior.

As an example, take a NOC. If a transaction is driven on interface A at clock cycle N, and it is expected that the NOC will generate a new transaction at clock cycle N+2, on interface B, then a scoreboard that gets all the data from interface A and interface B can ensure that the DUT is behaving as expected. So in general, answer to your question is No.

In some limited corner cases, may be okay to restrict the scoreboard to monitor transactions of a single interface. This is true if all the input and response transactions happen on the same interface.

Logie Ramachandran
Accelver Systems Inc.

In reply to logie:

Thanks Ramachandran for your explanation.
Yes i agree scoreboard design is complex in TB building based on design.

Why the question raised in my mind is, if the requirement has someting like this: Stimulus is driving from one interface and out trasactions are traversing through multiple interfaces based on its functionalities, then it is judgible to have each scoreboard for each interface right?.
Or one common scoreboard can be designed and extended multiple scoreboards based on the interface transaction checking. Is this make sense.?

Appreciate to take this framework of scoreboard design discussion might helps for me, along with any other ideas.

regards,
nvas.

Look at my NOC example above. Looks like you need to have a single scoreboard with all the interfaces feeding data into it. This is the only way the scoreboard can check for the correctness of the DUT. Hope this helps.