hasProperty
Description
Examples
Get the weight
property from a component with the
sysComponent
stereotype applied.
Create a model with a component called Component
.
model = systemcomposer.createModel("archModel"); systemcomposer.openModel("archModel"); arch = get(model,"Architecture"); comp = addComponent(arch,"Component");
Create a profile with a stereotype and a property, then apply the profile to the model.
profile = systemcomposer.profile.Profile.createProfile("sysProfile"); base = profile.addStereotype("sysComponent"); base.addProperty("weight",Type="double",DefaultValue="10",Units="g"); model.applyProfile("sysProfile")
Apply the stereotype to the component, then set a new weight property.
applyStereotype(comp,"sysProfile.sysComponent") setProperty(comp,"sysProfile.sysComponent.weight","5","g")
Find if the weight property exists on the component.
result = hasProperty(comp,"sysProfile.sysComponent.weight")
result = logical 1
Input Arguments
Architectural element, specified as one these objects:
Property, specified as a character vector or string in the form
"<profile>.<stereotype>.<property>"
.
Data Types: char
| string
Output Arguments
Query result, returned as 1
(true
) or 0
(false
).
Data Types: logical
More About
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. | |
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. | |
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. | |
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. | |
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. |
Term | Definition | Application | More Information |
---|---|---|---|
Stereotype | Stereotypes provide a mechanism to extend the core language elements and add domain-specific metadata. | Apply stereotypes to core element types. An element can have multiple stereotypes. Stereotypes allow you to style different elements. Stereotypes provide elements with a common set of properties, such as mass, cost, and power. | |
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. For more information, see Use Property Inspector in System Composer. | |
Profile | A profile is a package of stereotypes. | You can use profiles to create a domain of specialized 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. |
Term | Definition | Application | More Information |
---|---|---|---|
Data dictionary | A data dictionary is a repository of data relevant to your model. The Architectural Data section of a data dictionary stores shared definitions used in Simulink® and architecture model interfaces, such as port interfaces, data types, and system wide constants. For more information, see What Is a Data Dictionary? | You can save local interfaces on a System Composer model to the Architectural Data section of a Simulink data dictionary using the Interface Editor. In addition to the Interface Editor, you can also use the Architectural Data Editor to manage and modify interfaces and value types. | |
Data interface | A data interface defines the kind of information that flows through a port. The same interface can be assigned to multiple ports. A data interface can be composite, meaning that it can include data elements that describe the properties of an interface signal. | Data interfaces represent the information that is shared through a connector and enters or exits a component through a port. Use the Interface Editor to create and manage data interfaces and data elements and store them in a data dictionary for reuse between models. | |
Data element | A data element describes a portion of an interface, such as a communication message, a calculated or measured parameter, or other decomposition of that interface. | Data interfaces are decomposed into data elements that can represent pins or wires in a connector or harness, messages transmitted across a bus, and data structures shared between components. | |
Value type | A value type can be used as a port interface to define the atomic piece of data that flows through that port and has a top-level type, dimension, unit, complexity, minimum, maximum, and description. | You can also assign the type of data elements in data interfaces to value types. Add value types to data dictionaries using the Interface Editor so that you can reuse the value types as interfaces or data elements. | Create Value Types as Interfaces |
Owned interface | An owned interface is an interface that is local to a specific port and not shared in a data dictionary or the model dictionary. | Create an owned interface to represent a value type or data interface that is local to a port. | Define Owned Interfaces Local to Ports |
Adapter | An adapter connects two components with incompatible port interfaces by mapping between the two interfaces. An adapter can act as a unit delay, rate transition, or merge. You can also use an adapter for bus creation. Use the Adapter block to implement an adapter. | With an adapter, on the Interface Adapter dialog box, you
can: create and edit mappings between input and output interfaces, apply an interface conversion
|
Term | Definition | Application | More Information |
---|---|---|---|
Physical subsystem | A physical subsystem is a Simulink subsystem with Simscape™ connections. | A physical subsystem with Simscape connections uses a physical network approach suited for simulating systems with real physical components and represents a mathematical model. | Implement Component Behavior Using Simscape |
Physical port | A physical port represents a Simscape physical modeling connector port called a Connection Port (Simscape). | Use physical ports to connect components in an architecture model or to enable physical systems in a Simulink subsystem. | Define Physical Ports on Component |
Physical connector | A physical connector can represent a nondirectional conserving connection of a specific physical domain. Connectors can also represent physical signals. | Use physical connectors to connect physical components that represent features of a system to simulate mathematically. | Architecture Model with Simscape Behavior for a DC Motor |
Physical interface | A physical interface defines the kind of information that flows through a physical port. The same interface can be assigned to multiple ports. A physical interface is a composite interface equivalent to a | Use a physical interface to bundle physical elements to describe a physical model using at least one physical domain. | Specify Physical Interfaces on Ports |
Physical element | A physical element describes the decomposition of a physical interface. A physical element is equivalent to a | Define the | Describe Component Behavior Using Simscape |
Version History
Introduced in R2021a
See Also
Tools
Blocks
Objects
systemcomposer.profile.Profile
|systemcomposer.profile.Stereotype
|systemcomposer.profile.Property
Functions
systemcomposer.profile.Profile.createProfile
|systemcomposer.loadProfile
|applyProfile
|removeProfile
|renameProfile
|systemcomposer.profile.editor
|systemcomposer.profile.Profile.find
|systemcomposer.profile.Profile.load
|save
|open
|close
|systemcomposer.profile.Profile.closeAll
|systemcomposer.profile.Stereotype.find
|getDefaultStereotype
|setDefaultStereotype
|getDefaultElementStereotype
|setDefaultElementStereotype
|addStereotype
|removeStereotype
|getStereotype
|applyStereotype
|batchApplyStereotype
|getStereotypes
|changeStereotype
|removeStereotype
|hasStereotype
|addProperty
|removeProperty
|setProperty
|getProperty
|getPropertyValue
|getEvaluatedPropertyValue
|getStereotypeProperties
|applyStereotypeOrder
|getStereotypeNamesByOrder
|increaseStereotypeOrder
|decreaseStereotypeOrder
MATLAB Command
You clicked a link that corresponds to this MATLAB command:
Run the command by entering it in the MATLAB Command Window. Web browsers do not support MATLAB commands.
Select a Web Site
Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select: United States.
You can also select a web site from the following list
How to Get Best Site Performance
Select the China site (in Chinese or English) for best site performance. Other MathWorks country sites are not optimized for visits from your location.
Americas
- América Latina (Español)
- Canada (English)
- United States (English)
Europe
- Belgium (English)
- Denmark (English)
- Deutschland (Deutsch)
- España (Español)
- Finland (English)
- France (Français)
- Ireland (English)
- Italia (Italiano)
- Luxembourg (English)
- Netherlands (English)
- Norway (English)
- Österreich (Deutsch)
- Portugal (English)
- Sweden (English)
- Switzerland
- United Kingdom (English)