Not supported

You save a subsystem in the same file as its parent.

To create or change a subsystem, you must edit the parent file, which can lead to file contention and merge problems.

Supported

You save the parent library block of a linked block in a separate file.

Using separate files helps to avoid file contention.

Supported

You save a referenced subsystem in a separate file.

Using separate files helps to avoid file contention.

Supported

You save a referenced model in a separate file.

Using separate files helps to avoid file contention.

Not supported

Subsystems depend on models to provide a context for execution.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

You can develop a referenced model independently from the models that use it.

To simulate a referenced model as a standalone model, open the referenced model as the top model in a new window. The referenced model must have the data required to execute in a standalone context. For example, the referenced model must have the variables and data types that define parameters and signals.

Not supported

You cannot directly place subsystems in a source control system.

To reduce file contention and use separate version control for each subsystem, use a subsystem reference.

Supported

You can place library files in a source control system.

To provide individual version control for each library block, use subsystem references and model references in the library. When you drag these blocks from the library into your model, they reference the subsystem file or model file.

Forwarding tables allow you to map old library blocks to new versions of the blocks.

Supported

You can place subsystem files in a source control system.

Supported

You can place model files in a source control system.

Not supported

Use model references instead.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

Protected models obscure model contents, which can be useful when distributing models.

Creating a protected model requires a Simulink^® Coder™ license. For more information, see Protect Models to Conceal Contents (Simulink Coder).

Using a protected model does not require a Simulink Coder license. For more information, see Reference Protected Models from Third Parties.

Not supported

While you can copy a subsystem to reuse it in a model, the copies are independent of each other.

Supported

You can link to the same parent library block multiple times in multiple models without creating copies.

Managing library links adds some overhead, such as managing broken, disabled, or parameterized links.

Supported

You can reference the same subsystem multiple times in multiple models without creating copies.

Supported

You can reference the same model multiple times in multiple models without creating copies. See Model Reuse.

Supported

You can share data among instances by defining the data outside the component. For example, by using a data store in a common parent subsystem.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

You can share data among instances of the referenced model by creating a data store inside the model. See Share Data Among Referenced Model Instances.

Supported

Subsystem copies are independent of each other.

Supported

When you edit a parent library block, the changes apply to the library file and propagate to all blocks that link to that block.

To edit an instance of the block, you can disable the library link.

You cannot disable library links when the parent library block has restricted write access.

Not supported

When you edit an instance of a referenced subsystem, the changes apply to the subsystem file and propagate to all other instances of the referenced subsystem.

Supported

When you edit an instance of a referenced model, the changes apply to the model file and propagate to all other instances of the referenced model.

To specify instance-specific parameter values for referenced models, see Parameterize Instances of a Reusable Referenced Model.

Supported

Add subsystem variants to a Variant Subsystem or Variant Model block.

For more information, see Implement Variations in Separate Hierarchy Using Variant Subsystems.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

Add model variants to a Variant Subsystem or Variant Model block.

For more information, see Implement Variations in Separate Hierarchy Using Variant Subsystems.

Not supported

Loading a model loads all subsystem contents that are saved in the model.

Supported

The software incrementally loads a library at the point needed during editing, updating a diagram, or simulating a model.

Supported

The software incrementally loads a referenced subsystem at the point needed during editing, updating a diagram, or simulating a model.

Supported

The software incrementally loads a referenced model at the point needed during editing, updating a diagram, or simulating a model.

Not supported

Subsystems compile as part of their parent model.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

A referenced model that simulates in accelerator mode compiles according to the value of its Rebuild configuration parameter.

Whether a model compiles is independent of other models.

Not supported

Build artifacts, such as simulation targets, are not generated for subsystems.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

Team members and continuous integration (CI) systems can generate Simulink cache files for models that you use. These files let you reuse build artifacts, such as simulation targets, which can speed up simulation and code generation. For more information, see Share Simulink Cache Files for Faster Simulation.

Not supported

Subsystems do not reduce memory usage for simulation and code generation.

Not supported

Linked subsystems do not reduce memory usage for simulation and code generation.

Simulink duplicates library block instances during block update.

Not supported

Subsystem references do not reduce memory usage for simulation and code generation.

Simulink duplicates subsystem reference instances during block update.

Supported

Models referenced in accelerator mode reduce memory usage for simulation and code generation because Simulink incrementally loads compiled versions of them.

Supported

Subsystems that are not atomic avoid artificial algebraic loops.

If a subsystem is atomic, you can try to eliminate artificial algebraic loops by enabling the Subsystem block parameter Minimize algebraic loop occurrences.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

You can try to eliminate artificial algebraic loops by enabling Configuration Parameters > Model Referencing > Minimize algebraic loop occurrences.

Not supported

Subsystems inherit the solver of their parent model.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

You can use a local solver in a referenced model to solve a model reference as a separate set of differential equations. The local solver can use a different, larger step size. The choice of solver and solver settings involves a trade off between speed and accuracy in simulation. For more information, see Use Local Solvers in Referenced Models.

Not supported

Subsystems are built as part of their parent model.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

With Parallel Computing Toolbox™ software, you can distribute the code generation and compilation for referenced models across a parallel pool of MATLAB^® workers.

For large model reference hierarchies, you can increase the speed of diagram updates and code generation by building the model reference targets in parallel. For more information, see Reduce Update Time for Referenced Models by Using Parallel Builds and Reduce Build Time for Referenced Models by Using Parallel Builds (Simulink Coder).

Supported

If the context of a subsystem changes, such as the data type of an input signal, the related test harness must be updated.

For subsystems that are not atomic, the test harness may use different block execution orders, due to virtual boundaries.

For tools that support authoring, managing, and executing systematic, simulation-based tests of subsystems, see Create or Import Test Harnesses and Select Properties (Simulink Test).

To measure how thoroughly model components are tested, see Model Coverage (Simulink Coverage).

Supported

Same behavior as subsystems.

Supported

A test harness for a referenced subsystem has the same behavior as a test harness for a subsystem that is not stored in a separate file.

While you can create a test harness for a referenced subsystem, you cannot create a test harness for blocks within a referenced subsystem.

Supported

You can test a referenced model independently to isolate behavior by simulating it as a top model.

You can use a data-defined test harness, with MATLAB test vectors and direct coverage collection.

For tools that support authoring, managing, and executing systematic, simulation-based tests of subsystems, see Create or Import Test Harnesses and Select Properties (Simulink Test).

To measure how thoroughly model components are tested, see Model Coverage (Simulink Coverage).

Not supported

While you can perform SIL/PIL testing for a model that contains subsystems, you cannot simulate a subsystem independently.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

To perform SIL/PIL testing for a model reference hierarchy, see SIL and PIL Simulations (Embedded Coder).

Supported

By default, subsystem code is not reusable. To generate reusable subsystem code when possible, see Generate Subsystem Code as Separate Function and Files (Simulink Coder).

Supported

By default, subsystem code is not reusable. To generate reusable subsystem code when possible, see Generate Reusable Code from Library Subsystems Shared Across Models (Simulink Coder).

Supported

Same behavior as subsystems.

Supported

Each referenced model has one set of source code, regardless of how many times a model hierarchy includes the referenced model. Having single-sourced code can reduce the cost of verification.

Supported

While you can trace the generated code for a subsystem, if the subsystem context changes, the generated code changes. For example, a change to an input signal data type affects the subsystem code.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

You can trace the generated code for a referenced model independent of other models, which reduces the cost of verification.

With a Simulink Code Inspector™ license, you can create a traceability matrix for each referenced model. The traceability matrix provides the traceability among model objects, generated code, and model requirements. For more information, see Generate Traceability Matrices (Simulink Code Inspector).

Supported

You can specify signal properties at a subsystem interface.

For signal properties that you do not specify, subsystems inherit the signal properties from their context. Propagation of signal properties can lead to Simulink using signal properties that you do not anticipate.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

You must specify most signal properties at a referenced model interface.

Referenced models are context-independent with a defined boundary, so they do not inherit most signal properties.

Referenced models can inherit discrete sample times when the referenced model is sample-time independent.

Supported

You can specify physical connections at a subsystem interface.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Not supported

Physical connections must be fully contained within a referenced model. They cannot cross the model interface.

Supported

You can use a Simulink.Bus object, In Bus Element block, or Out Bus Element block to specify the hierarchy and properties of a bus that passes into or out of a subsystem.

Subsystems do not require the use of bus objects for virtual buses.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

You can use a Simulink.Bus object, In Bus Element block, or Out Bus Element block to specify the hierarchy and properties of a bus that passes into or out of a referenced model.

Model references do not require the use of bus objects for virtual buses when you use In Bus Element and Out Bus Element blocks.

Not supported

Subsystems use the configuration parameter settings of the model that contains them.

Not supported

Same behavior as subsystems.

Not supported

Same behavior as subsystems.

Supported

Configuration parameter settings can generally be different for a parent model and its referenced models. For compatibility information, see Set Configuration Parameters for Model Hierarchies.

Supported

You can initialize states of subsystems.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

You can initialize states from the top model using either the structure format or structure-with-time format.

Supported

Subsystems support conditional execution. For more information, see Conditionally Executed Subsystems Overview.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

Referenced models support conditional execution. For more information, see Conditionally Execute Referenced Models.

Supported

Subsystems support event-based behavior. For more information, see Using Initialize, Reinitialize, Reset, and Terminate Functions.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

Referenced models support event-based behavior. For more information, see Using Initialize, Reinitialize, Reset, and Terminate Functions.

Supported

You can define independent functions in subsystems. For more information, see Simulink Functions Overview.

Supported

Same behavior as subsystems.

Supported

Same behavior as subsystems.

Supported

You can define independent functions in a referenced model. For more information, see Export-Function Models Overview.