Embedded Software Test and Verification
Boeing PhantomWorks
To make system modifications, we updated the Simulink diagram, automatically generated the code, installed the generated code, and hit the build button. We experienced a significant increase in productivity and avoided the pitfalls of hand coding.![]()
- Verification, Validation, and Test Overview
- Early Requirements Validation
- Design Verification
- Embedded Software Test and Verification
- Digital and Analog Hardware Verification
- Hardware-in-the-Loop (HIL) Simulation for Embedded Systems
MathWorks products support the two standard approaches for verifying embedded software: model-to-software verification and run-time error detection in the source code. With model-to-software verification, a fully verified model of your embedded software serves as a golden reference for comparing its behavior with your handwritten or model-generated software. With run-time error detection, MathWorks products for run-time analysis apply formal methods on handwritten or automatically generated source code to verify that the code does not have run-time errors. These verification processes are especially important for high-integrity embedded systems.
Verify Software Behavior with the Model
With Model-Based Design, you develop a model of your embedded software using Simulink. After verifying the system model against requirements or expected behavior, you can generate code automatically from the model to reduce the chance of errors introduced through hand coding.
Model-to-software verification techniques like software-in-the-loop (SIL) testing and processor-in-the-loop (PIL) testing can be applied to handwritten or model-generated code to confirm that the behavior of the software matches the behavior of the model. Formal analysis methods available in Simulink Design Verifier automate the generation of SIL and PIL tests from your model, and Embedded Coder™ helps streamline the PIL test process.
Ensure Code Correctness and Detect Run-Time Errors
With MathWorks tools, detect run-time errors and prove the absence of specific errors in C/C++ and Ada source code, whether handwritten, model-generated, or a combination of the two. Mathematical analysis techniques in Polyspace® code verification products prove the absence of overflow, divide by zero, out-of-bounds array access, and other run-time errors in source code, without requiring program execution, code instrumentation, or test cases.
Support Industry Standards for High-Integrity Systems, Including DO-178B, IEC-61508, and ISO-26262
Design embedded software for high-integrity systems that meet industry standards with Simulink and related tools. DO Qualification Kit provides documentation, test cases, and procedures that let you qualify Simulink or Polyspace software verification tools for projects based on the DO-178 standard. IEC Certification Kit includes certificates and reports from certification authority TÜV SÜD that are based on documented, application-specific verification workflows to help you use Embedded Coder™ or Polyspace code verification products for projects based on the IEC 61508 and ISO 26262 standards.

Free Verification, Validation, and Test Technical Kits
Get resources for simulating, testing, and analyzing models to verify designs and validate requirements.
Get free kit