TAILIEUCHUNG - Standardized Functional Verification- P10

Standardized Functional Verification- P10:Every manager who brings a design to tape-out or who purchases IP must eventually face these questions. The ability to answer these questions based on quantitative analysis is both vital and yet elusive. In spite of the enormous technical advances made in IC development and verification software, the answers to these questions are still based largely on guesswork and hand waving. | Executing the Plan to Obtain Results 75 participate in perhaps a single simple atomic write and read transactions on a bus. It is desirable to preserve this always-working model as the project progresses from this point forward. Subsequent check-ins of code whether for the RTL or for the testbench should ideally not cause this most basic of functionality to break exhibit faulty behavior . Thus the regression suite has been born too. This is truly an important milestone Initial Coding IC done an instance of the target interoperates with the testbench and performs some basic function . produces correct responses to selected basic excitations. The value of achieving this particular milestone IC done is that it represents a particular synchronization of the RTL team with the verification team. It s usually the case that either the RTL or the testbench will precede the other in working functionality. When the code that lags the other catches up a working target in a working testbench containing a model of the context has been brought to life. Effective project management will facilitate cooperation between the two teams such that working functionality is continuously added to both the RTL and to the testbench enabling the regression suite to grow along with these two elements. This all takes place during the Final Coding phase of the code construction effort. At some point in time the RTL team will declare that all specified functionality has been coded in the RTL. This is the official end of the construction effort for the RTL and subsequent changes will be made to revise the RTL to fix bugs and to accommodate requirements for layout and timing. This is also a good time to begin tracking bugs formally. This is the second important milestone Final Coding FC done all defined and intended functionality has been coded. At this point all bugs recorded in the interpretation of the specification should be resolved and the associated interpretation should be correct and