CI/CD Automation for Model-Based Design
Simplify adoption and optimize Continuous Integration/Continuous Delivery (CI/CD) workflows for Simulink with the CI/CD Automation for Simulink Check Support Package. You can define your CI/CD pipeline, prequalify on your desktop to avoid build failures, integrate with CI Systems such as Jenkins® or Gitlab® and execute incremental builds to reduce build time.
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. Assess the status and quality of your code testing for software-in-the-loop (SIL) and processor-in-the-loop (PIL) tests by using the metric results in the SIL Code Testing Dashboard and PIL Code Testing Dashboard.
Measure Quality, Complexity and Maintainability
Assess your model’s size, architecture, and complexity with model metrics to help improve the readability, maintainability and reusability of your MATLAB, Simulink, and Stateflow artifacts in your project. Dashboards consolidate the metrics to help you monitor your progress towards compliance to standards such as ISO 26262, DO-178C, IEC 61508, IEC 62304, EN 50128, and other standards.
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 (4:03) or equivalence test failures, property proving counterexamples (6:33), 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