Issue 13345: Merge UML DataType into SysML ValueType (sysml-rtf) Source: Deere & Company (Mr. Roger Burkhart, burkhartrogerm(at)johndeere.com) Nature: Revision Severity: Significant Summary: Even though SysML ValueType includes all the capabilities of UML DataType, plus its own optional extensions, SysML currently both of these separately in its diagram elements and abstract syntax. This adds unnecessarily to the complexity of the specification (where both DataType and ValueType must be mentioned in multiple places) and to the language that the SysML user must learn. It's inconsistent with other renaming of UML elements by SysML, in which the neutral SysML term (e.g. Block) replaces the UML term (e.g. Class). Just as SysML Block replaces the UML term Class, there's no reason the SysML term ValueType can't replace the UML term DataType. Statement of OCL constraints and metamodel and diagram syntax specifications can be simplified as a result. Resolution: Because ValueType includes all capabilities UML DataType, plus its own optional extensions, no user need for keeping them both was identified during discussions within the RTF. In SysML user models, there’s no reason that the SysML term ValueType can’t replace the UML term DataType, in the same way that the SysML term Block replaces the UML term Class. In both cases, the substitute terms were chosen to be less software-specific than possibly appropriate for use by system modelers. Regardless of this rationale, consolidating to just ValueType simplifies the language including the specification of diagram elements and constraints. Revised Text: In Table 8.1, remove the row with “DataType” in the Element Name column. In the second sentence of Section 8.3.2.1 BindingConnector, replace “typed by a DataType or ValueType” with “typed by a ValueType”. In the sixth paragraph of Section 8.3.2.2 Block, replace “A property typed by a UML DataType or SysML ValueType” with “A property typed by a SysML ValueType”. in Constraint [6] of Section 8.3.2.2 Block, replace “typed by a UML DataType or SysML ValueType” with “typed by a SysML ValueType”. In Constraint [2] of Section 8.3.2.6 NestedConnectorEnd, replace “must be contained in the Block, DataType, or ValueType” with “must be contained in the Block or ValueType”. In Section 8.3.2.10 ValueType, remove the last paragraph of the Description subsection, which currently reads: If none of the additional characteristics of a SysML ValueType are required, then UML DataType may be used. In the second paragraph of Section 9.3.2.3 FlowPort, replace “classified by a single Block, ValueType, DataType, or Signal classifier” with “classified by a single Block, ValueType, or Signal classifier”. In the third paragraph of Section 9.3.2.3 FlowPort, replace “typed by a Block, ValueType, DataType, or Signal classifier” with “typed by a Block, ValueType, or Signal classifier”. In Constraint [1] of Section 9.3.2.3 FlowPort, replace “typed by a FlowSpecification, Block, Signal, DataType, or ValueType” with “typed by a FlowSpecification, Block, Signal, or ValueType”. In Constraint [1] of Section 9.3.2.4 FlowProperty, replace “typed by a ValueType, DataType, Block, or Signal” with “typed by a ValueType, Block, or Signal”. In the first paragraph of Section 11.3.1.4 ObjectNode, replace “(blocks or datatypes)” with “(blocks or value types)”. Actions taken: January 26, 2009: received issue January 12, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 26 Jan 2009 15:23:26 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Roger Burkhart Company: Deere & Company mailFrom: burkhartrogerm@johndeere.com Notification: No Specification: SysML 1.1 Section: 8 FormalNumber: formal/2008-11-02 Version: 1.1 RevisionDate: 11/08 Page: 32-70 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; MS-RTC LM 8; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022) Description Issue: Merge UML DataType into SysML ValueType. Discussion: Even though SysML ValueType includes all the capabilities of UML DataType, plus its own optional extensions, SysML currently both of these separately in its diagram elements and abstract syntax. This adds unnecessarily to the complexity of the specification (where both DataType and ValueType must be mentioned in multiple places) and to the language that the SysML user must learn. It's inconsistent with other renaming of UML elements by SysML, in which the neutral SysML term (e.g. Block) replaces the UML term (e.g. Class). Just as SysML Block replaces the UML term Class, there's no reason the SysML term ValueType can't replace the UML term DataType. Statement of OCL constraints and metamodel and diagram syntax specifications can be simplified as a result.