1
Automation Interface, Add-Ins and Tools / Re: Use toolbox of different MDG tech
« on: September 28, 2010, 06:20:11 pm »
Hi KP, (Hello Forum),
thanks for your very quick answer!
Actually, both worked! I just tested it and wound up both times with the exact results that I intended, i.e. my custom diagram featuring the SysML toolbox. Thank you so much!
I would, however, suspect that specifying "SysML_Interaction" instead of "SysML1.1::SysML_Interaction" is the more robust way to do it. I can imagine that when a new revision of the SysML MDG tech comes out (which I am sure will happen at some point... after all OMG just came out with SysML 1.2 :-) ), and someone has that new version of SysML MDG installed, then "SysML1.1::SysML_Interaction" might not work anymore, while "SysML_Interaction" might still be OK. Just speculation, however.
Thanks for explaining. So, I take it that I can extend the SysML language (rather than UML) in Enterprise Architect by regularly extending EA built-in elements (which afaik are pretty much UML), such as "Diagram_xxx" or "<<metaclass>> Class", and then extending an SysML equivalent element from the same EA built-in element alongside my own stereotype definition? Then, I would wind up with two stereotypes extending the metaclass.
Thanks for your help once again!
Bastian
thanks for your very quick answer!
Quote
QuoteIs it possible to specify the SysML::Interaction toolbox as the toolbox for my custom Diagram_Sequence?
I have no idea if it will work or not, but if it does you will need to specify either "SysML_Interaction" or "SysML1.1::SysML_Interaction". Let me know how you get on!
Actually, both worked! I just tested it and wound up both times with the exact results that I intended, i.e. my custom diagram featuring the SysML toolbox. Thank you so much!
I would, however, suspect that specifying "SysML_Interaction" instead of "SysML1.1::SysML_Interaction" is the more robust way to do it. I can imagine that when a new revision of the SysML MDG tech comes out (which I am sure will happen at some point... after all OMG just came out with SysML 1.2 :-) ), and someone has that new version of SysML MDG installed, then "SysML1.1::SysML_Interaction" might not work anymore, while "SysML_Interaction" might still be OK. Just speculation, however.
Quote
The SysML ibd extends "Diagram_CompositeStructure" so you would need to do the same.
[...]
You would need to extend Class and apply both «block» and your own stereotype to the same class element.
Thanks for explaining. So, I take it that I can extend the SysML language (rather than UML) in Enterprise Architect by regularly extending EA built-in elements (which afaik are pretty much UML), such as "Diagram_xxx" or "<<metaclass>> Class", and then extending an SysML equivalent element from the same EA built-in element alongside my own stereotype definition? Then, I would wind up with two stereotypes extending the metaclass.
Thanks for your help once again!
Bastian