Create System Composer model
Create a model, open it, and display its properties.
model = systemcomposer.createModel("model_name",true)
model = model with properties: Name: 'model_name' Architecture: [1×1 systemcomposer.arch.Architecture] SimulinkHandle: 2.0005 Views: [0×0 systemcomposer.view.ViewArchitecture] Profiles: [0×0 systemcomposer.profile.Profile] InterfaceDictionary: [1×1 systemcomposer.interface.Dictionary]
modelName — Name of new model
character vector | string
Name of new model, specified as a character vector or string. This name must be a valid MATLAB® identifier.
openFlag — Whether to open model
false or 0 (default) |
true or 1
Whether to open model upon creation, specified as a logical.
modelType — Type of model
"Architecture" (default) |
Type of model to create, specified as
"Architecture" for an
architecture model or
"SoftwareArchitecture" for a software
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|
A System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.
Perform operations on a model:
A System Composer model is stored as an SLX file.
|Create Architecture Model with Interfaces and Requirement Links|
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.
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:
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.
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.
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.
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|
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|
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|