Remove profile from model
Create a model.
model = systemcomposer.createModel("archModel"); systemcomposer.openModel("archModel");
Create a profile with a stereotype and properties, open the Profile Editor, then apply the profile to the model.
profile = systemcomposer.profile.Profile.createProfile("LatencyProfile"); latencybase = profile.addStereotype("LatencyBase"); latencybase.addProperty("latency",Type="double"); latencybase.addProperty("dataRate",Type="double",DefaultValue="10"); systemcomposer.profile.editor(profile) model.applyProfile("LatencyProfile");
Remove the profile from the model.
model — Architecture model
Architecture model, specified as a
dictionary — Data dictionary
Data dictionary, specified as a
systemcomposer.interface.Dictionary object. You can specify the default
data dictionary that defines local interfaces or an external data dictionary that
carries interface definitions. If the model links to multiple data dictionaries, then
dictionary must be the dictionary that carries interface
definitions. For information on how to create a dictionary, see
allocSet — Allocation set
allocation set object
Allocation set, specified as a
profileName — Name of profile
character vector | string
Name of profile, specified as a character vector or string.
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.
A System Composer model is the file that contains architectural information, including components, ports, connectors, interfaces, and behaviors.
Perform operations on a model:
A System Composer model is stored as an SLX file.
|Create Architecture Model with Interfaces and Requirement Links
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 architectural 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. Transfer information between components with:
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.
These are different types of ports:
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.
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. Stereotype 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.
Introduced in R2019a