View NAF:NCV-2 Capability Taxonomy Subview



The NCV-2 Capability Taxonomy subview is part of the NATO Capability View and one of the 49 NATO Architecture Framework subviews*.

Version & Date

Version 3.1

* =  changed at 3.1

+ =  new at 3.1

The change history is derived from the definition of each NATO Architecture view within section 5.2.3 NATO Capability View (NCV) in AC/322(SC/1-WG/1)N(2009)0005-ADD2.  NATO Architecture Framework Version 3.1 document from .

See NAF Release History.


From the NATO Architecture Framework v3, CHAPTER 4, Section 4.4.2

The Capability Taxonomy (NCV-2) subview provides a structured list of capabilities and sub-capabilities that are required within a capability area during a certain timeframe

Covered by NATO release conditions.


The NCV-2 subview is used to capture and organise the NATO capabilities required for the vision established in the Capability Vision subview (NCV-1) into a structured list.

The structured list provided by the NCV-2 subview will be a comprehensive list of the capabilities that need to be delivered during a particular timeframe. The list is structured hierarchically, and each capability is, where necessary, subdivided into sub capabilities and/or functions, in order to provide clarity and the appropriate level of granularity required by subsequent processes in the capability management process. All terms used in the NCV-2 will be expressed only in non-implementation specific based terms - i.e. these terms are military capability based, not equipment focused. An NCV-2 product will be developed for each specified timeframe.

Covered by NATO release conditions.

Data Objects*

From the NATO Architecture Framework v3.1, CHAPTER 5, Section

The data in an NCV-2 can include:

Covered by NATO release conditions.

From The MODAF Strategic Viewpoint p7:


Full size:File:MODAFStV-2CapabilityTaxonomy simplifiedMM.gif

Subject to Crown Copyright

Note - this shows that Environment is a legitimate data object.

This diagram is taken from MODAF 1.2.004 MODAF::StV-2 Capability Taxonomy View as it is identical to that in NAF 3.1 with the following substitutions for view/subview number:


Configuration History


Function is always associated with a means whether technology or similar - it is part of the solution and hence function shouldn’t be mixed with capability which is implementation free.


Other Frameworks

See also:



Category:Framework -> View
Category:NAF -> Subview



© 2010 Eclectica Systems Ltd.