Stereotype SysML blocks #2465
Replies: 5 comments 4 replies
-
Also, once a stereotype is created, how is it referenced by the CSS? |
Beta Was this translation helpful? Give feedback.
-
Something like this? Although Blocks are considered stereotypes of Classes in the SysML spec, we treat them as normal metaclasses -- similar to how one would create a stereotype from a Class. The CSS I created is: block[appliedStereotype.classifier.name=hardware] {
background-color: #99c1f1;
} These are references in the model. The stereotype is referencing an "instance" of the stereotype (since stereotypes are normally part of a meta model). See the UML spec on Instances and Gaphor Specific Constructs. |
Beta Was this translation helpful? Give feedback.
-
Yes I saw that too, but you can rename the element BEFORE connecting the stereotype. And it flows through. |
Beta Was this translation helpful? Give feedback.
-
Ouch. I expected all model elements to be present. Or at least have the modeling elements of the active profile available. It's probably a good idea to support stereotypes for the SysML and RAAML profiles by default. |
Beta Was this translation helpful? Give feedback.
-
I checked the code. Indeed, the list of classes only contains classes from the UML module. Unfortunately the code does not have access to the active modeling profile. It does make sense to have a Profile section in the SysML toolbox, though. |
Beta Was this translation helpful? Give feedback.
-
How would I stereotype the SysML components (e.g. Proxy Ports or Blocks)?
The metaclass doesn't allow for selecting SysML components and generalization of the block stereotype doesn't create a new stereotype. Creating a stereotype generalized from a new block stereotype results in creating duplicate stereotypes.
Beta Was this translation helpful? Give feedback.
All reactions