SysML 1.1 RTF Avatar
  1. OMG Issue

SYSML11 — Section: Ports and Flows - Behavioral flow ports

  • Key: SYSML11-6
  • Legacy Issue Number: 10033
  • Status: closed  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Behavioral flow ports. In Ports and Flows, FlowPort 9.3.2.5, Description, the fourth and sixth paragraph seem to give contradictory defintions of behavioral flow ports. The second refers to the UML isBehavior semantics. The fourth refers to "relaying" to properties or parameters, but doesn't explain what that means. If the two paragraphs are referring to the same thing, then presumably a block behavior is a classifier behavior, and since that behavior executes while the block instance exists, relaying to the parameters requires those parameter to be streaming, in the sense of CompleteActivities. The semantics of relaying properties is unrelated to UML behavior ports.

  • Reported: SysML 1.0b1 — Sat, 29 Jul 2006 04:00 GMT
  • Disposition: Resolved — SysML 1.1
  • Disposition Summary:

    Change the following paragraph in section 9.3.2.3:
    "Flow ports relay items to/from the associated connector to/from properties of the owning block or parameters of the block behavior if the port is not connected to an internal link that may relay the items to an internal part of its owner. This means that every flow property contained within a flow port is bound to a property owned by the block or a parameter of the block behavior."
    To:
    "Flow ports relay items to their owning block or to a connector that connects them with their owner's internal parts (internal connector).
    The isBehavior attribute inherited from UML port is interpreted in the following way: if isBehavior is set to true, then the items are relayed to\from the owning block. More specifically, every flow property within the flow port is bound to a property owned by the port's owning block or to a parameter of its behavior. If isBehavior is set to false, then the flow port must be connected to an internal connector which in turn related the items via the port. The need for isBehavior is mainly to allow specification of internal parts relaying items to their containing part via flow ports"
    Add the following constraint:
    [5] If a flow port is not connected to an internal part then isBehavior should be set to true.

  • Updated: Fri, 6 Mar 2015 20:58 GMT