RAAML 1.0 FTF Avatar
  1. OMG Issue

RAAML — Choice of allocation of GSN fields to UML attributes

  • Key: RAAML-53
  • Status: closed  
  • Source: Object Management Group ( Mr. Juergen Boldt)
  • Summary:

    Under ‘GSNNode’ it is stated that the ‘short phrase’ (referred to in the GSN standard as the <element statement>) shall be captured as the UML model element name, whilst the Human-readable identifier (referred to in the GSN standard as the <element identifier>) shall be stored as a separate tag. This appears an odd choice since the <element identifier> is assured to be unique, whilst the <element statement> is not. It may be appropriate to swap these allocations.

  • Reported: RAAML 1.0b1 — Tue, 11 May 2021 18:30 GMT
  • Disposition: Closed; No Change — RAAML 1.0
  • Disposition Summary:

    GSN Statement Text and Identifier

    The uniqueness or non-uniqueness of the field was not a primary reason for the mapping choice.
    The reason for mapping the GSN statement text to a UML element name is to make it easier for the end user to see/find/manipulate the element in the tool UI. UML tools primarily expose the model element names everywhere in the GUI (element visualization in the diagrams, various tables, containment trees),
    while tag information is secondary.

  • Updated: Thu, 31 Mar 2022 19:32 GMT