-
Key: SYSML2_-260
-
Status: open
-
Source: sodiuswillert.com ( Mr. Eran Gery)
-
Summary:
Clause 7.16.1 (rep. notation for actions) shows a graphical notation example of an accept action corresponding to the following textual notation:
action trigger1 : Trigger accept scene : Scene via viewPort;
It shows 3 alternative graphical notations which are confusing and inconsistent.
That graphical representative example needs to be corrected. Here are few issues:- it shows an unbound parameter "receiver" in 2nd and 3rd examples
- first example uses the type Trigger instead of Trigger1
- 3rd example uses guillemets in the wrong way
- too many options instead of one "canonical" way to do this
- it uses a parameter that in 2nd example called scene and in 3rd example called payload
-
Reported: SysML 2.0b2 — Mon, 29 Jul 2024 07:03 GMT
-
Updated: Tue, 6 Aug 2024 05:39 GMT
SYSML2_ — Accept action in representative notation tables is confusing and needs cleanup
- Key: SYSML2_-260
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF 2