Main Content

createStateflowChartBehavior

Add Stateflow chart behavior to component

Description

example

createStateflowChartBehavior(component) adds Stateflow® Chart behavior to a component. The connections, interfaces, requirement links, and stereotypes are preserved. The component must have no sub-components and must not already be linked to a model.

Examples

collapse all

Add a Stateflow chart behavior to the component named 'robotComp' within the current model.

Create a model 'archModel.slx'.

model = systemcomposer.createModel('archModel',true);
arch = get(model,'Architecture');

Add two components to the model with the names 'electricComp' and 'robotComp'.

names = {'electricComp','robotComp'};
comp = addComponent(arch,names);

Add Stateflow chart behavior model to the 'robotComp' component.

createStateflowChartBehavior(comp(2));

Input Arguments

collapse all

Architecture component with no sub-components, specified as a systemcomposer.arch.Component object.

More About

collapse all

Definitions

TermDefinitionApplicationMore Information
architectureA 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
modelA 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.

System Composer models are stored as .slx files.

Create an Architecture Model
componentA 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 architecture 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
portA 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
connectorConnectors 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

TermDefinitionApplicationMore Information
reference componentA reference component is a component whose definition is a separate architecture model or Simulink® behavior model.A reference component represents a logical hierarchy of other compositions. You can reuse compositions in the model using reference components.
state chartA state chart diagram demonstrates the state-dependent behavior of a component throughout its state lifecycle and the events that can trigger a transition between states.Add Stateflow Chart behavior to describe an architectural component using state machines.Add Stateflow Chart Behavior to Architecture Component
sequence diagramA sequence diagram is a behavior diagram that represents the interaction between structural elements of an architecture as a sequence of message exchanges.You can use sequence diagrams to describe how the parts of a static system interact.

Introduced in R2021a