This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English version of the page.

Note: This page has been translated by MathWorks. Click here to see
To view all translated materials including this page, select Country from the country navigator on the bottom of this page.

Design Model Architecture

Create independent components to share between models or teams, reduce visual complexity with model hierarchy

Simulink® facilitates component-based modeling and modular design. You can segment your model into design components and then model, simulate, and verify each component independently. You can save individual components as subsystems in a library or as separate models. Team members can then work on those components in parallel.

Organizing your model into hierarchical components can improve readability, traceability, and reusability, while allowing for concurrent development and unit testing. To mimic real-life systems, define components based on self-contained system functionality.

  • Model Components
    Learn when to use different types of model components
  • Subsystems
    Group blocks into functional subsystems, create model hierarchy
  • Libraries
    Reusable libraries of blocks and subsystems
  • Model References
    Reuse models as blocks in other models
  • Variant Systems
    Create custom model versions to support different specifications, without duplication
  • Data Stores
    Define global values for multiple signals at different levels of a model
  • Composite Signals
    Use composite signals, such as buses, to group signals and reduce model complexity