360 MV's FormalDoublePASS™ completeness methodology
The FormalDoublePass™ completeness methodology comprehensively guides the engineer from verification planning to final, documented True Functional Sign-off. The methodology gives detailed recipes on how to successfully tackle and complete the following four verification phases in order to leverage the full capabilities of 360 MV – efficiently achieving error-free modules and IP.The Four FormalDoublePASS™ Phases
-
Verification Planning
User partitions the overall verification task into sub-tasks, based upon the specification, the transaction view of the design and a tool-guided code review process. -
Design Conditioning
User executes an extensive set of automatically generated design consistency checks to rapidly clean the RTL code of common coding errors. -
Property Development
User deploys the property development environment to step-wise describe and verify selected code using specification-compliant, transaction-level properties. The debugging and diagnosis environment enables the user to quickly locate the root cause of errors in the RTL, the property or the original specification. -
Complete Property Set Development
User employs the automatic completeness analysis to systematically identify all verification gaps. Detailed debugging and diagnosis information guides the user to develop and prove additional properties to close these gaps. The user reliably knows that verification is terminated when the completeness analysis confirms that the property set is indeed complete. At this point, a True Functional Sign-off is reached.
Results upon True Functional Sign-Off:
- RTL is free of any unintended, unexpected, and unverified behaviour – error-free operation is ensured
- Specification cleaned from errors and omissions
- Complete set of proven, specification compliant properties
- Complete set of integration conditions that ensure correct integration of the verified component in any target design