SysML 1.6 RTF Avatar
  1. OMG Issue

SYSML16 — Reference Properties do not reference properties

  • Key: SYSML16-371
  • Status: closed  
  • Source: University of Arizona ( Mr. Rick Steiner)
  • Summary:

    A reference property of a Block may only be typed by (i.e. "reference") another Block. There is no current mechanism for a reference property to explicitly reference a part property of a different block. See Figure D.16 for example; the PowerSubsystem Block is assumed to be referencing the part property of the BrakeSubsystem typed by BrakePedal. This is a logical conclusion since there is only one part property typed by BrakePedal, but if there were multiple part properties typed by BrakePedal, the reference property of the PowerSubsystem Block would be ambiguous.

    Practical use of reference properties has consistently implied that a particular part property CAN be referenced (i.e. "a part property owned by another block"), but no mechanism for this is explicitly provided in SysML. Also, there does not appear to be any constraint on instance semantics of reference properties that might clarify this ambiguity at the instance level.

    See also SYSML16-42 and SYSML16-228.

  • Reported: SysML 1.5 — Tue, 17 Oct 2017 00:17 GMT
  • Disposition: Deferred — SysML 1.6
  • Disposition Summary:

    Defer

    Postponed to the next RTF

  • Updated: Mon, 1 Apr 2019 18:16 GMT