Main Content

createSubsystemBehavior

Add subsystem behavior to component

    Description

    example

    createSubsystemBehavior(component) adds subsystem 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

    To create a new Simulink® model with the same interface as the component and link the component to the new model, use the createSimulinkBehavior function.

    Examples

    collapse all

    Add subsystem 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 subsystem behavior model to the 'robotComp' component.

    createSubsystemBehavior(comp(2));

    Input Arguments

    collapse all

    Component with no subcomponents, 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 with Interfaces and Requirement Links
    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
    physical subsystemA physical subsystem is a Simulink subsystem with Simscape™ connections.A physical subsystem with Simscape connections uses a physical network approach suited for simulating systems with real physical components and represents a mathematical model.Describe Component Behavior Using Simscape
    physical portA physical port represents a Simscape physical modeling connector port called a Connection Port (Simscape).Use physical ports to connect components in an architecture model or to enable physical systems in a Simulink subsystem.Define Physical Ports on a Component
    physical connector

    A physical connector can represent a nondirectional conserving connection of a specific physical domain. Connectors can also represent physical signals.

    Use physical connectors to connect physical components that represent features of a system to simulate mathematically.Architecture Model with Simscape Behavior for a DC Motor
    physical interface

    A physical interface defines the kind of information that flows through a physical port. The same interface can be assigned to multiple ports. A physical interface is a composite interface equivalent to a Simulink.ConnectionBus object that specifies at least one Simulink.ConnectionElement object.

    Use a physical interface to bundle physical elements to describe a physical model using at least one physical domain.Specify Physical Interfaces on the Ports
    physical element

    A physical element describes the decomposition of a physical interface. A physical element is equivalent to a Simulink.ConnectionElement object.

    Define the Type of a physical element as a physical domain to enable use of that domain in a physical model.Describe Component Behavior Using Simscape

    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.
    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 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 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.
    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 R2021b