In the Webel trail versions of the SysML-1.6 spec sample Figure D.38, the alignment of ObjectNode symbols over the ActivityParameterNode boundaries is completely contrived, please DO NOT mimic it; please use explicit Pins instead!

This page identifies a possible issue, inconsistency, concern, error, or bug!

One of the ways Webel IT Australia helps promote tools, technologies, and languages is by donating a lot of time identifying, tracking, and reporting potential issues, in order to help vendors and developers improve the tools and technologies. In some cases, we also offer workarounds and advice for users. All issues tracked on our public site are offered most constructively and with sincerest gratitude to the tool vendors and technology developers.

DISCLAIMER: Vendors do not officially endorse issue analysis by Webel IT Australia.

Icon class

icon_class

far fa-sticky-note

icon_class_computed

far fa-sticky-note

Note kind

ISSUE

STYLE

Specification keywords

SysML-1.6

UML keywords

elided Pin notation

ObjectNode

SysMLv1.x keywords

HSUV sample problem

AllocateActivityPartition

Keywords

Note that because the tool does not correctly implement UML elided Pin notation the "ObjectNode symbols" in fact represent incorrect CentralBufferNodes:

MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode in place of "elided Pin notation" instead of an abstract ObjectNode symbol and 2 arrow symbols (that are supposed to represent together 2 Pins and 1 ObjectFlow edge)

Therefore:

Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins!

Relates to

Figure D.38 - Detailed Behavior Model for “Provide Power” {ELIDED PINS}

Figure D.38 - Detailed Behavior Model for “Provide Power” {EXPLICIT PINS}

Related notes

Related notes (backlinks)

Related snippets (extracts)

Visit also

Visit also (backlinks)

Flags