| Key | Issue | Reported | Fixed | Disposition | Status | |
|---|---|---|---|---|---|---|
| PSUM-8 | Associations must be named in a MOF model | PSUM 1.0a1 | open | |||
| PSUM-7 | Model Element Risk should have a name different from Risk | PSUM 1.0a1 | open | |||
| PSUM-10 | Improve diagram readability and consistency | PSUM 1.0a1 | open | |||
| PSUM-11 | Use consistent font for model element names | PSUM 1.0a1 | open | |||
| PSUM-9 | Rephrase personalized sentences throughout the document | PSUM 1.0a1 | open |
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.
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.
In some diagrams of the metamodel, element names are underlined, or part of the diagram elements have shadows and others not, enumerations have unnecessary color.
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.
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.
