createStateflowChartBehavior - Add Stateflow chart behavior to component - MATLAB (original) (raw)
Main Content
Add Stateflow chart behavior to component
Since R2021a
Syntax
Description
createStateflowChartBehavior([component](#mw%5Fc934da0d-c1c8-43d3-b849-1392791e1135))
adds Stateflow® Chart behavior to a component component
. The connections, interfaces, requirement links, and stereotypes are preserved. The component must have no subcomponents and must not already be linked to a model.
Note
Components with physical ports cannot be saved as architecture models, model references, software architectures, or Stateflow chart behaviors. Components with physical ports can only be saved as subsystem references or as subsystem component behaviors.
Examples
Add Stateflow chart behavior to the component named "robotComp"
within the current model.
Create a model named "archModel"
.
model = systemcomposer.createModel("archModel"); systemcomposer.openModel("archModel"); arch = get(model,"Architecture");
Add two components to the model electricComp
and robotComp
. Rearrange the model.
names = ["electricComp","robotComp"]; comp = addComponent(arch,names); Simulink.BlockDiagram.arrangeSystem("archModel")
Add Stateflow chart behavior to the robotComp
component.
createStateflowChartBehavior(comp(2));
Input Arguments
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 R2021a
See Also
Blocks
Functions
- inlineComponent | createSimulinkBehavior | createArchitectureModel | createArchitectureSubsystem | extractArchitectureFromSimulink | linkToModel | linkToFMU | isFMU | isReference | isProtected
Topics
- Overview of System Composer API
- Implement Component Behavior Using Simulink
- Decompose and Reuse Components
- Implement Component Behavior Using Stateflow Charts
- Implement Component Behavior Using Simscape
- Use FMU Components with Architectural Data in Architecture Models
- Simulate and Deploy Software Architectures