Arguably the most impactful feature of R2021a was the beta release of the Visual Studio Code extension. This allowed developers to run Polyspace Bug Finder live inside their IDE, checking code before pushing to the repository—shifting analysis left in the SDLC.
Polyspace R2021a includes two primary static analysis tools, plus supporting utilities:
| Product | Purpose | Typical Use | |---------|---------|-------------| | Polyspace Bug Finder | Find logic, data flow, and concurrency defects early. | Continuous integration (CI) for general code quality. | | Polyspace Code Prover | Prove absence of runtime errors (overflow, division by zero, out-of-bounds access). | Certification & safety-critical code (DO-178C Level A, ISO 26262 ASIL D). | | Polyspace Access | Web-based dashboard for aggregating results across teams/projects. | Centralized review, traceability, and metrics. | | Polyspace Server | Batch execution and compute farm integration (e.g., LSF, SLURM). | Large-scale or automated analysis. |
Choose Polyspace R2021a if:
Avoid if:
For teams already in the MathWorks ecosystem (Simulink, Embedded Coder, MATLAB), Polyspace R2021a is a natural, powerful extension. Its ability to prove code correctness—not just guess—makes it indispensable for the most demanding embedded applications.
Before dissecting the R2021a update, it is crucial to understand the two core products within the Polyspace family: polyspace r2021a
R2021a brought these two tools closer together, offering a unified desktop interface and significantly improved server-side processing.
With C++17 adoption rising in embedded (e.g., std::optional, structured bindings, if constexpr), Polyspace R2021a extended its semantic analysis to handle these constructs correctly in both Bug Finder and Code Prover. The abstract interpretation domain was updated to model std::variant and std::visit without false positives.
For medical device software, R2021a improves the documentation workflow. The generated reports now include more granular traceability links, specifically tailored to the software lifecycle requirements of IEC 62304. This reduces the manual effort required to map static analysis results to the Software Development Plan (SDP). Arguably the most impactful feature of R2021a was
Polyspace R2021a is a "maturity release." It fixes the performance bottlenecks of R2020b, adds practical support for VS Code (PAYC), and significantly speeds up Code Prover via multi-core. It is not a revolutionary UI overhaul, but for safety-critical teams writing MISRA-compliant C/C++ for automotive, avionics, or medical devices, it represents a stable, actionable upgrade.
The results database schema changed from SQLite embedded to a more robust PostgreSQL backend for server deployments. Note: This is a breaking change. If you upgrade a Polyspace Access server from R2020b to R2021a, automatic migration is not supported. You must export old results as JSON before upgrading.