Checks compliance with MISRA C, MISRA C++, AUTOSAR C++14, and CERT C/C++.
R2021a set the stage for features that arrived in later releases (2021b through 2024):
This plugin addresses a major pain point for QA teams: bridging the gap between raw analysis logs and actionable developer feedback.
| Codebase (LOC) | Tool | R2020b time | R2021a time | Memory Δ | |---------------|------|-------------|-------------|-----------| | 200k (C, automotive) | Code Prover | 28 min | 24 min | -8% | | 500k (C++, aerospace) | Bug Finder | 17 min | 14 min | -5% | | 50k (C, MISRA) | Bug Finder | 4.2 min | 3.5 min | -10% | polyspace r2021a
Despite its robustness, users reported three recurring issues post-launch:
This guide covers the core features and setup of Polyspace R2021a , focusing on its two primary static analysis components: Bug Finder Code Prover 1. New Features in R2021a
The number of steps required to integrate Polyspace with current or earlier releases of MATLAB and Simulink was reduced, simplifying configuration for teams that use mixed toolchain versions. Checks compliance with MISRA C, MISRA C++, AUTOSAR
The Polyspace Access web interface received major usability updates in R2021a. Quality assurance leads and developers can collaborate smoothly on code reviews. The interface tracks triage history, allows users to assign findings, and displays compliance dashboards over time. Practical Workflow: Using Polyspace R2021a
: While 16 GB RAM is often cited as a minimum for MATLAB-based tools, 32 GB or 64 GB
and Code Prover separately if you are using the server versions. Each product typically requires its own license run through the MathWorks Installer MATLAB/Simulink Integration New Features in R2021a The number of steps
R2021a introduces a new category of specifically designed to manage and reduce software complexity.
The R2021a release brought several workflow-optimising updates that improved analysis speed, precision, and integration. 1. AUTOSAR RTE API Optimization