-
Key: SYSML2-640
-
Status: open
-
Source: MDD4All ( Dr. Oliver Alt)
-
Summary:
In SysML v2 parts are drawn in the graphical notation with rounded corners. In UML and and also in SysML v1.x there is a clear graphical language paradigm to use rounded corners only for behavioral elements like activities, states and use cases and all elements showing static aspects of a system like data structures, architectural things etc. are defining elements that have no rounded corners (e.g. classes, objects, blocks, parts, nodes etc.).
Would it not be possible to find a better graphical notation to differ between definition elements and their instances? What about using different shapes or different stroke widths? Also icons could be used in graphical elements to express a what kind of element it is - like it is done in BPMN for example.
I think following the rule, that behavioral aspects are modeled with rounded elements and static aspects with not-rounded elements would provide a better compatibility to still existing and well known standards like UML, SysML v1.x, BPMN etc.
Many people are still trained with high effort in using this notations in their daily work and I think they will be very confused when the should use SysML v2 in the future with that big paradigm shift in the graphical notation. -
Reported: SysML 2.0b1 — Tue, 16 Jan 2024 12:01 GMT
-
Updated: Mon, 8 Apr 2024 18:20 GMT
SYSML2 — Find a better way to differ between definition and instance elements in graphical notation
- Key: SYSML2-640
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF