SysML 1.6 RTF Avatar
  1. OMG Issue

SYSML16 — SysML::Block constraint#3 containts an incorrect assertion about UML

  • Key: SYSML16-310
  • Status: closed  
  • Source: Airbus Group ( Mr. Yves Bernard)
  • Summary:

    SysML::Block constraint#3 states the following


    In the UML metamodel on which SysML is built, any instance of the Property metaclass that is typed by a block (a Class with the «block» stereotype applied) and which is owned by an Association must [sic] not have a name and may not be defined as a navigable owned end of the association. (While the Property has a “name” property as defined by its NamedElement superclass, the value of the “name” property, which is optional, must be missing.)

    However there is no constraint in UML requiring that ends owned by the association have empty names. SysML can possibly require it but the added value is not obvious. I suggest focusing this constraint on the link between navigability and end ownership:

    Any instance of the Property metaclass that is typed by a block (a Class with the «block» stereotype applied) and which is owned by an Association may not be defined as a navigable owned end of the association.

  • Reported: SysML 1.5 — Thu, 6 Jul 2017 11:49 GMT
  • Disposition: Duplicate or Merged — SysML 1.6
  • Disposition Summary:

    To be merged with the formalization of SysML constraints (SYSML16-274)

    To be merged with the formalization of SysML constraint which includes adding them explicitly in the model of the SysML profile

  • Updated: Mon, 1 Apr 2019 18:17 GMT