Implement transaction logic in driver or sequence class

In reply to ak_verifsj:

In reply to dave_59:
Hi dave, I think my wordings made the question little complicated. Rephrasing the questions - Consider scenario where I need to send data[31:0] on each clk. I need to send 15 data in 25 clks. On the remaining 10 clks driver should not drive anything on DUT.

Your interface spec should say what are you doing when not sending data to the DUT. Maybe your interafce has an ‘idel’ state.
BTW the sequencer does not send any transaction to the driver. The driver polls the transactions from the sequencer. In the driver there is all timing and nowhere else.