Property

Create query to select non-evaluated values for object properties or stereotype properties for elements

Since R2019b

Syntax

query = Property(name)

Description

query = Property(name) creates a query query that the find and createView functions use to select non-evaluated values for object properties or stereotype properties for elements based on a specified property name name.

Examples

Find Model Elements that Satisfy Property

Import the package that contains all of the System Composer™ queries.

import systemcomposer.query.*

Open the Simulink® project file for the keyless entry system.

scKeylessEntrySystem

Load the architecture model.

model = systemcomposer.loadModel("KeylessEntryArchitecture");

Create a query to find components that contain Sensor in their Name property and run the query, displaying the first.

constraint = contains(Property("Name"),"Sensor");
sensors = find(model,constraint,Recurse=true,IncludeReferenceModels=true);
query = sensors(1)

query = 1x1 cell array
    {'KeylessEntryArchitecture/Door Lock//Unlock System/Rear Pass Door Lock Sensor/Door Lock Sensor'}

Input Arguments

name — Property name

character vector | string

Property name for model element, specified in the form "<profile>.<stereotype>.<property>" or any property on the designated class.

Example: "Name"

Example: "AutoProfile.BaseComponent.Latency"

Data Types: char

Output Arguments

query — Query

query constraint object

Query, returned as a systemcomposer.query.Constraint object.

More About

Definitions

Term	Definition	Application	More Information
view	A view shows a customizable subset of elements in a model. Views can be filtered based on stereotypes or names of components, ports, and interfaces, along with the name, type, or units of an interface element. Create views by adding elements manually. Views create a simplified way to work with complex architectures by focusing on certain parts of the architectural design.	You can use different types of views to represent the system. Switch between a component diagram, component hierarchy, or architecture hierarchy. For software architectures, you can switch to a class diagram view. A viewpoint represents a stakeholder perspective that specifies the contents of the view.	Modeling System Architecture of Keyless Entry System
element group	An element group is a grouping of components in a view.	Use element groups to programmatically populate a view.	Create Architecture Views Interactively Create Architectural Views Programmatically
query	A query is a specification that describes certain constraints or criteria to be satisfied by model elements.	Use queries to search elements with constraint criteria and to filter views.	Find Elements in Model Using Queries
component diagram	A component diagram represents a view with components, ports, and connectors based on how the model is structured.	Component diagrams allow you to programmatically or manually add and remove components from the view.	Inspect Components in Custom Architecture Views
hierarchy diagram	You can visualize a hierarchy diagram as a view with components, ports, reference types, component stereotypes, and stereotype properties.	There are two types of hierarchy diagrams: Component hierarchy diagrams display components in tree form with parents above children. In a component hierarchy view, each referenced model is represented as many times as it is used. Architecture hierarchy diagrams display unique component architecture types and their relationships using composition connections. In an architecture hierarchy view, each referenced model is represented only once.	Display Component Hierarchy and Architecture Hierarchy Using Views

Version History

Introduced in R2019b