SysML 1.1 RTF Avatar
  1. OMG Issue

SYSML11 — Section: ItemFlow

  • Key: SYSML11-16
  • Legacy Issue Number: 10342
  • Status: closed  
  • Source: ( Fraser Chadburn)
  • Summary:

    FlowPorts can be typed by (p64): · Block · DataType · FlowSpecification · Signal · ValueType FlowProperties (which are owned by FlowSpecifications) can be typed by (p65): · Block · DataType · Signal · ValueType Yet ItemFlows can only be typed by (p66): · Block · ValueType Since FlowPorts and associated Flow Specifications define “what can flow” between the block and its environment. Whereas ItemFlows specify “what does flow” in a specific usage context. It therefore proposed that the ItemFlows constraint section is updated to include DataType and Signal, as well Block and ValueType (i.e. same as FlowProperties). Note: It is assumed that having an ItemFlow typed by a flow specification would make no sense, since the item properties have direction on them that would have to be interpreted in relation to the direction of the item flow arrow. Is this assertion correct?

  • Reported: SysML 1.0b1 — Mon, 11 Sep 2006 04:00 GMT
  • Disposition: Resolved — SysML 1.1
  • Disposition Summary:

    Change the constraint on the conveyed classifier of items flows to be the same
    as the constraint on item properties. In answer to the question, item flows can
    convey items that have flow properties, but these flow properties apply to the
    item itself, not the source and target of the flow.

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