Implementation notes

Implementation APIs

The following APIs have been defined for easy extension fo the scoreboard classes:

1. Configuration API: cl_syoscb_cfg
2. Item API: cl_syoscb_item
3. Queue API: cl_syoscb_queue
4. Compare API: cl_syoscb_compare_base
5. Subscriber API: cl_syoscb_subscriber
6. Iterator API: cl_syoscb_queue_iterator_base

General error handling

In general when a lower level method detects an error then two concepts are used. Primarily, the method will either issue a UVM info with some information about what went wrong or issue a UVM error/fatal immediately. The first one will then return 1'b0 to signal that something went wrong. Thus, it is up to the parent levels to catch the error and convert them into UVM errors/fatals etc. This method was chosen since the parent level typically provides more and better information when things go wrong.

Error categories

There are several ERROR categories. The following table lists them with some explanation:

Error Category	Description
IMPL_ERROR	Implementation error. Something is really broken
QUEUE_ERROR	A queue related error, e.g. the queue could not be found
CFG_ERROR	Configuration error. Usually, because the configuration object is missing
TYPE_ERROR	Type error. Typically issued when $cast() fails
COMPARE_ERROR	Compare error. Issued, e.g. when the in order compare fails /table>

Multiple queue references

Both the top level class cl_syoscb and the configuration class cl_syoscb_cfg contains handles to all queues. The former uses an ordinary array which provides a fast way of looping over the queues and the latter an associative which makes it easy to find a queue using only its name.