OMG System Modeling Language Avatar
  1. OMG Specification

OMG System Modeling Language — Open Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
SYSML17-150 Owned properties of an InterfaceBlock SysML 1.5 open
SYSML17-185 Sample problem diagrams are inconsistent, need to refactor from integrated model SysML 1.5 open
SYSML17-152 Parameter direction typo in XMI SysML 1.5 open
SYSML17-255 BDD representation of activity hierarchy SysML 1.5b1 open
SYSML17-159 Reference Properties do not reference properties SysML 1.5 open
SYSML17-176 SysML::Trace relationship is not specialized from UML::Trace in the XMI SysML 1.5 open
SYSML17-177 SysML::Refine relationship is not specialized from UML::Refine in the XMI SysML 1.5 open
SYSML17-167 Description of AdjunctProperty SysML 1.5 open
SYSML17-160 DirectedFeature is confusing SysML 1.5 open
SYSML17-156 Replace UML4SysML::Kernel by UML4SysML::Generalization SysML 1.5 open
SYSML17-157 Typos/editorials found in the SysML 1.5 specification document SysML 1.5 open
SYSML17-172 ConnectorProperty is redundant SysML 1.5 open
SYSML17-161 Add Graphical notation for General Classifier SysML 1.5 open
SYSML17-174 Connectors are not allowed in bdd SysML 1.5 open
SYSML17-165 Typo in revised text of issue SYSML16-289 SysML 1.5 open
SYSML17-158 Statements missing in the abstract syntax description SysML 1.5 open
SYSML17-173 Combined call-out notation not allowed SysML 1.5 open
SYSML17-154 Clarification of typing a binding connector SysML 1.5 open
SYSML17-184 Inappropriate character for multiplying symbol with combined units SysML 1.5 open
SYSML17-175 Do not move deprecated elements SysML 1.5 open
SYSML17-170 DistributedProperty should be abstract SysML 1.5 open
SYSML17-168 DistributedProperty should be abstract SysML 1.5 open
SYSML17-169 Diagram header is not intuitively interpreted SysML 1.5 open
SYSML17-163 Excluded UML metaclasses are not formally defined SysML 1.5 open
SYSML17-162 Add signal to constraint [1] for DistributedProperty SysML 1.5 open
SYSML17-153 Replace all occurrences of "has been" by "is" SysML 1.5 open
SYSML17-148 Owning Block definition is unclear SysML 1.5 open
SYSML17-171 DistributedProperty shall have an operation that checks whether a value is conform to the constraints of the distribution SysML 1.5 open
SYSML17-164 SysML 1.6 should be based on UML 2.5.1 SysML 1.5 open
SYSML17-155 Inconsistency in the DirectedRelationshipPropertyPath specification SysML 1.5 open
SYSML17-149 FullPort type SysML 1.5 open

Issues Descriptions

Owned properties of an InterfaceBlock

  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    Split from SYSML16-86:

    What are possible owned properties of the InterfaceBlock? Values, FlowProperties? other? In 9.1 InterfaceBlock it is not flow nor value

  • Reported: SysML 1.5 — Thu, 16 Mar 2017 07:43 GMT
  • Updated: Sat, 4 Jul 2020 14:51 GMT

Sample problem diagrams are inconsistent, need to refactor from integrated model

  • Status: open  
  • Source: Thematix Partners LLC ( Rick Steiner)
  • Summary:

    The diagrams in Annex D are in many ways inconsistent with each other. Fixing existing issues with each individual diagram will tend to make this problem worse, instead of better. For consistency's sake, the set of diagrams in Annex D needs to be generated from an integrated model as existing issues are addressed.

  • Reported: SysML 1.5 — Fri, 8 Mar 2019 19:15 GMT
  • Updated: Thu, 2 Jul 2020 13:00 GMT


BDD representation of activity hierarchy

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    I would question whether it was correct to change section 11.3.1.1 "Activity" by replacing the BDD representation of activity hierarchy (as per v1.3) with adjunct action properties (introduced in v1.4). Whilst the latter is possible with the AdjunctProperty facility, the prior method, inherited from UML, is still valid. That is, unless the UML activity hierarchy is expressly deprecated from SysML. Even then, it will leave end users with the question of what the additional benefit is of the adjunct property as applied to call behaviour actions.

  • Reported: SysML 1.5b1 — Thu, 19 Sep 2019 15:45 GMT
  • Updated: Sun, 16 Feb 2020 15:25 GMT
  • Attachments:

Reference Properties do not reference properties

  • Status: open  
  • Source: Thematix Partners LLC ( Rick Steiner)
  • Summary:

    A reference property of a Block may only be typed by (i.e. "reference") another Block. There is no current mechanism for a reference property to explicitly reference a part property of a different block. See Figure D.16 for example; the PowerSubsystem Block is assumed to be referencing the part property of the BrakeSubsystem typed by BrakePedal. This is a logical conclusion since there is only one part property typed by BrakePedal, but if there were multiple part properties typed by BrakePedal, the reference property of the PowerSubsystem Block would be ambiguous.

    Practical use of reference properties has consistently implied that a particular part property CAN be referenced (i.e. "a part property owned by another block"), but no mechanism for this is explicitly provided in SysML. Also, there does not appear to be any constraint on instance semantics of reference properties that might clarify this ambiguity at the instance level.

    See also SYSML16-42 and SYSML16-228.

  • Reported: SysML 1.5 — Tue, 17 Oct 2017 00:17 GMT
  • Updated: Sat, 15 Feb 2020 01:48 GMT

SysML::Trace relationship is not specialized from UML::Trace in the XMI

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    The SysML::Trace stereotype is a specialization of the UML::Trace stereotype defined in the StandardProfile.

    In the SysML XMI the SysML::Trace stereotype has no generalization relationship to the UML::Trace stereotype. It is just a stereotype extending UML::Abstraction.

  • Reported: SysML 1.5 — Tue, 15 Jan 2019 09:53 GMT
  • Updated: Mon, 27 Jan 2020 00:16 GMT

SysML::Refine relationship is not specialized from UML::Refine in the XMI

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    The SysML::Refine stereotype is a specialization of the UML::Refine stereotype defined in the StandardProfile.

    In the SysML XMI the SysML::Refine stereotype has no generalization relationship to the UML::Refine stereotype. It is just a stereotype extending UML::Abstraction.

  • Reported: SysML 1.5 — Tue, 15 Jan 2019 09:55 GMT
  • Updated: Mon, 27 Jan 2020 00:16 GMT

Description of AdjunctProperty

  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    The first sentence of the description of the Adjunct property stereotype does not make sense:
    "The AdjunctProperty stereotype can be applied to properties to constrain their values to the values of connectors typed by association blocks, call actions, object nodes, variables, parameters, interaction uses, and submachine states"

  • Reported: SysML 1.5 — Mon, 7 May 2018 12:13 GMT
  • Updated: Mon, 27 Jan 2020 00:16 GMT

DirectedFeature is confusing

  • Status: open  
  • Source: Software Centre of Excellence, Rolls-Royce Div. ( Dave Banham)
  • Summary:

    The intended use for the <<DirectedFeature>> stereotype is not at all clear from its specification in section 9.3.2.4 in SysML 1.5. To be clear, the current description describes what it is, but not why it is required, or how a modeller might use it. Moreover, it is not clear whether it specifically applies to ports (since its part of the section that specifies the language facilities for ports and flows (section 9), or whether it relates to features (properties?) of a block that are not ports.

    The issue was discussed at the RTF meeting of 2017-10-12 as a result of discussing issue http://issues.omg.org/browse/SYSML16-108. There was little consensus on what DirectedFeature is, although Conrad suggested the following (being my interpretation of what was said):
    A DirectedFeature of a block describes whether the block implements that feature (it's "provided") or that the feature is represents a conceptually virtualised feature as an "assumption" that something else in the model will provide it. The fulfilment of the required assumption with an actually provided realisation of that feature is by a connector between the required and the provided features.

    The problem with this interpretation is that it seems to have nothing to do with ports! There is of course further scope for confusion with the UML notation of provided and required interfaces on UML ports.
    At the very least, some examples that clearly illustrate what problem DirectedFeature solves and the types of model elements that it is to be applied to would help a lot.

  • Reported: SysML 1.5 — Thu, 12 Oct 2017 16:39 GMT
  • Updated: Mon, 27 Jan 2020 00:16 GMT

Replace UML4SysML::Kernel by UML4SysML::Generalization

  • Status: open  
  • Source: Commissariat a l Energie Atomique-CEA ( Benoit Maggi)
  • Summary:

    In SysML 1.5 pdf document ( p 147 Table 14.2- Graphical paths included in Use Case diagrams)

    Latest element in the table :

    • Path name: Generalization
    • Concrete Syntax : ->
    • Abstract Syntax Reference : UML4SysML::Kernel
      => it should be UML4SysML::Generalization

    Also present in SysML 1.4 pdf version

  • Reported: SysML 1.5 — Wed, 30 Aug 2017 15:13 GMT
  • Updated: Mon, 27 Jan 2020 00:16 GMT

Typos/editorials found in the SysML 1.5 specification document


ConnectorProperty is redundant

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    The ConnectorProperty is redundant. The same feature is provided by AdjunctProperty.

    see slide 17: http://tinyurl.com/ybvdx6ew

  • Reported: SysML 1.5 — Thu, 27 Sep 2018 18:26 GMT
  • Updated: Tue, 24 Sep 2019 08:18 GMT

Add Graphical notation for General Classifier

  • Status: open  
  • Source: Lockheed Martin ( Charles Galey)
  • Summary:

    The usage of Generalization in SysML is a key part of establishing Domain Specific Languages and contexts for models. In particular it has great ability to establish reusability within our models. However, the only mechanism via which we can visually denote the nature of an object is via non-normative extensions to M2 via stereotypes such as <<Car>> or other examples. This is undesirable, we should have the ability (on classes and parts typed by those classes) to optionally display the General (or any General class of a Block) classifier of a Block on BDD's, IBD's and Parametric diagrams. This will, greatly enhance the readability of our diagrams, remove the complexity of implementing M2 stereotypes simply designed for visualization, and expose via the diagram usage of reusable libraries to make the foundation of our models.

    Example Format might be (in ASCII art):

    ------------
    <<Block>>
    [Car]
    Porsche
    --------------

  • Reported: SysML 1.5 — Fri, 20 Oct 2017 05:22 GMT
  • Updated: Fri, 28 Jun 2019 11:50 GMT

Connectors are not allowed in bdd

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    Figure D.23 depicts two blocks with ports that are connected by a connector.

  • Reported: SysML 1.5 — Thu, 29 Nov 2018 09:33 GMT
  • Updated: Tue, 23 Apr 2019 00:20 GMT
  • Attachments:

Typo in revised text of issue SYSML16-289

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    Typos in revised text for Annex C

    • Change "C.1.1 and C.1.2" to "C.1.2 and C.1.3".
    • Change "C.5 through C.7" to "C.4 through C.7".
  • Reported: SysML 1.5 — Mon, 5 Mar 2018 20:42 GMT
  • Updated: Tue, 23 Apr 2019 00:20 GMT

Statements missing in the abstract syntax description

  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    The description of stereotypes in the abstract syntax is missing all the "base_xxx" attributes that refer to the instances of extended elements. However this is required in order to specify the corresponding multiplicity and redefinition, if any.

    In addition, it should also be specified whether the corresponding stereotype is "required" or not. At that time, the only way to know it is to parse the normative XMI file.

  • Reported: SysML 1.5 — Thu, 21 Sep 2017 07:18 GMT
  • Updated: Tue, 23 Apr 2019 00:20 GMT

Combined call-out notation not allowed

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    Figure D.25 depicts a allocate call-out notation that represents more than one call-out relationship. I don't think that it is allowed.

  • Reported: SysML 1.5 — Thu, 29 Nov 2018 09:36 GMT
  • Updated: Mon, 25 Mar 2019 23:03 GMT

Clarification of typing a binding connector


Inappropriate character for multiplying symbol with combined units

  • Status: open  
  • Source: Schindler Aufzüge AG ( Markus WALKER)
  • Summary:

    Some of the combined units use a period character instead of a multiply symbol. An example is the unit ‹newton metre› where the symbol is ‹N.m›. In contrary, other units make use of the middle dot character, e.g., ‹kilogram metre squared per second›, using the symbol ‹kg · m 2/s›.

    The SI Guide prescribes to use a middle dot or a thin space or if not ambiguous no character to combine different units that are multiplied.

  • Reported: SysML 1.5 — Fri, 22 Feb 2019 16:04 GMT
  • Updated: Thu, 14 Mar 2019 14:45 GMT

Do not move deprecated elements


DistributedProperty should be abstract

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    The DistributedProperty itself does not make sense. As specified in the specification specific distributions should be defined as subclasses of the DistributedProperty stereotype. Therefore, the stereotype should be abstract.

  • Reported: SysML 1.5 — Thu, 27 Sep 2018 17:05 GMT
  • Updated: Thu, 7 Mar 2019 16:44 GMT

DistributedProperty should be abstract

  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    The DistributedProperty stereotype should be abstract since it needs to be specialized in order to be usable.

  • Reported: SysML 1.5 — Mon, 7 May 2018 12:45 GMT
  • Updated: Thu, 7 Mar 2019 16:43 GMT

Diagram header is not intuitively interpreted

  • Status: open  
  • Source: INCOSE / SSI ( Troy Peterson)
  • Summary:

    The SysML diagram header is not easily interpreted. Suggest a new format that provides the same information and content but following the typical naming convention used in SysML - i.e. name:Type

    Suggestion/Example:

    From:
    req [Package] Auto_Specification [Automobile System Requirements]

    To:
    Automobile System Requirements:req | Auto_Specification:Package

    Optional format adds "[req]" as an option to turn on to in bold or white text on a black background filling the header box around the diagram kind "req" in this case. Image examples provided to Rick Steiner and Sandy Friedenthal in separate communications.

    [req] Automobile System Requirements:req | Auto_Specification:Package

  • Reported: SysML 1.5 — Thu, 13 Sep 2018 04:34 GMT
  • Updated: Thu, 7 Mar 2019 16:40 GMT

Excluded UML metaclasses are not formally defined

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    Table 4.1. excludes several UML metaclasses from SysML. However, figure 4.2 shows that the SysML profile imports the whole UML. Instead, the SysML profile should use the metamodelReference and metaclassReference properties to import only the included elements.

  • Reported: SysML 1.5 — Fri, 9 Feb 2018 12:54 GMT
  • Updated: Thu, 28 Feb 2019 14:40 GMT

Add signal to constraint [1] for DistributedProperty

  • Status: open  
  • Source: Bombardier Transportation ( Karsten Koechlin)
  • Summary:

    At the moment the stereotype distrubtedProperty is only allowed to be applied to properties of classifier stereotyped by Block or ValueType.
    We would like to apply the distributedProperty stereotype also to properties of classifier stereotyped by Signal.
    Reason: The properties of a block are transmitted by signal properties, the properties of the signal should also reflect the distribution.

  • Reported: SysML 1.5 — Mon, 22 Jan 2018 12:43 GMT
  • Updated: Thu, 28 Feb 2019 14:24 GMT

Replace all occurrences of "has been" by "is"

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    In several places of the SysML specification document the term "has been" is used. It should be replaced by "is".

  • Reported: SysML 1.5 — Tue, 6 Jun 2017 07:44 GMT
  • Updated: Thu, 21 Feb 2019 16:37 GMT

Owning Block definition is unclear

  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    The definition of owning block for proxy port given in the description sub-section of 9.3.2.7 FlowProperty is unclear and misleading. It should be reworded and moved to the ProxyPort description

  • Reported: SysML 1.5 — Thu, 2 Mar 2017 15:41 GMT
  • Updated: Thu, 21 Feb 2019 16:09 GMT

DistributedProperty shall have an operation that checks whether a value is conform to the constraints of the distribution

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    While it is not possible to check if a value conforms to, for example, uniform or mean distribution, it is possible to check, if it conforms to constraints of the specified distribution. For example, the minimum and maximum values of a uniform distribution.

  • Reported: SysML 1.5 — Thu, 27 Sep 2018 17:14 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT

SysML 1.6 should be based on UML 2.5.1

  • Status: open  
  • Source: oose Innovative Informatik eG ( Tim Weilkiens)
  • Summary:

    SysML should be based on the newest available UML specification. Current UML specification is version 2.5.1. SysML 1.5. is still based on UML 2.5.

  • Reported: SysML 1.5 — Fri, 23 Feb 2018 14:29 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT

Inconsistency in the DirectedRelationshipPropertyPath specification

  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    Some DirectedRelationshipPropertyPath constraint definitions assume that the relationship on which this stereotype is applied is binary but there is no formal constraint enforcing it.

  • Reported: SysML 1.5 — Thu, 10 Aug 2017 12:27 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT

FullPort type

  • Status: open  
  • Source: Airbus Group ( Yves Bernard)
  • Summary:

    Split from SYSML16-86:

    What is the type of FullPort? Spec says nothing

  • Reported: SysML 1.5 — Thu, 16 Mar 2017 07:42 GMT
  • Updated: Sun, 13 Jan 2019 15:32 GMT