Limitations

Rhapsody's limitations  compared to the UML / SysML standard
What the standard says: 
How it looks in Rhapsody / Workaround: 
According to standard you can have multiple initial flows in an Activity Diagram. This is not supported in Rhapsody.
Use Fork node instead to create additional token.

In SysML 1.2 Dimensions where renamed to  QuantityKind
and further extended: See Link
Rhapsody 9.0 still uses the old concept of Dimensions which is outdated - The concept of QuantityKind is not available 
Workaround: Extend Rhapsody SysML Profile and create your own. 
Do you have identified more limitations  ? Happy to get your message:  frank.braun@rhapsody.guru

Share by: