Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: PeteC on March 21, 2022, 10:49:56 pm
-
If I include SysML1.3::quantityKind and SysML1.3::unit in my toolbox definition I am able to include those elements in my custom toolbox, but if I change it to the current SysML1.4:: then it doesn't work. When I drop the unit and quantityKind elements by manually selecting the SysML 1.5 toolbox, it is notable that they do not have any stereotype and likely why my inclusion in a toolbox is failing. So how then do I include the SysML 1.4/1.5 versions of unit and quantityKind elements? I'd prefer to use the latest rather than the retrograde step of using elements from SysML1.3.
I am able to successfully include SysML1.4::ValueType in my custom toolbox.
-
These simply don't exist anymore in the SysML 1.4 or SysML 1.5 profile.
You'll have to add the simple UML basetype to your toolbox.
Geert
-
They have been added as patterns. Try "SysML1.4::Unit(UMLPatternSilent)" and "SysML1.4::QuantityKind(UMLPatternSilent)" although I'm not 100% sure if you can import a pattern from a different technology like that. If it doesn't work, you will need to recreate the patterns in your own technology. Let us know how you get on.
-
Neil answered how you create the elements, so I'll just keep my explanation.
What's happened is that the SysML specification no longer defines a stereotype for these types. Instead it provides classes and Unit and QuantityKind are instances of those types. We implemented this as a pattern.
-
Thanks KP. Importing them as patterns works correctly.