OMG System Modeling Language Avatar
  1. OMG Specification

OMG System Modeling Language — Open Issues

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

Issues Descriptions

Incorrect statement about UML n-aries

  • Key: SYSML16-69
  • Legacy Issue Number: 16093
  • Status: open  
  • Source: NIST ( Conrad Bock)
  • Summary:

    Section 8.3.1.3 (UML Diagram Elements
    not Included in SysML Block Definition
    Diagrams) says "N-ary associations,
    shown in UML by a large open diamond
    with multiple branches, can be modeled
    by an intermediate block with no loss in
    expressive power." An intermediate
    block cannot capture multiplicities that
    would be on an the ends of an n-ary
    association. These multiplicities are
    for the links from end to end, rather
    than from intermediate object to end, as
    they would be with an intermediate
    object. However, intermediate blocks
    can specify the number of links each end
    might participate in for any of the
    other n-1 ends, which is not possible
    with n-ary associations. The
    expressiveness of n-aries and
    intermediate blocks is overlapping,
    rather than equivalent.

  • Reported: SysML 1.2 — Tue, 22 Mar 2011 04:00 GMT
  • Updated: Sat, 18 Nov 2017 00:57 GMT

Item flows can have multiple types but item properties cannot

  • Key: SYSML16-66
  • 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: Thu, 16 Mar 2017 07:37 GMT

Description of Item Flows

  • Key: SYSML16-64
  • 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: Thu, 16 Mar 2017 07:37 GMT

Blocks cannot own items flows

  • Key: SYSML16-62
  • 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: Thu, 16 Mar 2017 07:35 GMT

IBD notation doesn't distinguish item properties from connector labels

  • Key: SYSML16-63
  • 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: Thu, 16 Mar 2017 07:28 GMT

Definition of part

  • Key: SYSML16-68
  • 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: Mon, 6 Mar 2017 14:18 GMT

Lightweight representations of faults, failures, hazards and off-nominal conditions and behavior

  • Key: SYSML16-79
  • Legacy Issue Number: 16657
  • Status: open  
  • Source: INCOSE ( Sanford Friedenthal)
  • Summary:

    There is a critical need to model off nominal conditions and behavior associated with faults, failures, and hazards. However, there currently is no standard way to represent this in the SysML model. This issue is intended to provide some lightweight and standardized and light-weight capability for this type of modeling, such as a trigger on a state machine with the stereotype failure or a fault stereotype to represent a fault condition. There is a separate profile (not standardized) that was developed by Bruce Powell Douglass that provides a broader more comprehensive capability that could be leveraged as source material.

  • Reported: SysML 1.2 — Thu, 10 Nov 2011 05:00 GMT
  • Updated: Thu, 23 Feb 2017 12:52 GMT

TestCase should use PackageMerge

  • Key: SYSML16-73
  • 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: Tue, 21 Feb 2017 16:18 GMT

Association owning ends

  • Key: SYSML16-72
  • 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: Tue, 21 Feb 2017 16:17 GMT