RAAML 1.0 FTF Avatar
  1. OMG Issue

RAAML — Inability to import xmi profiles into Rhapsody

  • Key: RAAML-11
  • Status: closed  
  • Source: Stellantis ( Jerry Hendler)
  • Summary:

    Hi folks, I am part of the Society of Automotive Engineers STPA workgroup with Kyle Post and others. I did reach out to Kyle and he didn't have a solution for my issue, thought I'd ask the group. I am using Rhapsody v8.4 developing SysML models (using their SysML profile) and trying to import these RAAML profiles, but the Rhapsody xmi importer doesn't get past the first step, saying 'Cannot determine uml version'. Wondered if this is an issue others have run into and whether there might be a simple solution, Thanks, Jerry

  • Reported: RAAML 1.0b1 — Tue, 16 Mar 2021 14:01 GMT
  • Disposition: Closed; No Change — RAAML 1.0
  • Disposition Summary:

    Current .xmi's are correct and standard compliant

    Was an issue with using an older tool version.

    Data that the xmi is correct:
    -Correct from MagicDraw's test
    -Correct from Enterprise Architect's test
    -Correct by comparison to other OMG normative documents:
    For example, UML 2.5.1 (e.g. StandardProfile.xmi)
    namespaces, used for UML models are:
    and those are exactly the namespaces that we used across the *.xmi documents in RAAML

    Additionally, the Rhapsody version used was an older version and if the UML version is manually changed to an older version it imported into Rhapsody.

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