OMG System Modeling Language Avatar
  1. OMG Specification

OMG System Modeling Language — Open Issues

  • Acronym: SysML
  • Issues Count: 7
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

IBD notation doesn't distinguish item properties from connector labels

  • Key: SYSML17-55
  • Legacy Issue Number: 15983
  • Status: open  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Item properties and connector labels both appear in colon notation near the center of an assocation. How do you tell the difference?

  • Reported: SysML 1.2 — Tue, 25 Jan 2011 05:00 GMT
  • Updated: Sun, 30 Jun 2019 10:31 GMT
  • Attachments:

Definition of part

  • Key: SYSML17-59
  • Legacy Issue Number: 16058
  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    The current definition of "part" includes
    ports. Is that intended?

  • Reported: SysML 1.2 — Fri, 11 Mar 2011 05:00 GMT
  • Updated: Sun, 30 Jun 2019 09:46 GMT

TestCase should use PackageMerge

  • Key: SYSML17-63
  • Legacy Issue Number: 16286
  • Status: open  
  • Source: KnowGravity Inc. ( Markus Schacher)
  • Summary:

    The stereotype «TestCase» is primarily specified in the UML Testing Profile (UTP) and should not be defined by SysML redundantly (or even inconsistently). Rather it should be separated in a dedicated package in SysML and a PackageMerge be specified. This would properly add the properties of a «TestCase» specified in SysML to the "base" «TestCase» specified in UTP.

  • Reported: SysML 1.2 — Fri, 27 May 2011 04:00 GMT
  • Updated: Wed, 30 Jan 2019 18:21 GMT

Association owning ends

  • Key: SYSML17-62
  • Legacy Issue Number: 16263
  • Status: open  
  • Source: The MathWorks ( Alan Moore)
  • Summary:

    Associations in SysML should be able to own their ends. Otherwise modelers can't add an association between blocks in model libraries they do not have permission to modify. They also cannot create association that are non-navigable in both directions, which might be useful for directing flows across them into flows contained by the association as a block.

  • Reported: SysML 1.2 — Wed, 25 May 2011 04:00 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT

Item flows can have multiple types but item properties cannot

  • Key: SYSML17-58
  • Legacy Issue Number: 16042
  • Status: open  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Item flows can have multiple types but item properties cannot

  • Reported: SysML 1.2 — Wed, 23 Feb 2011 05:00 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT

Description of Item Flows

  • Key: SYSML17-56
  • Legacy Issue Number: 15985
  • Status: open  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Description of item flow and its attributes should explain that "assign" means "realization", change "usage" to "instance", and convey items rather than classifiers.

  • Reported: SysML 1.2 — Tue, 25 Jan 2011 05:00 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT

Blocks cannot own items flows

  • Key: SYSML17-54
  • Legacy Issue Number: 15982
  • Status: open  
  • Source: NASA ( Nicolas Rouquette)
  • Summary:

    Blocks cannot own items flows, because UML NameSpace abstractly owns NamedElement. Consider specializing on blocks to own item flows.

  • Reported: SysML 1.2 — Tue, 25 Jan 2011 05:00 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT