systemcomposer.extractArchitectureFromSimulink - Extract architecture from Simulink model - MATLAB (original) (raw)
Extract architecture from Simulink model
Syntax
Description
systemcomposer.extractArchitectureFromSimulink([model](#mw%5F34726730-73b7-4c2b-a429-75824bc0d599),[name](#mw%5F93c919cc-1acb-4844-9b82-68ad26ee155d)) exports the Simulink® model model to an architecture modelname and saves it in the current directory.
systemcomposer.extractArchitectureFromSimulink([model](#mw%5F34726730-73b7-4c2b-a429-75824bc0d599),[name](#mw%5F93c919cc-1acb-4844-9b82-68ad26ee155d),[Name=Value](#namevaluepairarguments)) exports the Simulink model model to an architecture modelname and saves it in the current directory with additional options.
Examples
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 present, are also preserved.
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 Simulink model of F-14 Flight Control.
Extract an architecture model from the original model.
systemcomposer.extractArchitectureFromSimulink('f14','F14ArchModel'); Simulink.BlockDiagram.arrangeSystem('F14ArchModel'); systemcomposer.openModel('F14ArchModel');
Input Arguments
Simulink model name from which to extract the architecture, specified as a character vector or string. The model must be on the path.
Example: "f14"
Data Types: char | string
Architecture model name, specified as a character vector or string. This model is saved in the current directory.
Example: "F14ArchModel"
Data Types: char | string
Name-Value Arguments
Specify optional pairs of arguments asName1=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("f14","F14ArchModel",AutoArrange=false,ShowProgress=true)
Whether to auto-arrange architecture model, specified as 1 (true) or 0 (false).
Example: systemcomposer.extractArchitectureFromSimulink("f14","F14ArchModel",AutoArrange=false)
Data Types: logical
Whether to show progress bar, specified as 1 (true) or 0 (false). This option is useful for larger models.
Example: systemcomposer.extractArchitectureFromSimulink("f14","F14ArchModel",ShowProgress=true)
Data Types: logical
More About
| Term | Definition | Application | More Information |
|---|---|---|---|
| Architecture | A System Composer™ architecture represents a system of components and how they interface with each other structurally and behaviorally. | Different types of architectures describe different aspects of systems. You can use views to visualize a subset of components in an architecture. You can define parameters on the architecture level using the Parameter Editor. | Compose Architectures VisuallyAuthor Parameters in System Composer Using Parameter Editor |
| Root | A root is at the top of an architecture hierarchy. A root architecture has a boundary defined by its architecture ports that surround the system of interest. | The root architecture has a system boundary surrounding your architecture model. You can add architecture ports that define interfaces across the boundary. | Compose Architectures Visually |
| Model | A System Composer model is the file that contains architectural information, such as components, ports, connectors, interfaces, and behaviors. | Perform operations on a model including extracting root-level architecture, applying profiles, linking interface data dictionaries, or generating 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 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, another 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. Transfer information between components with port interfaces using the Interface Editor, and parameters using the Parameter Editor. | Compose Architectures Visually |
| 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. | 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. The root architecture has a boundary defined by its ports. | Compose Architectures Visually |
| 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. | Compose Architectures Visually |
Version History
Introduced in R2019a