UAF 1.2 RTF Avatar
  1. OMG Issue

UAF12 — Capability specialisations are needed

  • Key: UAF12-17
  • Status: closed  
  • Source: Dassault Systemes ( Dr. Aurelijus Morkevicius)
  • Summary:

    Currently Capability in UAF is representing business level capability, however; there are no corresponding elements at the solution domain. It is common practice in engineering to use a concept of Feature as a technical capability provided by a system or a set of systems. Having feature concept in UAF has beed already discussed in UAF 1.1 RTF and agreed between group members. It is something that has been requested by Boeing and now is also requested by Airbus. Another Airbus request is to make Competence a type of feature provided by organisational resources. This would fit Competence concept into the right place in hierarchy as now it is kind of left alone.

  • Reported: UAF 1.1 — Thu, 28 Nov 2019 09:34 GMT
  • Disposition: Resolved — UAF 1.2
  • Disposition Summary:

    Capability Kind introduced to support the need

    CapabilityKind enumerated list is added to classify the capability as e.g. operational, resource, strategic, personnel, service, security, or other. There are no specific constraints added when which of the kinds is supposed to be used. It depends on the methodology used within the organization. The generic use of Capability kinds is addressed in the EA guide document. By the default CapabilityKind is set to undefined.

  • Updated: Thu, 31 Mar 2022 19:31 GMT
  • Attachments: