Find if element has property
weight property from a component with the
sysComponent stereotype applied.
Create a model with a component called
model = systemcomposer.createModel('archModel',true); arch = get(model,'Architecture'); comp = addComponent(arch,'Component');
Create a profile with a stereotype, 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.
Find if the weight property exists on the component.
result = hasProperty(comp,'sysProfile.sysComponent.weight')
result = logical 1
element— Architecture model element
Architecture model element, specified as one of these objects:
Property, specified as a character vector or string in the form
result— Query result
trueor 1 |
Query result, returned as a logical.
|architecture||A System Composer™ architecture represents a system of components and how they interface with each other structurally and behaviorally. You can represent specific architectures using alternate views.|
Different types of architectures describe different aspects of systems:
|Compose Architecture Visually|
|model||A System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.|
Perform operations on a model:
System Composer models are stored as SLX files.
|Create an Architecture Model with Interfaces and Requirement Links|
|component||A component is a nontrivial, nearly independent, and replaceable part of a system that fulfills a clear function in the context of an architecture. A component defines an architecture element, such as a function, a 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.||Components|
|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.|
There are different types of 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.||Connections|
|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 elements: root-level architecture, component architecture, connectors, ports, data interfaces, and value types of a model. 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. For each element the stereotype is applied to, specific property values are specified.||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. Profiles are stored in XML files when they are saved.|
|interface data dictionary||An interface data dictionary is a consolidated list of all the interfaces and value types in an architecture and where they are used.|
Local interfaces on a System Composer model can be saved in an interface data dictionary using the Interface Editor.
Interface dictionaries can be reused between models that need to use a given set of interfaces, elements, and value types. Data dictionaries are stored in separate SLDD files.
|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 an interface data dictionary for reuse between models.||Create an Architecture Model with Interfaces and Requirement Links|
|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:
|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 a locally defined 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 helps connect two components with incompatible port interfaces by mapping between the two interfaces. An adapter can also act as a unit delay or rate transition. Use the Adapter block to implement an adapter.|
With an adapter, you can perform functions on the Interface Adapter dialog:
|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.||Describe 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 a Component|
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|
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 the Ports|
A physical element describes the decomposition of a physical interface. A physical
element is equivalent to a
|Define the ||Describe Component Behavior Using Simscape|