SysML 1.7 RTF Avatar
  1. OMG Issue

SYSML17 — 'Figure 15-4: Behavior Allocation' multiple issues in the diagram and the supporting text

  • Key: SYSML17-355
  • Status: closed  
  • Source: Webel IT Australia ( Dr. Darren Kelly)
  • Summary:

    The title of the section is:

    15.4.1 Behavior Allocation of Actions to Parts and Activities to Blocks

    There is in fact no allocation of an Activity to a Block, there is an allocation of an Activity6 to a Part7.

    From p. 177:

    Specific behavior allocation of Actions to Parts are depicted in Figure 15-4.

    But the diagram includes an allocation from an Activity6 to a Part7 (that it is a part is confirmed by the «part» keyword in the allocatedTo callout).

    The allocation to Activity6 comes from a nested part ..

    The allocation is from the Activity6 to a part ...

    The use of part names 'Part5', 'Part7' with Capitals is confusing. It is much clearer to have property names that are lowerCase. If they must have names with Capitals then the Blocks that type them should be shown (see attached image).

    The use of the part name 'Block1' as the allocation target for Action1 is beyond confusing when there is a block Block1 in the same diagram.

    ASIDE: I wish the RTF diagram contributors would adopt a policy across the entire specfication of using lowerCamelCase (no spaces) for all block properties and UpperPascalCase (no spaces) for all Blocks

    The diagram figure is low resolution and needs to be replaced.

    The following may be in part MagicDraw/Cameo 19SP3 tool issues:

    • The path callout in the Note for the allocatedTo on Activity6 in the tool is '«part» Block4::Block7::part7'; the spec has '«part» Block4.Part5.Part7'
    • The tool could not (as far as I can tell) display the qualified name corresponding to Part:Block1 for the header in a swimlane
  • Reported: SysML 1.6 — Wed, 1 Jul 2020 03:34 GMT
  • Disposition: Resolved — SysML 1.7
  • Disposition Summary:

    Behavior Allocation

    Correct the text in following way:

    Specific behavior allocation+s+ of Actions to Parts and Activities to Blocks are depicted in Figure 15-4.

    The allocation to Activity6 from action1 comes from goes to a nested part, and uses the attributes of DirectedRelationshipPropertyPath to specify the path of properties to reach that part. The sourceContext targetContext of the allocation is Block4 Block 0 and the sourcePropertyPath targetPropertyPath is (Part5) part1. Note that the AllocateActivityPartition, if used in this manner, is unambiguously associated with behavior allocation.

    Replace the diagram with this one:

    This diagram can be found in the specification model in the teamwork cloud under Element ID

  • Updated: Thu, 22 Dec 2022 13:45 GMT
  • Attachments: