Issue 19813: NestedConnectorEnd violates UML "roles" constraint (sysml-rtf) Source: (, ) Nature: Clarification Severity: Minor 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 (8.3.1.2.6, 8.3.2.11) 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. Resolution: Revised Text: Actions taken: June 30, 2015: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 30 Jun 2015 07:04:40 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Johan Van Noten Employer: mailFrom: johan@qootec.be Terms_Agreement: I agree Specification: OMG Systems Modeling Language Section: 4.4 FormalNumber: ptc/2013-12-09 Version: 1.4 beta Doc_Year: 2013 Doc_Month: December Doc_Day: 09 Page: 48 Title: NestedConnectorEnd violates UML "roles" constraint Nature: Clarification Severity: Minor CODE: 3TMw8 B1: Report Issue Remote Name: 213-224-27-206.ifiber.telenet-ops.be Remote User: HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko Time: 07:04 AM Description: 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 (8.3.1.2.6, 8.3.2.11) 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.