Find stereotype by name
Find a stereotype in the small UAV (unmanned aerial vehicle) model.
scExampleSmallUAV stereotype = systemcomposer.profile.Stereotype.find("UAVComponent.OnboardElement")
stereotype = Stereotype with properties: Name: 'OnboardElement' Description: 'Represents the base component of UAVComponent' Parent: [0x0 systemcomposer.profile.Stereotype] AppliesTo: 'Component' Abstract: 0 Icon: 'network' ComponentHeaderColor: [210 210 210] ConnectorLineColor: [168 168 168] ConnectorLineStyle: 'Default' FullyQualifiedName: 'UAVComponent.OnboardElement' Profile: [1x1 systemcomposer.profile.Profile] OwnedProperties: [1x3 systemcomposer.profile.Property] Properties: [1x3 systemcomposer.profile.Property]
name — Name of stereotype
character vector | string
Name of stereotype, specified as a character vector or string in the form
stereotype — Found stereotype
Found stereotype, returned as a
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