Main Content

removeProperty

Remove property from stereotype

Description

example

removeProperty(stereotype,propertyName) removes a property from the stereotype.

Examples

collapse all

Add a component stereotype and add a VoltageRating property with value 5. Then remove the property.

profile = systemcomposer.profile.Profile.createProfile("myProfile");
stereotype = addStereotype(profile,"electricalComponent",AppliesTo="Component")
property = addProperty(stereotype,"VoltageRating",DefaultValue="5");
removeProperty(stereotype,"VoltageRating")

Input Arguments

collapse all

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

Name of property to be removed, specified as a character vector or string.

Data Types: char | string

More About

collapse all

Definitions

TermDefinitionApplicationMore Information
stereotype

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, and functions. Functions only apply to software architectures. 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
property

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.

profile

A profile is a package of stereotypes 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 profile or in several. When you save profiles, they are stored in XML files.

Version History

Introduced in R2019a