-
Key: SYSML2_-424
-
Status: closed
-
Source: Airbus Group ( Mr. Yves Bernard)
-
Summary:
SYSML2_-403change semantics and the class hierarchy for FlowConnectionUsage and therefor impact the specification of the transformation that is related to that class -
Reported: SysML 2.0b2 — Fri, 20 Dec 2024 17:43 GMT
-
Disposition: Resolved — SysML 2.0b4
-
Disposition Summary:
Modify the specification of the transformation
The following classes defined in the model of the v1 to v2 transformation are impacted by
SYSML2_-403:- ToFlowConnectionUsage_Init
- ObjectFlow_Mapping
- InformationFlow_Mapping
For the latter class (i.e. InformationFlow_Mapping), InformationFlow that is the UML metaclass, that is specified as its source element, has semantics of structural relationship. So, it shall not be mapped to a FlowConnectionUsage anymore. Instead, this resolution propose to map it to ConnectionUsage, in cases where the InformationFlow is realized by one (or more) connector or associations. In the other cases, this proposal does not provide mappings.
-
Updated: Sat, 19 Jul 2025 19:25 GMT
SYSML2_ — Adopted resolution SYSML2_-403 has impact on the v1 to v2 Transformation
- Key: SYSML2_-424
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF 2