The benefits of a metric-driven verification flow are based on the value of using specifications to create verification plans, measuring progress, and being able to determine when high-quality verification closure is achieved. Coverage, checks, and assertions provide the verification-specific metrics used to determine closure. Verification job failures, bugs, and design revisions all provide insight into the actual status of a project.
Leveraging Cadence® Incisive® verification technologies, the Cadence metric-driven verification (MDV) flow starts from automated planning, either annotating existing specifications with verification intent or creating an executable verification plan using all team member input. The plan specifies the verification environment requirements to be implemented in a coverage-driven testbench language and ensuring design intent can be delivered. Verification IP, including the automated Compliance Management System, provides immediate access to the MDV methodology by delivering a protocol-specific verification plan and test suite. Verification simulation, formal analysis, analog mixed-signal, acceleration, and emulation engines are dispatched and convergence of multiple verification engines is managed within the Incisive Enterprise Manager. Failures are analyzed and prioritized. Regression coverage is analyzed and changes to the testbench and assertions are developed to reach closure. From a verification perspective, closure is measured by coverage, which is an abstract way to tangibly measure all the features and functions you are trying to verify. Progress analysis and reports help the verification team make adjustments to their resource allocation (people and tools) to reach closure more efficiently and measure closure more accurately.
- Improved verification planning results in higher quality
- Metrics analysis and reporting increase schedule predictability
- Failure/metrics analysis and job automation boost overall team productivity