1. OMG Mailing List
  2. SysML Extension for Physical Interaction and Signal Flow Simulation (SysPISF) 1.0 Finalization Task Force

Open Issues

  • Issues not resolved
  • Name: syspisf-ftf
  • Issues Count: 3

Issues Descriptions

Improve stereotype names

  • Key: SYSPISF_-3
  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    The stereotype defined in order to support simulation of physical and signal flows might also be used for specifying related system characteristics through a model, independently of any simulation intent.

    However, the "Sim" prefix used for each stereotype defined in this profile might discourage such an utilization and so it tends to restrict its domain of application. It's a shame.

    Consider using a more neutral prefix like "pisf" or avoiding using the "Sim" prefix for all of the stereotypes. Especially constants are of far broader interest than simulation only (and should event be introduced in SysML to me). The name "Constant" would be convenient. Also, I think that "SimVariable" could be renamed "FlowVariable".

  • Reported: SysPISF 1.0b1 — Thu, 27 Apr 2017 07:12 GMT
  • Updated: Tue, 2 May 2017 06:18 GMT

More detail needed in Annex A

  • Key: SYSPISF_-2
  • Status: open  
  • Source: NIST ( Mehdi Dadfarnia)
  • Summary:

    Filed for AB.

    Annex A needs to be more descriptive. It could use some more examples to explain the capabilities and scope of the extension and libraries.

  • Reported: SysPISF 1.0b1 — Mon, 8 Aug 2016 21:32 GMT
  • Updated: Thu, 6 Apr 2017 14:21 GMT

Binding connector notation: Use "equal" instead of "equals"

  • Key: SYSPISF_-1
  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    Figure 13, 14 shows binding connectors with keyword "equals". The keyword should be just "equal".

  • Reported: SysPISF 1.0b1 — Thu, 2 Feb 2017 16:34 GMT
  • Updated: Thu, 6 Apr 2017 14:21 GMT