View NAF:NCV-2 Capability Taxonomy Subview
Overview
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 http://www.nhqc3s.nato.int/Browser.asp?Target=_docs/NAF_v3_1 .
See NAF Release History.
Purpose
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.
Definition
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 5.2.3.2
The data in an NCV-2 can include:
- Capability
- Capability Specialization (relationship between capabilities)
- Capability Dependencies
- Enterprise Phase
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:
- MODAF::AV-1 equates to NAF::NAV-1
- MODAF::StV-1 equates to NAF::NCV-1
- MODAF::StV-2 equates to NAF::NCV-2
- MODAF::StV-6 equates to NAF::NCV-6
- MODAF::SV-1 equates to NAF::NSV-1
Presentation
Configuration History
- 3.1 removed Enterprise Phase and added Capability Dependencies and Measurable Property to data objects
Comments
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.
References
- Section 4.4.2 (page 191 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
- Section 5.2.3.2 (page 369 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
- Section 5.2.3.2 of Chapter 5 AC/322(SC/1-WG/1)N(2009)0005-ADD2 NATO Architecture Framework Version 3.1
- The MODAF Strategic Viewpoint. 26th April 2010. http://www.mod.uk/DefenceInternet/AboutDefence/CorporatePublications/InformationManagement/MODAF/TheStrategicViewpointstv.htm
Other Frameworks
See also:
- DODAF::CapV-1 Capability Taxonomy Subview
- DODAF::CV-2 Capability Taxonomy Model
- MODAF::StV-2 Capability Taxonomy View
- TRAK::EVp-02 Capability Hierarchy Viewpoint
Category:Framework -> View
Category:NAF -> Subview
Category:Capability
Category:Strategic
Clip to Evernote
Bookmark this on Delicious
