Precise Semantics for Uncertainty Modeling Avatar
  1. OMG Specification

Precise Semantics for Uncertainty Modeling — All Issues

  • Acronym: PSUM
  • Issues Count: 8
  • Description: All Issues
Closed All
All Issues

Issues Descriptions

Rephrase personalized sentences throughout the document

  • Key: PSUM-9
  • Status: closed  
  • 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
  • Disposition: Resolved — PSUM 1.0b2
  • Disposition Summary:

    Rephrase text to match standards phraseology

    The FTF rephrased all sentences of "personal flavor" to represent phraseology expected from a standard document.

  • Updated: Mon, 17 Jun 2024 13:38 GMT

Improve diagram readability and consistency


Use consistent font for model element names

  • Key: PSUM-11
  • Status: closed  
  • 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
  • Disposition: Resolved — PSUM 1.0b2
  • Disposition Summary:

    Represent literal model element mentioning with italic font

    The FTF agrees that many literal mentioning of model elements are not represented in italic font as they should. This resolution corrects this.

  • Updated: Mon, 17 Jun 2024 13:38 GMT

Explicit Artifact Citation Element no longer available in SACM 2.3

  • Key: PSUM-2
  • Status: closed  
  • 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
  • Disposition: Resolved — PSUM 1.0b2
  • Disposition Summary:

    Resolve connection to SACM 2.3

    A revision of SACM had removed the explicit citation modeling. To overcome this backward-incompatible change in SACM, the PSUM submission substituted the missing ArtifactElementCitation element in a stub model. This resolution corrects the situation by moving ArtifactElementCitation to the PSUM Evidence and Risk package, and make it specializing ArtifactReference of SACM. The change is purely in the PSUM Metamodel, but will also affect Clause 13 and Figures 8.1 and 13.1

  • Updated: Mon, 17 Jun 2024 13:38 GMT
  • Attachments:

Associations must be named in a MOF model

  • Key: PSUM-8
  • Status: closed  
  • 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
  • Disposition: Resolved — PSUM 1.0b2
  • Disposition Summary:

    Name all unnamed Associations in the Metamodel

    The FTF agreed that all unnamed Associations shall be named.

  • Updated: Mon, 17 Jun 2024 13:38 GMT

Artifact is misspelled as Artefact

  • Key: PSUM-1
  • Status: closed  
  • 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
  • Disposition: Resolved — PSUM 1.0b2
  • Disposition Summary:

    Rename "artefact" to "artifact"

    In Clause 13 "Evidence", and in the PSUM Metamodel, the word "artifact" is misspelled as "artefact". Besides linguistics, this causes also reference problems between PSUM and SACM. Correcting the spelling resolves the references too.

  • Updated: Mon, 17 Jun 2024 13:38 GMT

Model Element Risk should have a name different from Risk

  • Key: PSUM-7
  • Status: closed  
  • 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
  • Disposition: Closed; No Change — PSUM 1.0b2
  • Disposition Summary:

    Follow ISO 31000 Guidance

    The FTF decided to follow the lead of ISO 31000 and retains the element name "Risk". This is what ISO 31000 says:
    ISO 31000 creates a new definition of risk as "the effect of uncertainty on objectives, whether positive or negative." This definition shifts the understanding of risk away from the possibility of a negative outcome and toward the uncertainty itself.

    ISO 31000 divides risks into three categories, all incurring uncertainty:

    • Hazard (if the uncertain event occurs, there will be negative outcomes)
    • Control (the results of the uncertainty are themselves uncertain)
    • Opportunity (if the uncertain event occurs, there will be positive outcomes)
  • Updated: Mon, 17 Jun 2024 13:38 GMT

Update Intellectual Property clause to ensure unrestricted world-wide access

  • Key: PSUM-3
  • Status: closed  
  • 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
  • Disposition: Resolved — PSUM 1.0b2
  • Disposition Summary:

    Update intellectual property rights statement in Clause 6.2

    Update the intellectual property rights statement to ensure this specification is freely accessible to everyone and everywhere in the world at no cost.

  • Updated: Mon, 17 Jun 2024 13:38 GMT