${taskforce.name} Avatar
  1. OMG Task Force

2nd SysML-Modelica 1.0 FTF — Closed Issues

  • Key: SYM_
  • Issues Count: 7
Open Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

The figure references UML4SysML which is no longer part of/used by the version of SysML (1.3)

  • Key: SYM_-7
  • Legacy Issue Number: 17221
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The figure references UML4SysML which is no longer part of/used by the version of SysML (1.3) included in the normative references

  • Reported: SyM 1.0b2 — Fri, 9 Mar 2012 05:00 GMT
  • Disposition: Resolved — SyM 1.0
  • Disposition Summary:

    The figure should reference UML package instead of the UML4SysML package.

  • Updated: Sat, 7 Mar 2015 08:56 GMT

wrong reference

  • Key: SYM_-6
  • Legacy Issue Number: 17218
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The figure references UML4SysML which is no longer part of/used by the version of SysML (1.3) included in the normative references

  • Reported: SyM 1.0b2 — Fri, 9 Mar 2012 05:00 GMT
  • Disposition: Resolved — SyM 1.0
  • Disposition Summary:

    See issue 17214 for disposition

  • Updated: Sat, 7 Mar 2015 08:56 GMT

namespace definition in the XMI and the URI attribute of the Profile

  • Key: SYM_-5
  • Legacy Issue Number: 17217
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    The namespace definition in the XMI and the URI attribute of the Profile is xmlns:SysML4Modelica=http://www.omg.org/spec/SysM/20120213. This uses SysM not the official directory (according to the other documents) which is the shorter SyM.

  • Reported: SyM 1.0b2 — Fri, 9 Mar 2012 05:00 GMT
  • Disposition: Resolved — SyM 1.0
  • Disposition Summary:

    The spec name “SysM” was wrongly used in the XMI definition of the SysML4Modelica profile. It needs to be changed to the shorter "SyM" version.

  • Updated: Sat, 7 Mar 2015 08:56 GMT

It's unclear what compliance would mean

  • Key: SYM_-4
  • Legacy Issue Number: 17216
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Section 2 includes in Level 0 Compliance “The SysML4Modelica profile must be compliant with OMG SysML v1.3.”. However a) this profile is part of this specification and b) SysML does not define compliance for Profiles. So it’s unclear what compliance would mean

  • Reported: SyM 1.0b2 — Fri, 9 Mar 2012 05:00 GMT
  • Disposition: Resolved — SyM 1.0
  • Disposition Summary:

    In order to avoid any confusion, the sentence "The SysML4Modelica profile must be compliant with OMG SysML v1.3" should be remove.

  • Updated: Sat, 7 Mar 2015 08:56 GMT

In general the Part structure used is not appropriate for OMG specifications

  • Key: SYM_-3
  • Legacy Issue Number: 17215
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    In general the Part structure used is not appropriate for OMG specifications. It does not make sense to label Part I as non-normative. Especially as Part I includes Conformance and Normative References!

  • Reported: SyM 1.0b2 — Fri, 9 Mar 2012 05:00 GMT
  • Disposition: Resolved — SyM 1.0
  • Disposition Summary:

    The part structure is kept since it is still considered helpful to structure the document. Part 1 needs to be labeled as normative.

  • Updated: Sat, 7 Mar 2015 08:56 GMT

new figure uses <> <> and <> applied to lines using the Dependency notation

  • Key: SYM_-2
  • Legacy Issue Number: 17214
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    the new figure still uses <<conformsTo>> <<transformation>> and <<instanceOf>> applied to lines using the Dependency notation. These have no defined meaning (either as keywords nor as stereotypes defined either in this specification, SysML or UML). Whatever <<instanceOf>> means it’s not the case that a transformationRecord is an instance of a transformation. If these stereotypes are retained there should be an explanation to say they are purely informal

  • Reported: SyM 1.0b2 — Fri, 9 Mar 2012 05:00 GMT
  • Disposition: Resolved — SyM 1.0
  • Disposition Summary:

    An additional sentence needs to be added stating that the <<conformsTo>>, <<transformation>> and <<instanceOf>> stereotypes are purely informal

  • Updated: Sat, 7 Mar 2015 08:56 GMT

clarification needed for the fromLibrary attribute

  • Key: SYM_-1
  • Legacy Issue Number: 16593
  • Status: closed  
  • Source: Georgia Institute of Technology ( Chris Paredis)
  • Summary:

    In the SysML-Modelica Transformation Specification (http://www.omg.org/spec/SyM/1.0/Beta1/PDF/), the attribute fromLibrary for the stereotype «modelicaClassDefinition» is not sufficiently clearly defined (Section 8.2, page 10). The spec mentions that some details (e.g. "value properties and parts") can be omitted when using the fromLibrary tag, but the spec is not sufficiently precise as to which details exactly can/should be omitted and which should still be retained. Since this is a construct that will likely be used extensively, it should be defined more precisely.

  • Reported: SyM 1.0b2 — Wed, 12 Oct 2011 04:00 GMT
  • Disposition: Resolved — SyM 1.0
  • Disposition Summary:

    The identified issue does not relate to the mapping of language constructs between SysML and Modelica but rather to a user- and tool-specific usability aspect of the transformation. The issue therefore does not identify a problem with the specification. Additionally, the “fromLibrary” attribute of the «modelicaClassDefinition» stereotype will be removed since it does not relate to the mapping of language constructs between SysML and Modelica.

  • Updated: Sat, 7 Mar 2015 08:56 GMT