MathWorks introduces Polyspace embedded code verification products with a range of new enhancements.
Polyspace embedded code verification products are used to prove the absence of certain run-time errors in source code in development environments.
New features such as the Polyspace metrics web dashboard, automated scheduling of verification jobs, email notification and increased code metric support allow engineers to choose and track embedded software quality metrics and thresholds.
Helping software teams to better define quality objectives and achieve them faster, Polyspace embedded code verification products are suitable for high-integrity applications across the automotive, aerospace, defence as well as industrial automation and machinery industries.
Embedded software in critical applications needs to meet specific software quality objectives as part of regulatory mandates or corporate verification processes. In order for software teams to achieve these objectives, developers and managers need to define quality goals, evaluation criteria and associated metrics thresholds.
Key features of the enhanced Polyspace embedded code verification products:
- Metrics web dashboard helps software developers define relevant metrics and thresholds such as code metrics, MISRA-C and run-time error metrics
- Dashboard provides the ability to track progress of these metrics through the verification process and compare differences in quality in each code revision
- Integration with nightly processes and email systems, helping to automate the process of continuous verification and preventing code quality fluctuations
- Reduced iterative work of manual verification tasks, allowing engineers to focus on higher-level verification tasks
Andrew Clay, Managing Director Australia, MathWorks says that in addition to verifying that embedded software is free of run-time errors, quality engineers and managers also need increased visibility into the software quality lifecycle.
The enhanced Polyspace solutions facilitate a common interface for the development team to design software quality models that support continuous code verification, allowing them to measure their progress relative to critical metrics and enabling them to meet increasing demands for high quality software.