Simulink Check


Customize Model Checks

Configure, customize, and automate custom Model Advisor checks to ensure that models comply with your organization’s own standards and guidelines.

Find and Fix Errors as You Go

Use edit-time checking to identify errors and address them as they are introduced to avoid rework later. Create custom edit-time checks for Simulink®, System Composer™, or Stateflow® to meet your organization’s own standards.

Track Requirements-Based Testing

Monitor the status and quality of unit testing artifacts to assess the completeness of your requirements-based testing and comply with ISO 26262 and DO-178C standards.

Measure Model Quality with Metrics

Collect model metrics to assess your model’s architecture, complexity, and readability in compliance with ISO 26262, DO-178C, DO-331, DO-254, IEC 61508, IEC 62304, EN 50128, and other standards. Integrate metrics such as model size, lines of code, status of guideline compliance, reuse, and complexity in a single view.

Automate Model Reviews and Reporting

Generate Model Advisor reports for reviews. Justify violations to suppress warnings and errors. Run checks on multiple machines in parallel to accelerate compliance verification with Parallel Computing Toolbox™.

Simplify and Debug Complex Models

Use Model Slicer to highlight functional dependencies through a combination of static and dynamic analysis based on active behavior during simulation. Debug errors such as baseline test or equivalence test failures, property proving counterexamples, or integer overflows.

Identify and Refactor Modeling Clones Across Models

Analyze models to locate clones and duplicate modeling patterns. Automatically refactor to improve maintainability, increase reuse, and reduce design complexity. Detect inefficient patterns and refactor them for increased code efficiency.

“We use our system design model in Simulink for ARP4754 to establish stable, objective requirements. We save time by using the model as the basis for our software design model for DO-178—from which we generate flight code—and reusing validation tests for software verification.”

Ronald Blanrue, Airbus Helicopters