Main Content

setDefaultStereotype

Set default stereotype for profile

    Description

    example

    setDefaultStereotype(profile,stereotypeName) sets the default stereotype for a profile. The stereotype must apply to components.

    Examples

    collapse all

    Create a profile for latency characteristics.

    profile = systemcomposer.profile.Profile.createProfile('LatencyProfile');
    
    connLatency = profile.addStereotype('ConnectorLatency','AppliesTo','Connector');
    connLatency.addProperty('secure','Type','boolean');
    connLatency.addProperty('linkDistance','Type','double');
    
    nodeLatency = profile.addStereotype('NodeLatency','AppliesTo','Component');
    nodeLatency.addProperty('resources','Type','double','DefaultValue','1');
    
    portLatency = profile.addStereotype('PortLatency','AppliesTo','Port');
    portLatency.addProperty('queueDepth','Type','double');
    portLatency.addProperty('dummy','Type','int32');

    Set the default stereotype.

    profile.setDefaultStereotype('NodeLatency');

    Create a model and apply the profile. Open the profile editor.

    modelName = 'archModel';
    arch = systemcomposer.createModel(modelName,true);
    
    arch.applyProfile('LatencyProfile');
    
    systemcomposer.profile.editor()

    Get stereotypes on the root architecture.

    stereotypes = getStereotypes(arch.Architecture)
    stereotypes =
    
      1×1 cell array
    
        {'LatencyProfile.NodeLatency'}

    Input Arguments

    collapse all

    Profile, specified as a systemcomposer.profile.Profile object.

    Stereotype name, specified as a character vector or string. The stereotype must be present in the profile.

    Example: 'ComponentStereotype'

    Data Types: char | string

    More About

    collapse all

    Definitions

    TermDefinitionApplicationMore Information
    architectureA 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:

    • Functional architecture describes the flow of data in a system.

    • Logical architecture describes the intended operation of a system.

    • Physical architecture describes the platform or hardware in a system.

    Compose Architecture Visually
    modelA System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.

    Perform operations on a model:

    • Extract the root-level architecture contained in the model.

    • Apply profiles.

    • Link interface data dictionaries.

    • Generate instances from model architecture.

    System Composer models are stored as SLX files.

    Create an Architecture Model with Interfaces and Requirement Links
    componentA 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
    portA 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:

    • 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.

    Ports
    connectorConnectors 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

    TermDefinitionApplicationMore Information
    stereotypeA 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
    propertyA 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.
    profileA 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.

    Introduced in R2019a