Precise Semantics for Uncertainty Modeling Avatar
  1. OMG Specification

Precise Semantics for Uncertainty Modeling — Open Issues

  • Acronym: PSUM
  • Issues Count: 8
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Artifact is misspelled as Artefact

  • Key: PSUM-1
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    Throughout Clause 13 "Evidence", and in the metamodel, namely in the Evidence and Risk package, the word "Artifact" is misspelled as "Artefact". Correcting this will implicitly correct also a discrepancy with SACM.

  • Reported: PSUM 1.0b1 — Tue, 31 Oct 2023 01:07 GMT
  • Updated: Mon, 25 Mar 2024 15:54 GMT

Update Intellectual Property clause to ensure unrestricted world-wide access

  • Key: PSUM-3
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    Update the text of Clause 6.2 "Intellectual Property Rights" to ensure unrestricted world-wide access to the specification at no cost. The OMG IPR rules and the recorded copyrights shall apply.

  • Reported: PSUM 1.0b1 — Tue, 31 Oct 2023 01:26 GMT
  • Updated: Mon, 25 Mar 2024 15:54 GMT

Explicit Artifact Citation Element no longer available in SACM 2.3

  • Key: PSUM-2
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    Unfortunately SACM removed the explicit Artifact Citation element at some point in its revision history, which breaks backward compatibility. A solution for the use of citation in the PSUM Evidence and Risk package would be a specialization of the SACM ArtifactReference metaclass, then subsetting the reference pointing to referenced Artifacts to point to the cited Artifact

  • Reported: PSUM 1.0b1 — Tue, 31 Oct 2023 01:18 GMT
  • Updated: Mon, 25 Mar 2024 15:54 GMT
  • Attachments:

Associations must be named in a MOF model

  • Key: PSUM-8
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    The PSUM specification defines a MOF metamodel for the modeling of uncertainty. However, the Associations in this metamodel are not named, which is a requirement for MOF models.

  • Reported: PSUM 1.0a1 — Wed, 7 Feb 2024 03:42 GMT
  • Updated: Mon, 25 Mar 2024 15:54 GMT

Model Element Risk should have a name different from Risk

  • Key: PSUM-7
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    This issue was actually raised by the designated reviewer form the OMG Architecture Board. His argument was, that "Risk" is too broad for risk resulting from uncertainty.

  • Reported: PSUM 1.0a1 — Wed, 7 Feb 2024 03:37 GMT
  • Updated: Mon, 25 Mar 2024 15:54 GMT

Improve diagram readability and consistency


Use consistent font for model element names

  • Key: PSUM-11
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    In Clause 6.1.1, the use of italic font to designate model element names in the text is mandated. This is not consistently applied throughout the document.

  • Reported: PSUM 1.0a1 — Wed, 7 Feb 2024 04:00 GMT
  • Updated: Mon, 25 Mar 2024 15:54 GMT

Rephrase personalized sentences throughout the document

  • Key: PSUM-9
  • Status: open  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    There are many places in the document where sentences read similar like "We decided to define ..." or "therefore we defined ..." (maybe not exact quotes, but demonstrating the style). These sentences need to be rephrased to read as expected in a standards document.

  • Reported: PSUM 1.0a1 — Wed, 7 Feb 2024 03:50 GMT
  • Updated: Mon, 25 Mar 2024 15:54 GMT