Is there a figure that shows how calls flow from test → sequence → sequencer → driver?
I don’t need conceptual flow because that is pretty much clear from UVM cookbook but real calls.
In reply to verif_learner:
A test calls one more more virtual sequences/sequences.
A sequence will be executed on a sequencer, generating seq_items. seq_items are retrieved from the driver using get or get_next_item. The interface between the sequencer and the driver is blocking.