-
Key: UMLTP23-3
-
Status: closed
-
Source: Lockheed Martin ( Ms. Annemarie Kibbe)
-
Summary:
Will SysML2 <<verify>> and UTP2 <<verifies>> stereotypes become the same eventually? This is a stereotype that seems like it could become the same in both specs if worked between groups. The different stereotypes lead to unnecessary complexity which hurts adoption for users trying to use both specs.
Section 8.3.1.4.5 describes verifies.
-
Reported: UTP2 2.2b1 — Sat, 23 Dec 2023 02:25 GMT
-
Disposition: Closed; Out Of Scope — UTP2 2.3b1
-
Disposition Summary:
Harmonization of UTP 2.x and SysMLv2 is out of scope
The RTF agreed to close this issue:
SysMLv2 is based on KerML, therefore, compatibility is not given. UTP2 as well as SysMLv1.x is based on UML 2.x and the UML2 profiling mechanism which is not supported by SysMLv2
UTP2 is aligned with SysMLv1.x, i.e., UTP2::verifies is technically and partially semantically compatible with SyML::verify. -
Updated: Mon, 24 Mar 2025 13:34 GMT
UMLTP23 — Verifies vs verify relationship
- Key: UMLTP23-3
- OMG Task Force: UML Testing Profile 2 (UTP2) 2.3 RTF