-
Key: SYSML17-86
-
Legacy Issue Number: 18434
-
Status: closed
-
Source: INCOSE ( Sanford Friedenthal)
-
Summary:
The allocate and requirements relationships (e.g., satisfy, verify, derive) do not explicitly state the degree to which these relationships apply. For example, a satisfy relationship may imply a model element may fully satisfy, partially satisfy, or not satisfy at all a particular requirement at a point in the design process. However, there is no standard way to refer to this partial vs complete satisfaction. A similar issue applies to the verify and derive relationships.
Note: Similar issues apply to allocate relationships where the allocate may indicate that the element is fully or partially allocated to another element.
The SysML spec should consider incorporating a tagged value to indicate 0, partial or complete on these relationships.
-
Reported: SysML 1.3 — Fri, 8 Feb 2013 05:00 GMT
-
Disposition: Closed; Out Of Scope — SysML 1.7
-
Disposition Summary:
Proposal: Inability to specify partial allocation and requriements satisfaction
New features are out-of-scope for SysML 1.7 and should be covered by SysML v2 if necessary for SysML.
-
Updated: Thu, 22 Dec 2022 13:45 GMT
SYSML17 — Inability to specify partial allocation and requriements satisfaction
- Key: SYSML17-86
- OMG Task Force: SysML 1.7 RTF