SyM 1.0b2 FTF Avatar
  1. OMG Issue

SYM — SysML-Modelica Transformation Spec problem with

  • Key: SYM-12
  • Legacy Issue Number: 16545
  • Status: closed  
  • Source: Change Vision ( Michael Chonoles)
  • Summary:

    As found by Lenny Delligatti of Lockheed Martin.

    On page 5 of the spec., it shows that the SysML4Modelica profile references the SysML profile (Figure 2 in the screenshot below):

    But I believe that’s an error. I believe that a «reference» dependency is only legal from a profile to a metamodel.

    One profile can «import» another profile (and thus transitively reference a metamodel), but not «reference» another profile.

  • Reported: SyM 1.0b1 — Fri, 9 Sep 2011 04:00 GMT
  • Disposition: Resolved — SyM 1.0b2
  • Disposition Summary:

    A UML dependency can be between any two NamedElements. The dependency can also be tagged with any stereotype and be given any name. So the <<reference>> dependency is by itself legal. However, a keyword such as <<import>> can also be applied to a dependency.The <<import>> keyword seems more suitable to be applied on a dependency between profiles. So the <<reference>> dependencies to the UML4SysML metamodel (as shown in the SysML spec) in Figure 2 are kept and the <<reference>> dependency between the SysML4Modelica and SysML profiles in Figure 2 is replaced by an <<import>> dependency.

  • Updated: Fri, 6 Mar 2015 20:58 GMT