APP-INST 1.0 FTF Avatar
  1. OMG Issue

APPINST — XMI model (c4i/13-09-06) doesn't model Array types correctly

  • Key: APPINST-5
  • Status: closed  
  • Source: Real-Time Innovations ( Mr. Andrea Sorbini)
  • Summary:

    The XMI model (file c4i/13-09-06) does not correctly model arguments and function parameters that are meant to be arrays.

    An example can be found at line 258:

    <ownedParameter xmi:id="EAID_RT000000_5B50_404d_861C_A9E007E4ECB7" name="return" type="EAnone_ObservableObject___" direction="return"/>

    The type is shown as "ObservableObject [ ]" in the UML diagram, but it was translated into an "anonymous type" by the modelling tool.

    These invalid references must be replaced by the ID of the intended element type (e.g. the ID of "ObservableObject"), and the array nature must be modelled by setting the multiplicity of each array attribute or parameter to 0..*

  • Reported: APP-INST 1.0b1 — Tue, 3 Nov 2015 05:06 GMT
  • Disposition: Resolved — APP-INST 1.0
  • Disposition Summary:

    Fix invalid type identifiers for Array types in XMI model

    The invalid type identifiers described by issue APPINST-5 have been replaced by valid references to the expected array types in the normative XMI model.

    Resolution for this issue required changes to be applied to the UML model, created in Enterprise Architect. These changes were applied together with those required by resolution APPINST-7.

    The offending elements were identified by inspecting document c4i/13-09-06 in search of XML elements which presented a value for their type attribute that matched the regular expression:

    EAnone_[a-zA-Z]+___$
    

    These elements were modified in Enterprise Architect so that they would reference the correct type for their elements. The functionalities provided by the tool were used to mark each element as an array.

    After performing modifications for APPINST-7, the resulting UML model was exported to an XMI file, which was modified according to APPINST-6 and APPINST-8.

    The final version of the document is attached to this resolution as omg_appinst_pim.xmi and it resolves issues APPINST-1, APPINST-2, APPINST-5, and APPINST-9.

    Change Log

    The regeneration of the XML from the updated UML model replaces the references to undefined types with names such as "EAnone_XXX" with the proper GUIDs "EAID_XXX" to existing types in the model.

  • Updated: Tue, 29 Mar 2016 15:05 GMT
  • Attachments: