Main Content


Remove stereotype from profile

Since R2019a



removeStereotype(profile,stereotype) removes a stereotype from the specified profile.


collapse all

Create a profile, add a component stereotype to the profile, open the Profile Editor, and remove the stereotype from the profile.

profile = systemcomposer.profile.Profile.createProfile("LatencyProfile");
stereotype = addStereotype(profile,"electricalComponent",AppliesTo="Component");

Input Arguments

collapse all

Profile, specified as a systemcomposer.profile.Profile object.

Stereotype to remove, specified as a systemcomposer.profile.Stereotype object or by name as a character vector or string.

Example: "electricalComponent"

Data Types: char | string

More About

collapse all


TermDefinitionApplicationMore Information

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.

Version History

Introduced in R2019a