In reply to cgales:
In reply to Reuben:
The reason for using the standard UVM topology of sequencer-driver connection and standalone monitor has to due to ensuring that component reuse is maintained.
The sequencer-driver part of the UVC should be able to operate independently of any other component. If the sequence is generating a read transaction, the driver should generate a response to the sequencer with the read value so that the sequencer can use the response data to potentially influence the next sequence item. Since everything is transaction based, there is the potential that your monitor items aren’t synchronized properly.
While there is some duplication of code between the driver and monitor, this is required to ensure UVC reuse.
I see. Thanks for the info.