# What are the key points when implementing Driver?

**URL:** <https://verificationacademy.com/forums/t/what-are-the-key-points-when-implementing-driver/36300>\
**Category:** UVM\
**Tags:** UVM, driver\
**Created:** [July 16, 2019, 7:29am UTC](https://verificationacademy.com/forums/t/what-are-the-key-points-when-implementing-driver/36300 "2019-07-16T07:29:06Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![MarinaZhang](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/m/49beb7/32.png) [@MarinaZhang](https://verificationacademy.com/forums/u/MarinaZhang)\
**Post date:** [July 21, 2019, 12:45pm UTC](https://verificationacademy.com/forums/t/what-are-the-key-points-when-implementing-driver/36300/17 "2019-07-21T12:45:38Z")

</div>

_In reply to [chr\_sue](https://verificationacademy.com/forums/t/what-are-the-key-points-when-implementing-driver/36300/16):_

ready is DUT’s input signal, so my tb drive this signal, at the same time the driver sample data according to valid and ready, and then encapsulate into items.

BTW, I have learned all the basic\_uvm course last year or so.

---

_[View the full topic](https://verificationacademy.com/forums/t/what-are-the-key-points-when-implementing-driver/36300)._
