Main Content

createArchitectureModel

Create architecture model from component

Description

example

createArchitectureModel(component,modelName) creates an architecture model from the component component that references the model modelName.

example

createArchitectureModel(component,modelName,modelType) creates an architecture model of type modelType from the component component that references the model modelName.

Examples

collapse all

Save a component named 'robotComp' in Robot.slx and reference the model.

Create a model 'archModel.slx'.

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

Add two components named 'electricComp' and 'robotComp' to the model.

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

Save the 'robotComp' component in an architecture model so the component references the model Robot.slx.

createArchitectureModel(comp(2),'Robot');

Save a component named 'robotComp' in Robot.slx and reference the model.

Create a model 'archModel.slx'.

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

Add two components named 'electricComp' and 'robotComp' to the model.

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

Save the 'robotComp' component in a software architecture model so the component references the model Robot.slx.

createArchitectureModel(comp(2),'Robot','SoftwareArchitecture');

Input Arguments

collapse all

Component, specified as a systemcomposer.arch.Component object. The component must have an architecture with definition type composition. For other definition types, this function gives an error.

Model name, specified as a character vector or string.

Example: 'Robot'

Data Types: char | string

Type of model to save, specified as 'Architecture' for an architecture model or 'SoftwareArchitecture' for a software architecture model.

Data Types: char | string

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

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 componentA 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 compositionA 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
class diagramA 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

Introduced in R2021b