Apply stereotype to all elements in architecture
Apply Stereotype to All Connectors
Create a profile, add a connector stereotype, and add a property with a default value. Open the Profile Editor to inspect the profile.
profile = systemcomposer.profile.Profile.createProfile("LatencyProfile"); stereotype = addStereotype(profile,"standardConn",AppliesTo="Connector"); stereotype.addProperty("latency",Type="double",DefaultValue="10"); systemcomposer.profile.editor(profile)
Create a model with three components, ports, and connectors between them. Improve the model layout.
modelName = "archModel"; arch = systemcomposer.createModel(modelName,true); rootArch = get(arch,"Architecture"); names = ["Component1","Component2","Component3"]; newComponents = addComponent(rootArch,names); outPort1 = addPort(newComponents(1).Architecture,"testSig1","out"); inPort1 = addPort(newComponents(2).Architecture,"testSig1","in"); outPort2 = addPort(newComponents(2).Architecture,"testSig2","out"); inPort2 = addPort(newComponents(3).Architecture,"testSig2","in"); conn1 = connect(newComponents(1),newComponents(2)); conn2 = connect(newComponents(2),newComponents(3)); Simulink.BlockDiagram.arrangeSystem(modelName)
Apply the profile to the model.
Apply the connector stereotype to all the connectors in the architecture
rootArch. Inspect the connectors in the Property Inspector to
confirm the applied stereotypes.
arch — Architecture
Architecture, specified as a
elementType — Element type
Element type, specified as
"Function". The element type
only available for software architectures.
stereotype — Stereotype to apply
character vector | string
Stereotype to apply, specified as a character vector or string in the form
"<profile>.<stereotype>". This stereotype must be applicable
for the element type.
flag — Whether to apply stereotype recursively
false or 0 (default) |
true or 1
Whether to apply stereotype recursively, specified as a logical. If
flag is 1 (
true), the stereotype is applied to
the elements in the architecture and its sub-architectures.
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:
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.
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 stereotype is a custom extension of the modeling language. Stereotypes provide a mechanism to extend the architecture language elements by adding domain-specific metadata.
Apply stereotypes to model elements such as root-level architecture, component architecture, connectors, ports, data interfaces, value types, functions, requirements, and links. Functions only apply to software architectures. You must have a Requirements Toolbox™ license to apply stereotypes to requirements and links. A model element can have multiple stereotypes. Stereotypes provide model elements with a common set of property fields, such as mass, cost, and power.
|Extend Architectural Design Using Stereotypes|
A property is a field in a stereotype. You can specify property values for each element to which the stereotype is applied.
Use properties to store quantitative characteristics, such as weight or speed, that are associated with a model element. Properties can also be descriptive or represent a status. You can view and edit the properties of each element in the architecture model using the Property Inspector.
A profile is a package of stereotypes that you can use to create a self-consistent domain of element types.
Author profiles and apply profiles to a model using the Profile Editor. You can store stereotypes for a project in one or several profiles. When you save profiles, they are stored in XML files.
Introduced in R2019a