Transactional Style C++ Testbench

What are transactional testbench

a testbench that uses transactions that provide an abstraction layer above directly assigning values to input pins and directly checking values of output pins of a DUT
consists of:
- transaction generator/sequence: a block that generates stimulus data for the DUT
- driver: a block that drives the aforementioned data onto the DUT
- monitor: a block that observes the DUT's outpus and generates result data packets
- scoreboard: a block that collects various data packedts, then compares them for correctness
- coverage: a block that collects various data packets, and calculates functional coverage
drawbacks: complexity, slower to get basic simulations going
- howerver: flexibility and resuability

trancation: a high-level data exchange operation
- trancation item: a data packet(a collection of data or instructions)

transaction generator: a class or block of code that generates transaction items

drivers: take [[transactional style C++ testbench#Transaction and trancation item|transaction item]] and manipulate the physical pins of an input interface with 1's and 0's to drive data into a DUT

interface: a collection or a group of pins that are used for a specific function

monitor: observe what's happening on the interface
- it is connected to an output interface, and check the output of the DUT
- input: ensure that the associated driver drives the interface correctly

scoreboard: performs checks on the recieved transaction items to make sure the observed input stimuli result in correct outputs, and determines whether the testbench passes or fails