In reply to Varunshivashankar:
It looks like you are running only a few tests on your current environment using the steps in the initial block.
I do not know all the details of your design. But I beleive you have to have all these steps in eaach of your sequences, assuming the DUT needs to be initialised (reset), configured, enabled and executed with checking.
The driver is implementing the protocol of your functional interface, polling a sequence item from the sequencer, processing this item and optionally generating a response and pass it back to the sequence. Where the quecking will happen depends on your design. It might be in the sequnce or you need a scoreboard.