Main Content


Get value of architecture property



    value = getPropertyValue(element,property) gets the non-evaluated property value for the provided architectural element.


    collapse all

    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");

    Create a model with a component called 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.


    Get the property value.

    value = getPropertyValue(comp,"LatencyProfile.electricalComponent.latency")
    value =

    Input Arguments

    collapse all

    Property name, specified as a character vector or string in the form "<profile>.<stereotype>.<property>".

    Data Types: char | string

    Output Arguments

    collapse all

    Property value, returned as a character vector.

    Data Types: char

    More About

    collapse all


    TermDefinitionApplicationMore Information

    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.


    The root is at the top of an architecture hierarchy. A root architecture has a boundary defined by its architecture ports surrounding 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.

    Compose Architectures Visually


    A System Composer model is the file that contains architectural information, such as components, ports, connectors, interfaces, and behaviors.

    Perform operations on a model:

    • Extract root-level architecture.

    • Apply profiles.

    • Attach interface data dictionaries.

    • Generate instances from model architecture.

    A System Composer model is stored as an SLX file.

    Create Architecture Model with Interfaces and Requirement Links

    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:

    Compose Architectures Visually


    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.

    Compose Architectures Visually


    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.

    Compose Architectures Visually

    TermDefinitionApplicationMore Information

    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.


    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.


    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.

    TermDefinitionApplicationMore 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 Simulink.ConnectionBus object that specifies a number of Simulink.ConnectionElement objects.

    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 Simulink.ConnectionElement object.

    Define the Type of a physical element as a physical domain to enable use of that domain in a physical model.

    Describe Component Behavior Using Simscape

    Version History

    Introduced in R2019a