-
Key: SYSML2_-349
-
Status: open
-
Source: DEKonsult ( Mr. Hans Peter de Koning)
-
Summary:
In subclause 7.20.1, Table 19, example "Requirement" the compartment labels "require constraints" and "assume constraints" and their content are misleading and inconsistent.
- Besides pure "require ConstraintUsage" statements a "require constraints" compartment may also contain "require RequirementUsage" statements. Furthermore, a "require RequirementUsage" has the same semantics as a composite RequirementUsage owned by a containing RequirementUsage (see explanation in subclause 7.20.2). Therefore a better compartment name is possibly "requires".
- Similarly besides pure "assume ConstraintUsage" statement an "assume constraints" compartment may also contain "assume RequirementUsage" statements. Therefore a better compartment name is possibly "assumes".
-
Reported: SysML 2.0b2 — Wed, 16 Oct 2024 14:07 GMT
-
Updated: Sat, 11 Jan 2025 22:26 GMT
SYSML2_ — Inconsistent compartment labels
- Key: SYSML2_-349
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF 2