I also read some something about the layered approach in the book "Hardware Verification with SystemVerilog", chapter 4 "A Layered Approach". .
It look like a another view of the "OVM User Guide" documentation at page 71 (Figure 4-2 OVC Verification Environment Class Diagram).
But I'm not sure is that the same issues?
What's your opinion?
Hi Stephan,
VMM/OVM/UVM and Truss are similar in that all methodologies advocate a separation of generator, driver, checker, and monitor.
Truss is different in that we advocate but do not require a layered approach. Truss does not have 800 rules, nor have a data or transactor base class, or rules on when and where you must construct your objects.
In fact, while we use Teal and Truss here at work, there are many different styles of methodology withing the truss umbrella. A main purpose of Truss was to allow every coder on your team to be as efficient as possible. We are fairly far along in this project, yet no one has had any issues with how anyone else codes or structures their code.
So Truss and the others are similar in theory yet vastly different in practice. Does that make sense?
Take Care,
mike
You must log in to post.
Member
Key Master