Simulink Design Verifier

Check modeled requirements for consistency and completeness before beginning your design.

Validate Requirements

Check modeled requirements for consistency and completeness before beginning your design.

Run-Time and diagnostic errors

Detect Run-Time and Diagnostic Errors

Before you run simulations, you can detect run-time and modeling errors, including integer overflow, division by zero, array out of bounds, subnormal values, and floating-point errors as well as data validity errors.

Viewing dead logic in your models.

Find Dead Logic

Find objects in your model that cannot be activated during simulation and execution of generated code.

Analyze Missing Test Coverage

Augment and extend existing manually created test cases to address incomplete model coverage and coverage of generated code and C/C++ code called from Simulink blocks and in Stateflow charts.

Safety Requirements

Verify Formal Safety Requirements

Verify that your design behaves according to formally defined safety requirements (3:53) that you express using MATLAB, Simulink, and Stateflow.

Requirements-based test cases.

Create Requirements-Based Test Cases

Generate test cases from models of system requirements.

“By enabling us to analyze requirements quickly, reuse designs from previous products, and eliminate manual coding errors, Model-Based Design has reduced development times and enabled us to shorten schedules to meet the needs of our customers.”

Simulink Design Verifier FAQs

Simulink Design Verifier uses formal methods to identify hidden design errors in models, verify that designs meet functional requirements, and generate test cases for model coverage and custom objectives.

It detects blocks that result in integer overflow, dead logic, array access violations, division by zero, subnormal values, floating-point errors, and data validity errors.

Dead logic refers to objects in your model that cannot be activated during simulation and execution of generated code. Simulink Design Verifier identifies these inactive components during formal analysis.

It automatically generates test cases to drive your model to satisfy condition, decision, modified condition/decision (MCDC), and custom coverage objectives, and can create requirements-based test cases from models of system requirements.

Yes, it can formally verify that your design behaves according to formally defined safety requirements expressed using MATLAB, Simulink, and Stateflow, and generates a simulation test case for each design error or requirements violation for debugging.

Yes, support for industry standards is available through IEC Certification Kit for ISO 26262 and IEC 61508, and DO Qualification Kit for DO-178 and DO-254.

It analyzes missing test coverage and augments existing manually created test cases to address incomplete model coverage and coverage of generated code and C/C++ code called from Simulink blocks and in Stateflow charts.

Yes, it can check modeled requirements using the Requirements Table for consistency and completeness before you begin implementing your design.