Link and unlink profiles and order stereotypes
Use the Manage Profiles tool to import profiles into the current architecture model, or remove profiles from the model that have already been imported. The imported profiles appear in a list by name and the model or dictionary to which a profile is linked. To manage the priority order of the stereotypes from all imported profiles, click Manage Stereotype Order. To define and edit profiles, use the Profile Editor tool.
Open the Manage Profiles
System Composer™ toolstrip: Navigate to Modeling > Profile Editor > Manage.
Import — Import profile into model
Import a profile into the current architecture model by navigating to the current
directory and choosing a profile with an
Remove — Remove profile from model or dictionary
Remove the selected profile on the list from the model or dictionary to which the profile is linked.
Manage Stereotype Order — Manage order of stereotypes for imported profiles
Manage the priority order of stereotypes for imported profiles so that when multiple profiles are applied to a model element, the highest priority stereotype will display stereotype-based styling.
For more information, see Change Stereotype Order Using Manage Profiles Tool.
Connector styling is sourced from the highest-priority stereotype that defines style information. Connector stereotypes have the highest priority, followed by port stereotypes and then interface stereotypes. When two connectors with different styling merge, if the styling is incompatible, the resulting connector is displayed in black.
model.applyProfile(profile) links a profile to the model.
model.removeProfile(profile) unlinks a profile from the
A 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.
Link interface data dictionaries.
Generate instances from model architecture.
A System Composer model is stored as an SLX file.
Interface Data Dictionary
An interface data dictionary is a consolidated list of all the interfaces and value types in an architecture and where they are used.
Local interfaces on a System Composer model can be saved in an interface data dictionary using the Interface Editor. You can reuse interface dictionaries between models that need to use a given set of interfaces, elements, and value types. Linked data dictionaries are stored in separate SLDD files.
A profile is a package of stereotypes that you can use 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 or several profiles. When you save profiles, they are stored in XML files.
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 model elements such as root-level architecture, component architecture, connectors, ports, data interfaces, value types, functions, requirements, and links. Functions only apply to software architectures. You must have a Requirements Toolbox™ license to apply stereotypes to requirements and links. A model element can have multiple stereotypes. Stereotypes provide model elements with a common set of property fields, 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 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:
Port interfaces using the Interface Editor
Parameters using the Parameter Editor
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:
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.
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.
Introduced in R2019a