-
Key: UAF11-128
-
Status: closed
-
Source: Lockheed Martin ( Mrs. Laura E. Hart)
-
Summary:
<submission on behalf of James Johnson>
For completeness, consider listing ActualProject and ActualResource as CapableElements. Additionally, Achiever and Desirer should be listed as CapableElements. Please investigate and add if deemed appropriate. -
Reported: UAF 1.0 — Fri, 2 Feb 2018 15:17 GMT
-
Disposition: Resolved — UAF 1.1
-
Disposition Summary:
Actual Resource and Actual Service are now Capable Elements
It makes perfect sense to allow Exhibits relationship to be drawn between Actual Resource and Capability. The same applies to Actual Service as the Service Specification is Capable element. However, in case of Actual Project, we do not agree. Actual Project as well as project cannot directly exhibit capability. As for Achiever, all subtypes of achiever are already Capable elements except Actual Project. As for Desirer it would not make sense to have it as Capable Element because one of its subtypes is Capability. Capability cannot exhibit Capability.
-
Updated: Tue, 8 Oct 2019 17:49 GMT
-
Attachments:
- ActualResource.svg 423 kB (image/svg+xml)
- Actual_Resources_Traceability.svg 48 kB (image/svg+xml)
- Actual_Resources_Traceability.svg 70 kB (image/svg+xml)
- CapableElement.svg 189 kB (image/svg+xml)
- Resources_Traceability.svg 264 kB (image/svg+xml)
- Services_Traceability.svg 188 kB (image/svg+xml)
UAF11 — Inclusion of additional CapableElements
- Key: UAF11-128
- OMG Task Force: Unified Architecture Framework (UAF) 1.1 RTF