To verify structural and functional requirements, you must capture nonfunctional properties on elements in an architecture model. For example, if there is a limit on the total power consumption of a system, the model must capture the power rating of each electrical component. This requires extending built-in model element types with properties corresponding to requirements, in this case, an electrical component type as an extension of components. You can introduce a self-consistent domain of model element types into System Composer™ using a group of property sets, or stereotypes, called a profile.
System Composer provides these architectural model elements to describe an architecture model:
You can view the properties of each element in the architecture model using the Property Inspector. Open Property Inspector using View > Property Inspector.
You author profiles using the Profile Editor. Profiles are saved separately from the architecture model and are available to all architecture models.
When you create a profile, you define:
Stereotypes — Customize built-in model element types
Property sets — Add analysis properties to an architecture model element
Data types, dimensions, etc — Define property values
You can define stereotypes to extend built-in elements and capture additional data about
an element. Element stereotypes define the class of the elements to which they apply. For
MechanicalComponent stereotype with properties such as
Volume applies only to components.
A stereotype does not have to define a class. For example, a
ProjectItem stereotype can add generic properties such as catalog number
or unit cost, a
BorrowedItem stereotype can add properties such as
ReturnDeadline. A model element can
have multiple stereotypes.
Stereotypes can extend other stereotypes to include their properties. For example, a
UserInterface stereotype can be an extension of a
SoftwareComponent stereotype, and add a property called
You can collect stereotypes in profiles.
Create a profile to define a set of component, port, and connection types to be used in an architecture model. For example, a profile for an electromechanical system, such as a robot, could consist of these types:
Analog signal connection
Define a profile using the Profile Editor. In any architecture model, select Architecture > Profile > Profile Editor. Click New Profile. Select new profile to start editing.
Name the profile and provide a description. Add stereotypes by clicking New Stereotype. You can delete stereotypes and profiles by clicking in their respective menus.
Save the profile. The file name is the same as the profile name.
Select a stereotype in a profile to define it:
Name — The name of the component type, for example,
Applies to — The model element type to which the stereotype applies. This field can be an architecture, component, port, or connector. You can apply this stereotype only to a model element of this type.
Icon — Icon to be shown on the model element.
Base stereotype — Other stereotype on which this stereotype is based. This can be empty.
Abstract stereotype — A stereotype that is not intended to be applied directly to a model element. You can use abstract stereotypes only as the base stereotype for other stereotypes.
Add properties to a stereotype using . Define these fields for each property:
Property name — Valid variable name
Type — Numerical, string, or enumeration data type
Unit — Value units as a string
Default — Default value
Add, delete, and reorder properties using the property toolstrip:
You can create a stereotype that applies all model element types by setting the Applies to field to <nothing>. With these stereotypes, you can add properties to elements regardless of whether they are components, ports, connectors, or architectures.
Each profile can have a set of default stereotypes. Use default stereotypes when each new element of a certain type must assume the same stereotype. System Composer applies a default stereotype to the root architecture when you import the profile. You can set this default in the Profile Editor using the Stereotype applied to root on import field.
This default stereotype is for the top-level architecture. If a model imports multiple profiles, the default component stereotype for all profiles apply to the architecture.
Each component stereotype can also have defaults for the components, ports, and
connections added to its architecture. For example, if you want all new connections in an
electrical component to be analog connections, set
AnalogConnection as a
default stereotype for the
After you import the profile into a model, all new connections assume the