UAF 1.3b1 RTF Avatar
  1. OMG Issue

UAF13 — Enable a Requirement Relationship between AbstractReqirement and Capability

Open Closed All
  • Key: UAF13-43
  • Status: closed  
  • Source: MITRE ( Ms. Rae Anderson)
  • Summary:

    The only allowable relationship between <<Capability>> and any Requirement element is <<trace>>. In US Department of Defense acquisition processes, stakeholder needs are defined as capabilities within a Capability Description Document. These capabilities are high-level system requirements from which system and sub-system requirements should be derived. The recommended solution is to enable the <<deriveReqt>> to have <<Capability>> as the target and any type of <<AbstractRequirement>> as the source of a <<deriveReqt>> relationship. An alternative would be the <<refine>> requirement relationship.
  • Reported: UAF 1.2b1 — Sun, 29 May 2022 20:33 GMT
  • Disposition: Deferred — UAF 1.3b1
  • Disposition Summary:

    UAF RTF 1.3 scope is limited to Mission Engineering only

    Out of scope for 1.3
  • Updated: Mon, 24 Mar 2025 13:35 GMT