Community
Participate
Working Groups
When I create a new Papyrus model, in the dialog for naming the model and defining a default diagram, I get some choices that refer to SysML diagrams. However, I think that Papyrus, when it comes out of the box, should be a pure UML tool and not a UML + SysML tool. There will likely be many users who do not know about and do not care about SysML -- they should not be confused by such extraneous diagram choices. If SysML is used, then it should be a special Papyrus-SysML tool, properly configured, etc. and not part of Papyrus proper.
I agree on the need to provide specific UML and SysML tool. This will probably be provided as RCP bundle containing only modeling related tool (understand that unnecessary menu, view of Eclipse are masked). The generic (UML + SysML + ...) version of the tool is also useful as Papyrus provide an edition framework for any language, not necessarily UML or SysML, accepting diagram for these languages or additional user defined diagrams.
The current spec. of Papyrus makes it a UML + SysML editor. There is currently no plan to make SysML optional. I close this task.
