-
Key: SYSML2_-417
-
Status: open
-
Source: Ansys Government Initiatives ( Mr. Richard Page)
-
Summary:
After resolution
SYSML2_-403to issueSYSML2_-173, FlowConnectionDefinition no longer specializes ConnectionDefinition (now specializing only ActionDefinition and KerML Interaction), and FlowConnectionUsage no longer specializes ConnectionUsage (now only specializing ActionUsage, ConnectorAsUsage and KerML ItemFlow. As a result ofSYSML2_-403, having "Connection" in the name of the "Flow" classes causesconfusion among users that don't see the distinction between structure and behavior.Renaming FlowConnectionDefinition to FlowDefinition and FlowConnectionUsage to FlowUsage would avoid confusion going forward. Not making this change prior to finalization of SysML v2 runs the risk of having confusion that would require complex deprecation steps to correct later.
Similarly for SuccessionFlowConnectionUsage, which specializes FlowConnectionUsage.
-
Reported: SysML 2.0b2 — Wed, 11 Dec 2024 21:29 GMT
-
Updated: Wed, 18 Dec 2024 17:32 GMT
SYSML2_ — Remove "Connection" from the names "FlowConnectionDefinition", "FlowConnectionUsage", and "SuccessionFlowConnectionUsage"
- Key: SYSML2_-417
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF 2