-
Key: SYSML17-93
-
Legacy Issue Number: 18502
-
Status: closed
-
Source: PTC ( Phillip Astle)
-
Summary:
Figure C.35 uses the optional notation for Pins (i.e.
>[]> instead of []->[]). The allocation callout note is anchored to the object node symbol which makes it ambiguous as to which dictionary item(s) are being allocated. It could be one of the following:+ the origin and destination pins
+ the object flow
+ the common type of the pinsSince it's unclear what is being allocated, it would make more sense to show the Pins on the diagram and link the callout note to the relevant item(s) (I believe it's supposed to go to the ObjectFlow).
-
Reported: SysML 1.3 — Tue, 26 Feb 2013 05:00 GMT
-
Disposition: Duplicate or Merged — SysML 1.7
-
Disposition Summary:
Merged with
SYSML17-185Merged with
SYSML17-185which collects all issues regarding annex D. -
Updated: Thu, 22 Dec 2022 13:45 GMT
-
Attachments:
- uml-2-5-Figure 15.14 ObjectFlow example.png 67 kB (image/png)
- uml-2-5-Figure 15.9 ObjectFlow notations.png 63 kB (image/png)
- uml-2-5-Figure 16.6 Standalone Pin notations.png 78 kB (image/png)
SYSML17 — Don't use the optional notation for Pins with Allocation
- Key: SYSML17-93
- OMG Task Force: SysML 1.7 RTF