-
Key: UAF-8
-
Status: closed
-
Source: Neil Kemp & Associates Inc ( Neil Kemp)
-
Summary:
I see capability is defined as “A high level specification of the enterprise's ability to execute a specified course of action.” Not sure I like it. If you said ‘A high level specification of something that enables the enterprise's ability to execute a specified course of action I would be a whole lot happier.
The DODAF definition of capability is “The ability to achieve a Desired Effect under specified (performance) standards and conditions through combinations of ways and means (activities and resources) to perform a set of activities.” I think this is a better definition, but again, the way its represented in their meta model it would be better described as “A thing that adds to The ability to achieve a Desired Effect under specified (performance) standards
The way both “official” definitions are worded I don’t think there is anything that is “countable” and therefore there is nothing that exists as an item to be captured in a structured model. I would argue that the chanes is needed to make the items countable and to then appear in a UML model and also question why competing definitions are necessary.
-
Reported: UAF 1.0b1 — Thu, 2 Feb 2017 20:24 GMT
-
Disposition: Resolved — UAF 1.0
-
Disposition Summary:
Capability Definition
modify Capability definition
-
Updated: Mon, 16 Oct 2017 15:16 GMT