Main Content

systemcomposer.extractArchitectureFromSimulink

Extract architecture from Simulink model

Description

example

systemcomposer.extractArchitectureFromSimulink(model,name) exports the Simulink® model model to an architecture model name and saves it in the current directory.

systemcomposer.extractArchitectureFromSimulink(model,name,Name,Value) exports the Simulink model model to an architecture model name and saves it in the current directory with additional options.

Examples

collapse all

Export an existing Simulink® model to a System Composer™ architecture model. The algorithmic sections of the original model are removed and structural information is preserved during this process. Requirements links, if any, are also preserved.

Convert Simulink Model to System Composer Architecture

System Composer converts structural constructs in a Simulink model to equivalent architecture model constructs:

  • Subsystems to components

  • Variant subsystems to variant components

  • Bus objects to interfaces

  • Referenced models to reference components

Open the Model

Open the Simulink model of the VR Power Window Model.

slexPowerWindowStart

Figure VR Power Window Model contains objects of type hgjavacomponent, uimenu, uipanel, uitoolbar.

open_system('slexPowerWindowExample');

Export the Model

Extract an architecture model from the original model.

systemcomposer.extractArchitectureFromSimulink('slexPowerWindowExample','PowerWindowArchModel');

Figure VR Power Window Model contains objects of type hgjavacomponent, uimenu, uipanel, uitoolbar.

Simulink.BlockDiagram.arrangeSystem('PowerWindowArchModel'); 
systemcomposer.openModel('PowerWindowArchModel');

Input Arguments

collapse all

Simulink model name from which to extract the architecture, specified as a character vector or string. The model must be on the path.

Example: "slexPowerWindowExample"

Data Types: char | string

Architecture model name, specified as a character vector or string. This model is saved in the current directory.

Example: "PowerWindowArchModel"

Data Types: char | string

Name-Value Arguments

Specify optional pairs of arguments as Name1=Value1,...,NameN=ValueN, where Name is the argument name and Value is the corresponding value. Name-value arguments must appear after other arguments, but the order of the pairs does not matter.

Before R2021a, use commas to separate each name and value, and enclose Name in quotes.

Example: systemcomposer.extractArchitectureFromSimulink("slexPowerWindowExample","PowerWindowArchModel",AutoArrange=false,ShowProgress=true)

Whether to auto-arrange architecture model, specified as a logical.

Example: systemcomposer.extractArchitectureFromSimulink("slexPowerWindowExample","PowerWindowArchModel",AutoArrange=false)

Data Types: logical

Whether to show progress bar, specified as a logical. This option is useful for larger models.

Example: systemcomposer.extractArchitectureFromSimulink("slexPowerWindowExample","PowerWindowArchModel",ShowProgress=true)

Data Types: logical

More About

collapse all

Definitions

TermDefinitionApplicationMore Information
architecture

A System Composer™ architecture represents a system of components and how they interface with each other structurally and behaviorally. You can represent specific architectures using alternate views.

Different types of architectures describe different aspects of systems:

  • Functional architecture describes the flow of data in a system.

  • Logical architecture describes the intended operation of a system.

  • Physical architecture describes the platform or hardware in a system.

Compose Architecture Visually
model

A System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.

Perform operations on a model:

  • Extract the root-level architecture contained in the model.

  • Apply profiles.

  • Link interface data dictionaries.

  • Generate instances from model architecture.

A System Composer model is stored as an SLX file.

Create Architecture Model with Interfaces and Requirement Links
component

A component is a nontrivial, nearly independent, and replaceable part of a system that fulfills a clear function in the context of an architecture. A component defines an architectural element, such as a function, a system, hardware, software, or other conceptual entity. A component can also be a subsystem or subfunction.

Represented as a block, a component is a part of an architecture model that can be separated into reusable artifacts.

Components
port

A port is a node on a component or architecture that represents a point of interaction with its environment. A port permits the flow of information to and from other components or systems.

There are different types of ports:

  • Component ports are interaction points on the component to other components.

  • Architecture ports are ports on the boundary of the system, whether the boundary is within a component or the overall architecture model.

Ports
connector

Connectors are lines that provide connections between ports. Connectors describe how information flows between components or architectures.

A connector allows two components to interact without defining the nature of the interaction. Set an interface on a port to define how the components interact.

Connections

Version History

Introduced in R2019a