-
Key: SYSML2-80
-
Status: closed
-
Source: Model Driven Solutions ( Mr. Ed Seidewitz)
-
Summary:
The reflective SysML model in the SysML Systems Library has the following inconsistencies with the normative SysML abstract syntax:
1. The feature AnalysisCaseUsage::analysisAction should subset usage, not feature.
2. The features of Definition, RequirementDefinition and Usage should have the same order as the properties of the corresponding metaclasses in the abstract syntax.
3. The feature ViewDefinition::satisfiedViewpoint should subset ownedRequirement, not ownedUsage.
4. The feature ViewDefinition::viewRendering should not subset ownedUsage.
5. The feature ViewUsage::satisfiedViewpoint should subset ownedRequirement, not ownedUsage.
6. The feature ViewUsage::viewRendering should not subset ownedUsage.
-
Reported: SysML 2.0a1 — Thu, 27 Apr 2023 20:59 GMT
-
Disposition: Resolved — SysML 2.0b2
-
Disposition Summary:
Regenerate the SysML.sysml model file
The SysML.sysml file is generated from the normative SysML abstract syntax. The reported errors were due to the file not being properly regenerated subsequent to some final abstract syntax updates before submission. The file should now be regenerated, not only to correct the reported errors, but also to reflect all other abstract syntax changes approved by the FTF.
-
Updated: Tue, 1 Jul 2025 14:50 GMT
SYSML2 — Reflective SysML abstract syntax model has inconsistencies
- Key: SYSML2-80
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF