Download Public Interface

Transactors should call a callback method before transmitting
data, allowing the user to record, modify or drop the data
Whether it is a transaction descriptor or driving a byte on a
physical interface, the new output data must be reported to the
user to be recorded in or checked against a scoreboard, modified
to inject an error or collect functional coverage metrics.
Transactors should call a callback method after generating any
new information, allowing the user to record or modify the new
information
Whenever a transaction requires locally generated additional
information, the additional information must be reported to the
user to be recorded in or checked against a scoreboard, modified
to inject an error or collect functional coverage. A reference to the
original transaction should be provided to convey context
information.
For example, a transactor prepending a packet with a preamble
should call a callback method with the generated preamble data
before starting the transmission process.
Transactors should call a callback method after making a
significant decision but before acting on it, allowing the user to
modify the default decision
Whenever a transactor makes a choice between several
alternatives, the choice and available alternatives must be
reported to the user to be recorded in or checked against a
scoreboard, modified to select another alternative or collect
functional coverage.
Transactors: Transactor Models
6-8