SysML 1.6 RTF Avatar
  1. OMG Issue

SYSML16 — NestedConnectorEnd violates UML "roles" constraint

  • Key: SYSML16-182
  • Legacy Issue Number: 19813
  • Status: closed  
  • Source: Anonymous
  • Summary:

    UML's constraint "UML::Connector::role" specifies that ConnectorEnds need to point to roles/parts owned by the Connector's structuredClassifier (direct or inherited).

    The specification draft 1.0 contained an explicit statement that SysML relaxed a limited number of the UML constraints ("roles" being one of them). This was e.g. mentioned in 0.11 on page 4 of document ad/2006-03-01.

    In the current 1.4 beta, section 4.4 "Extension Mechanisms" doesn't mention contraint relaxation as one of the applied techniques.

    Moreover, the specification of NestedConnectorEnd (, does not mention this relaxation either.

    Without a formal statement about this relaxation, I would conclude that the SysML spec conflicts with the UML spec.

  • Reported: SysML 1.4 — Tue, 30 Jun 2015 04:00 GMT
  • Disposition: Closed; No Change — SysML 1.6
  • Disposition Summary:

    Contraint relaxed concerning nestedConnectorEnds

    This is described in SysML 1.5 so no change is required: Block
    [9]The following constraint under 9.3.7, “ConnectorEnd” in the UML 2 standard is removed by SysML: “[3] The property held in self.partWithPort must [sic] not be a Port.”

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