Open Architecture Views Gallery
Open Views Editor
Open the keyless entry system example and create a view.
openProject("scKeylessEntrySystem"); model = systemcomposer.loadModel("KeylessEntryArchitecture"); fobSupplierView = model.createView("FOB Locator System Supplier Breakdown",... Color="lightblue");
Open the Architecture Views Gallery for the model.
A System Composer™ architecture represents a system of components and how they interface with each other structurally and behaviorally.
Different types of architectures describe different aspects of systems. You can use views to visualize a subset of components in an architecture. You can define parameters on the architecture level using the Parameter Editor.
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. Transfer information between components with:
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.
These 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 view shows a customizable subset of elements in a model. Views can be filtered based on stereotypes or names of components, ports, and interfaces, along with the name, type, or units of an interface element. Create views by adding elements manually. Views create a simplified way to work with complex architectures by focusing on certain parts of the architectural design.
You can use different types of views to represent the system. Switch between a component diagram, component hierarchy, or architecture hierarchy. For software architectures, you can switch to a class diagram view.
A viewpoint represents a stakeholder perspective that specifies the contents of the view.
An element group is a grouping of components in a view.
Use element groups to programmatically populate a view.
A query is a specification that describes certain constraints or criteria to be satisfied by model elements.
Use queries to search elements with constraint criteria and to filter views.
|Find Elements in Model Using Queries
A component diagram represents a view with components, ports, and connectors based on how the model is structured.
Component diagrams allow you to programmatically or manually add and remove components from the view.
|Inspect Components in Custom Architecture Views
You can visualize a hierarchy diagram as a view with components, ports, reference types, component stereotypes, and stereotype properties.
There are two types of hierarchy diagrams:
|Display Component Hierarchy and Architecture Hierarchy Using Views
Introduced in R2019b