Main Content

Get Started with Simulink Design Verifier

Identify design errors, prove requirements compliance, and generate tests

Simulink® Design Verifier™ uses formal methods to identify hidden design errors in models. It detects blocks in the model that result in integer overflow, dead logic, array access violations, and division by zero. It can formally verify that the design meets functional requirements. For each design error or requirements violation, it generates a simulation test case for debugging.

Simulink Design Verifier generates test cases for model coverage and custom objectives to extend existing requirements-based test cases. These test cases drive your model to satisfy condition, decision, modified condition/decision (MCDC), and custom coverage objectives. In addition to coverage objectives, you can specify custom test objectives to automatically generate requirements-based test cases.

Support for industry standards is available through IEC Certification Kit (for IEC 61508 and ISO 26262) and DO Qualification Kit (for DO-178).

Tutorials

Featured Examples

Videos

What Is Simulink Design Verifier?
Introduction to Simulink Design Verifier.

How to Use Simulink Design Verifier to Automatically Detect Design Errors in Your Simulink Models
Use Simulink Design Verifier to find errors in a design, and how errors, when detected, can be debugged using the visualization features in Simulink Design Verifier.

DO-178C Workflow for Automatic Test Vector Generation
Use Simulink Design Verifier to automatically generate test vectors to analyze missing model coverage collected by Simulink Coverage in order to comply with DO-178C and its supplements.

How to Debug a Property Proving Counterexample
Property proving with Simulink Design Verifier™ is a static analysis technique that uses formal methods to prove whether a given property will always be valid. This technique can help you formally verify that specific requirements implemented in your design will always be met.

Requirements-Based Testing Workflow
Explains how to create a test using a test sequence, define a formal assessment, link test cases to requirements, run test suites, and analyze missing model test coverage.