Upgrade MATLAB and Simulink

Best practices for migrating to newer MATLAB releases

Stay current with the latest software version of MATLAB^® and Simulink^® for new functionality, improved performance, and current regulatory compliance. Most users upgrade every release, but you can explore other cadence options that work best for your organization.

Read the MATLAB and Simulink Version Upgrades white paper to learn about the upgrade process, including a roll-out plan for large organizations and a checklist for quick reference.

MATLAB

• MATLAB Code Compatibility Analyzer: Analyzes code, lists compatibility issues, and provides instructions to address compatibility issues
• GUIDE to App Designer Migration tool for MATLAB: Converts your GUIDE app to an App Designer app
• MATLAB Unit Test framework: Provides test tools so you can write unit tests for your programs

Simulink

• Simulink Performance Advisor: Produces a report that recommends better configuration settings, implements them automatically, and runs simulations in accelerator mode to improve simulation performance
• Simulink Model Comparison: Compares models between two versions and merges differences
• Simulink Test: Provides tools for authoring, managing, and executing systematic, simulation-based tests of models, generated code, and simulated or physical hardware
• Run tests in multiple releases of MATLAB: Enables you to test functionality from later releases while running the tests in your preferred release of Simulink
• Equivalence test: Compare functional equivalence for two Simulink model simulations that were run in different releases
• Requirements Toolbox: Lets you author, link, and validate requirements within MATLAB or Simulink
• Requirements-based testing: Provides model verification, interpreting, and reporting test results
• Simulink Coverage: Performs model and code coverage analysis that measures testing completeness in models and generated code
• Code coverage: Enables you to collect code coverage metrics during software-in-the-loop (SIL) and processor-in-the-loop (PIL) simulations
• Continuous integration (CI): Use CI to automatically test and verify MATLAB code and Simulink models, and generate code in the new release

Embedded Coder

• Embedded Coder cross-release support: Integrates generated code from previous releases with generated code from the current release
• Cross-release code integration: Enables testing of generated code from different releases and code reuse of existing code from earlier releases without modifications