Organizing Your Model

Simulink lets you organize your model into clear, manageable levels of hierarchy by using subsystems. Subsystems encapsulate a group of blocks and signals in a single block. They are the primary method for including hierarchy in your model.

You can also segment your model into design components to model, simulate, and verify each component independently. Components can be saved as separate models or as subsystems in a library. They are compatible with configuration management systems, such as CVS and RCS, and with any registered Source Control Provider application on Windows platforms.You can reuse the design components on multiple projects, easily maintaining audit and revision histories.

Organizing your models in this way lets you select the level of detail appropriate to the design task. For example, you can use simple relationships to model high-level specifications and add more detailed relationships as you move toward implementation.

Configurable Subsystems

Configurable subsystems let you associate design variants with subsystems within a model. This capability simplifies the creation and management of designs that share components, as one model can represent a family of designs.

Conditionally Executed Subsystems

Conditionally executed subsystems let you change system dynamics by enabling or disabling specific sections of your design via controlling logic signals. Simulink lets you create control signals that can enable or trigger the execution of the subsystem based on specific time or events.

Control flow and logic blocks let you model simple commands to control enabled or triggered subsystems.

You can include more complex logic, as well as model event-driven systems, with Stateflow (available separately).