getDefaultElementStereotype - Get default stereotype for elements - MATLAB (original) (raw)

Get default stereotype for elements

Since R2021b

Syntax

Description

[stereotype](#mw%5Fb7f6cf97-1c15-423e-af19-30d12a80fc32%5Fsep%5Fmw%5F7965c94c-9a05-44d8-b9cb-6969fea14317) = getDefaultElementStereotype([stereotype](#mw%5Fb7f6cf97-1c15-423e-af19-30d12a80fc32%5Fsep%5Fmw%5F7965c94c-9a05-44d8-b9cb-6969fea14317),[elementType](#mw%5Fb7f6cf97-1c15-423e-af19-30d12a80fc32%5Fsep%5Fmw%5Fb134ab37-496a-4d12-bfb0-23d77ab31022)) gets the default stereotype stereotype of the child elements whose parent element of type elementType has the stereotypestereotype applied.

example

Examples

collapse all

Create a profile for latency characteristics and save it.

profile = systemcomposer.profile.Profile.createProfile("LatencyProfile");

latencybase = profile.addStereotype("LatencyBase"); latencybase.addProperty("latency",Type="double"); latencybase.addProperty("dataRate",Type="double",DefaultValue="10");

connLatency = profile.addStereotype("ConnectorLatency",... Parent="LatencyProfile.LatencyBase"); connLatency.addProperty("secure",Type="boolean"); connLatency.addProperty("linkDistance",Type="double");

nodeLatency = profile.addStereotype("NodeLatency",... Parent="LatencyProfile.LatencyBase"); nodeLatency.addProperty("resources",Type="double",DefaultValue="1");

portLatency = profile.addStereotype("PortLatency",... Parent="LatencyProfile.LatencyBase"); portLatency.addProperty("queueDepth",Type="double"); portLatency.addProperty("dummy",Type="int32");

profile.save

Specify the LatencyProfile.NodeLatency stereotype as a component stereotype. Set the default component stereotype.

nodeLatency.AppliesTo = "Component"; nodeLatency.setDefaultElementStereotype("Component","LatencyProfile.NodeLatency")

Get the default component stereotype on nodeLatency.

stereotype = getDefaultElementStereotype(nodeLatency,"Component")

stereotype =

Stereotype with properties:

                Name: 'NodeLatency'
         Description: ''
              Parent: [1×1 systemcomposer.profile.Stereotype]
           AppliesTo: 'Component'
            Abstract: 0
                Icon: 'default'
ComponentHeaderColor: [210 210 210]
  ConnectorLineColor: [168 168 168]
  ConnectorLineStyle: 'Default'
  FullyQualifiedName: 'LatencyProfile.NodeLatency'
             Profile: [1×1 systemcomposer.profile.Profile]
     OwnedProperties: [1×1 systemcomposer.profile.Property]
          Properties: [1×3 systemcomposer.profile.Property]

Output Arguments

More About

collapse all

Term Definition Application More Information
Architecture 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. Compose Architectures VisuallyAuthor Parameters in System Composer Using Parameter Editor
Root A root is at the top of an architecture hierarchy. A root architecture has a boundary defined by its architecture ports that surround the system of interest. The root architecture has a system boundary surrounding your architecture model. You can add architecture ports that define interfaces across the boundary. Compose Architectures Visually
Model A System Composer model is the file that contains architectural information, such as components, ports, connectors, interfaces, and behaviors. Perform operations on a model including extracting root-level architecture, applying profiles, linking interface data dictionaries, or generating instances from model architecture. A System Composer model is stored as an SLX file. Create Architecture Model with Interfaces and Requirement Links
Component A component is a 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, another 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 port interfaces using the Interface Editor, and parameters using the Parameter Editor. Compose Architectures Visually
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. 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. The root architecture has a boundary defined by its ports. Compose Architectures Visually
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. Compose Architectures Visually

Version History

Introduced in R2021b

See Also

Tools

Blocks

Objects

Functions

Topics