UAF 1.3b1 RTF Avatar
  1. OMG Issue

UAF13 — Figure 8:2 Architecture Views Does Not Conform to ISO/IEC/IEEE 42010 - Multiplicities, Naming, Direction [repeat - Tracker Now Using Correct OMG Identifiers]

  • Key: UAF13-116
  • Status: open  
  • Source: Eclectica Systems Ltd ( Nic Plum)
  • Summary:

    The use of a '*' multiplicity is incorrect - should be 1 or more Concerns. Similarly an ArchitecturalDescription (name error - should be ArchitectureDescription) should be composed of 1 or more Architecture Views (not *). A Viewpoint may frame only 1 Concern (not *)

    The use of a direction indicator is undefined and looks to be incorrect. In the direction from View to Viewpoint what is the relationship? In ISO 42010 there is a 'governs' relationship.

    The use solely of role names is incorrect - roles only label the target (source) node - they do not define a relationship. How is anyone supposed to implement a set or relationships where the relationships are not labelled? Figure 8:2 should use the relationship names defined in 42010 i.e. standardise.

    Using a role name that simply repeats the name of the source / target element is pointless - it adds no information whatsoever. The other problem with solely using role names is that if the label is offset it isn't clear whether it is a role or a relationship name and therefore whether it applies to the node or relationship.

  • Reported: UAF 1.2b1 — Thu, 4 Apr 2024 13:23 GMT
  • Updated: Thu, 4 Apr 2024 15:18 GMT