Concept development and experimentation: Difference between revisions

Revision as of 20:38, 17 September 2007

Revision as of 20:02, 1 December 2007

Line 9:

The potential impacts on interoperability and increased capabilities by emerging concepts must be captured by some process and exploited.

Concept development gives broad and sometimes ill-defined ideas a chance to be

Line 36 ⟶ 35:

Once validated and accepted, concepts are incorporated into military organizations – for example,

through doctrine and capability development processes.

== Literature ==

Line 45 ⟶ 43:

* Guide for Understanding and Implementing Defense Experimentation, The Technical Cooperation Program, 2005, ([http://www.dtic.mil/ttcp/])

== External links ==

== Weblinks ==

* Concept Development and Experimentation at [[Allied Command Transformation|NATO Allied Command Transformation]], ([http://www.act.nato.int/organization/transformation/jeeacdeindex.htm])

Line 53 ⟶ 50:

[[Category:United States Department of Defense]]

[[de:Concept Development & Experimentation]]