Get evaluated value of property from component
Get Evaluated Property Value
Create a profile, add a component stereotype, and add a property with a default value.
profile = systemcomposer.profile.Profile.createProfile('LatencyProfile'); stereotype = addStereotype(profile,'electricalComponent','AppliesTo','Component'); stereotype.addProperty('latency','Type','double','DefaultValue','10');
Create a model with a component.
model = systemcomposer.createModel('archModel'); arch = get(model,'Architecture'); comp = addComponent(arch,'Component');
Apply the profile to the model and apply the stereotype to the component. Open the profile editor.
model.applyProfile('LatencyProfile'); comp.applyStereotype('LatencyProfile.electricalComponent'); systemcomposer.profile.editor(profile)
Get the property value
value = getEvaluatedPropertyValue(comp,'LatencyProfile.electricalComponent.latency')
value = 10
element — Model element
architecture object | component object | port object | connector object | physical connector object | data interface object | value type object | physical interface object
Model element, specified as a
property — Property name
character vector | string
Property name, specified as a character vector or string in the form
value — Property value
double (default) |
enumeration class name
Property value, returned as a data type that depends on how the property is defined in the profile.
|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.|