5 VerificationPlan
5 VerificationPlan
Methodologies
What is a Verification Plan?
• Specification document for verification effort
– Mechanism to ensure all essential features are
verified as needed
• What to verify ?
– Features and under what conditions to verify them
• How to verify ?
– What methodologies to use – Formal, Checking,
Coverage etc.
– What should be - Stimulus, Checkers, Coverage
• Priority for features to be verified
• Directed Testing
• Using specifications, write verification plan with list of tests, focusing on each
feature
• Apply corresponding stimulus and verify log files and waveforms manually
• Incremental procedure, where tests are covered one by one
• Produces immediate results, since we check creation of every stimulus vector.
Disadvantages :
Requires lot of time in the beginning to set up the test structure
Most of bugs found but some bugs have to be found only by directed testing..
100% functional coverage indicates that all items in the test plan have been tested.
Note: Functional coverage is user specified. We provide input file that specifies what
all needs to be covered.
Code Coverage:
Code coverage tracks what lines of code or expressions in the code have been
exercised.
100% code coverage implies that all expressions in code have been executed.
Code coverage is done automatically by the tool. There is no input from the user.
Functional Coverage
Functional Coverage convergence
Start from here