Main Content

createSimulinkBehavior

Create Simulink behavior and link to component

Description

example

createSimulinkBehavior(component,modelName) creates a new Simulink® model, modelName, with the same interfaces as the component component and links the component to the new model. The component must have no children.

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 subsystem component behaviors.

If no functions are present in software architectures, this syntax creates a rate-based behavior. If functions are present, the syntax creates an export-function behavior.

example

createSimulinkBehavior(component,modelName,"Type",type) creates a new Simulink model or subsystem behavior, modelName, with the same interfaces as the component component and links the component to the new model. For more information, see Create Referenced Simulink Behavior Model.

Use this syntax to convert a subsystem component to a subsystem reference.

example

createSimulinkBehavior(component,"Type",type) creates a subsystem component behavior that is part of the parent model. The connections, interfaces, requirement links, and stereotypes of the component are preserved. The component must have no subcomponents and must not already be linked to a model. For more information, see Create Simulink Subsystem Behavior Using Subsystem Component.

example

createSimulinkBehavior(component,modelName,"BehaviorType",behavior) creates a new Simulink rate-based or export-function behavior, modelName, and links the software component to the new model. You can create rate-based or export-function behaviors for software architectures.

Examples

collapse all

Create a Simulink model behavior for the component robotComp in Robot.slx and link the model file to the component.

Create a model archModel.

model = systemcomposer.createModel("archModel",true);
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")

Create a Simulink behavior model for the robotComp component so the component references the Simulink model Robot.slx.

createSimulinkBehavior(comp(2),"Robot")

Create a Simulink subsystem behavior for the component robotComp in Robot.slx and link the subsystem file to the component.

Create a model archModel.

model = systemcomposer.createModel("archModel",true);
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")

Create a Simulink subsystem reference behavior for the robotComp component so the component references the Simulink subsystem Robot.slx.

createSimulinkBehavior(comp(2),"Robot",Type="SubsystemReference")

Create a Simulink subsystem behavior for the component robotComp in Robot.slx and link the subsystem file to the component.

Create a model archModel.

model = systemcomposer.createModel("archModel",true);
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")

Create a Simulink subsystem component behavior for the robotComp component that is part of the parent model.

createSimulinkBehavior(comp(2),Type="Subsystem")

Convert the subsystem component to a subsystem reference component behavior so the component references the Simulink subsystem Robot.slx.

createSimulinkBehavior(comp(2),"Robot",Type="SubsystemReference")

Create a Simulink model with export-function behavior myBehaviorModel.slx for the software component named C1 and link the model to the component.

Create a software architecture model named mySoftwareModel.

model=systemcomposer.createModel("mySoftwareModel","SoftwareArchitecture",true);
arch = get(model,"Architecture");

Add a component C1 to the model.

comp = addComponent(arch,"C1");

Create a Simulink model with an export-function behavior named myBeheaviorModel.slx that is referenced by the component C1.

createSimulinkBehavior(comp,"myBehaviorModel",BehaviorType="ExportFunction")

Input Arguments

collapse all

System or software architecture component with no children, specified as a systemcomposer.arch.Component object. This component can also be specified as a subsystem component to be converted to a subsystem reference.

Model name of the Simulink model to be created, specified as a character vector or string.

Example: "Robot"

Data Types: char | string

Component behavior, specified as one of these values:

  • "RateBased" to create a rate-based component behavior

  • "ExportFunction" to create an export-function component behavior

Data Types: char | string

Component behavior, specified as one of these values:

  • "ModelReference" to create a Simulink model reference component behavior

  • "SubsystemReference" to create a Simulink subsystem reference component behavior

  • "Subsystem" to create a Simulink subsystem component behavior

Data Types: char | string

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

TermDefinitionApplicationMore Information
reference component

A reference component is a component whose definition is a separate architecture model, Simulink behavior model, or Simulink subsystem behavior. A reference component represents a logical hierarchy of other compositions.

You can reuse compositions in the model using reference components. There are three types of reference components:

  • Model references are Simulink models.

  • Subsystem references are Simulink subsystems.

  • Architecture references are System Composer architecture models.

parameter definition

A parameter definition is the definition of a property that has instance semantics. A parameter definition specifies attributes such as name, data type, default value, and units.

Parameter definitions can be specified as model arguments on a Simulink model or a System Composer architecture model.

Access Model Arguments as Parameters on Reference Components
parameter

A parameter is an instance-specific value of a parameter definition. A parameter captures instance-specific values and units.

Parameters are available for each component linking to a model reference or architecture reference that specifies model arguments. You can specify independent values for a parameter on each component.

Use Parameters to Store Instance Values with Components
subsystem component

A subsystem component is a Simulink subsystem that is part of the parent System Composer architecture model.

Add Simulink subsystem behavior to a component to author a subsystem component in System Composer. You cannot synchronize and reuse subsystem components as Reference Component blocks because the component is part of the parent model.

state chart

A 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 a component using state machines. You cannot synchronize and reuse Stateflow chart behaviors as Reference Component blocks because the component is part of the parent model.

TermDefinitionApplicationMore Information
software architecture

A software architecture is a specialization of an architecture for software-based systems, including the description of software compositions, component functions, and their scheduling.

Use software architectures in System Composer to author software architecture models composed of software components, ports, and interfaces. Design your software architecture model, define the execution order of your component functions, simulate your design in the architecture level, and generate code.

software component

A software component is a specialization of a component for software entities, including its functions (entry points) and interfaces.

Implement a Simulink export-function, rate-based, or JMAAB model as a software component, simulate the software architecture model, and generate code.

software composition

A software composition is a diagram of software components and connectors that represents a composite software entity, such as a module or application.

Encapsulate functionality by aggregating or nesting multiple software components or compositions.

Modeling the Software Architecture of a Throttle Position Control System
software function

A software function is an entry point that can be defined in a software component.

You can apply stereotypes to software functions, edit sample times, and specify the function period using the Functions Editor.

Author and Extend Functions for Software Architectures
class diagram

A class diagram is a graphical representation of a static structural model that displays unique architecture types of the software components optionally with software methods and properties.

Class diagrams capture one instance of each referenced model and show relationships between them. Any component diagram view can be optionally represented as a class diagram for a software architecture model.

Class Diagram View of Software Architectures

Version History

Introduced in R2019a