United Architecture Framework Avatar
  1. OMG Specification

United Architecture Framework — Open Issues

  • Acronym: UAF
  • Issues Count: 3
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Change <> relationship source to <> element

  • Key: UAF13-44
  • Status: open  
  • Source: MITRE ( Rae Anderson)
  • Summary:

    Currently, a <<SecurityControl>> is the source of the <<mitigates>>relationship to the target <<SecurityRisk>>. Further research shows that a security control (a type of requirement) in and of itself does not actually mitigate a <<SecurityRisk>>. Rather, the <<ResourceMitigation>> that<<satisfies>> the <<SecurityControl>> requirement is the actual UAFElement that <<mitigates>> the <<SecurityRisk>>.

  • Reported: UAF 1.2b1 — Sun, 29 May 2022 20:50 GMT
  • Updated: Tue, 31 May 2022 14:23 GMT

Enable a Requirement Relationship between AbstractReqirement and Capability

  • Key: UAF13-43
  • Status: open  
  • Source: MITRE ( 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
  • Updated: Tue, 31 May 2022 14:23 GMT

UAFML should not redefine SysML method attribute of the Viewpoint Stereotype.

  • Key: UAF13-40
  • Status: open  
  • Source: Ball aerospace ( John C Kha)
  • Summary:

    The method redefinition changes the type from SysML Behavior to SysML String, which limits the usefulness of the UAF viewpoint stereotype unnecessarily without providing any benefit. The description of the method attribute is, "The methods employed in the development of the Viewpoint." Redefining this to a string precludes defining executable methods that generate a view from the viewpoint, while leaving it as a behavior would not preclude defining the method as a string, since the body attribute of UML OpaqueBehavior is a string.

    Allowing the definition of the method as a behavior would also allow explicitly defining the types of inputs from the model needed to produce the view from the viewpoint as the types of input parameters to the behavior.

  • Reported: UAF 1.2b1 — Thu, 14 Apr 2022 16:32 GMT
  • Updated: Thu, 21 Apr 2022 16:10 GMT