Link to an architectural definition or Simulink behavior
Use a Reference Component block to link an architectural definition of a System Composer™ component or a Simulink® behavior.
To add or connect System Composer components:
Add an architecture Reference Component from the Modeling tab or the palette. You can also click and drag a box on the canvas, selecting the Reference Component option once complete.
Add a port by selecting an edge of the component and choosing a direction from the
Click and drag the port to create a connection. Connect to another component, or have the option of creating a new component to complete the connection.
To connect the architecture Reference Component blocks to architecture or composition model root ports, drag from the component ports to the containing model boundary. When you release the connection, a root port is created at the boundary.
To manage Reference Component contents:
Upon creating a Reference Component, you have the option to
right-click on the component and select
From here, you can specify your reference model name, if it already exists. The
reference model can be a System Composer architecture model or a Simulink model.
With a regular Component block, you can right-click on the block and convert it into a reference component.
Save As Architecture Model to save the
contents of the component as an architecture model that can be referenced in
multiple places and kept in sync. The component will become a reference component
that links to the referenced architecture model.
Create Simulink Behavior to create a new
Simulink reference model and link to it.
Link to Model to link to a known model that
can be either a System Composer architecture model or a Simulink model.
To break the reference link for a Reference Component, you have the
option to right-click and select
Inline Model which inlines
the contents of the architecture model referenced by the specified component and breaks
the link to the reference model. The Reference Component becomes a
regular Component block.
Source— Input connection from another component
If you connect to a source component, the interfaces on the ports are shared.
Destination— Output connection to another component
If you connect to a destination component, the interfaces on the ports are shared.
|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:
|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:
System Composer models are stored as
|Create an Architecture Model|
|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 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|
|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:
|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|
|reference component||A 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 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 an architectural component using state machines.||Add Stateflow Chart Behavior to Architecture Component|
|sequence diagram||A 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.|