New Polyspace Code Verification Products
Use the new source code verification products Polyspace Bug Finder™ and Polyspace Code Prover™ to find bugs and prove the absence of errors in your code.
Polyspace Bug Finder provides significant functionality to the Polyspace product family. With Polyspace Bug Finder, you can quickly analyze your source files for bugs. Integrate Polyspace Bug Finder into your IDE (e.g., Eclipse or Visual Studio) as part of your code development process. With bug trace information, you can triage and debug defects in your editor and rerun Polyspace Bug Finder to ensure that you have corrected the error.
You can begin this process by checking for code compliance to standards like MISRA C/C++, JSF++, or by implementing your own custom coding rules. Run Polyspace Bug Finder analysis as soon as you have compiled your code in your IDE.
Polyspace Bug Finder identifies classes of defects such as:
Polyspace Code Prover helps verify the safety and reliability of high integrity applications using formal methods to help you detect and prove the absence of run-time errors for all the checks in your code.
MATLAB Distributed Computing Server™ and Parallel Computing Toolbox™ replace the client-server solution that existed prior to Release 2013b and give you the flexibility to adopt a desktop solution or a cluster-based verification process. This provides you with a scalable solution to run verification on large code bases. It also provides you with the ability to customize the job queuing mechanism using custom job schedulers like Windows HPC, LSF®, or TORQUE. Integration with the MATLAB computing platform gives you scripting capabilities in automating the project setup and in verification result post-processing.
The new Polyspace Bug Finder and Polyspace Code Prover products help you adopt a systematic process for qualifying high integrity software irrespective of the source. For example, Polyspace products can help you to measure the impact of changes you make to legacy code, or help you eliminate defects from code you develop from scratch. You can easily trace any bugs back to your model if you are using generated code environments like Simulink or TargetLink®. Verify your software early and often to decrease the cost of late or missed defects.
You can use Polyspace Bug Finder early in the development process (e.g., at the coding phase) to identify and fix defects before you spend time on code reviews. Run Polyspace Code Prover to prove the absence of run-time errors at a component level and eliminate the need for robustness testing. Later in the development process, run the tools on the entire application to account for integration errors.