SysML 1.1 RTF Avatar
  1. OMG Issue

SYSML11 — SysML:Ports can't be blocks

  • Key: SYSML11-66
  • Legacy Issue Number: 11628
  • Status: closed  
  • Source: Change Vision ( Michael Chonoles)
  • Summary:

    Apparently from while you can type a flowport by a block, that block indicates the things that flow over the port.

    A more intuitive interpretation would be that the flowport is a block. Most flowports appear to be physical things that may convey blocks.

    Without the ability to indicate the physical thing that is the block, you lose the ability to specify it, reuse it, define it, etc.

    It’s much more intuitive to indicate that the flowport is a


    In addition, for example, in Figure B.19. There are flowpoints named



    Based on section, these flowports convey Fittings, not Fuel.

    There needs to be a way, preferably graphically, that would indicate that the type of Flowport is a block, and in that block, allow for the definitiaojn of what flows.

  • Reported: SysML 1.0 — Thu, 4 Oct 2007 04:00 GMT
  • Disposition: Resolved — SysML 1.1
  • Disposition Summary:

    Ports are properties, so cannot be blocks, but the resolution of issue 13178
    clarifies that some ports represent a new, potentially physical, element in the
    system (full ports). These can be typed by blocks that have flow properties as
    well as other kinds of properties, as suggested above. Some ports do not
    represent a new element in the system (proxy ports). Flow specifications and
    non-atomic flow ports are redundant.

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