Testing in a Joint Environment Roadmap - U.S. Army Operational ...

More documents

Recommendations

Info

For Official Use Only Testing in a Joint Environment Roadmap Define required elements of the technical infrastructure and identify key tasks and timelines for achievement of this architecture. Establish a schedule effecting phased stand-up of the needed capability. Identify any milestone decision points. Function as implementation organization until responsibility is transferred to the owning organizations. Establish working liaisons with communities of interest, such as a possible OPFOR IPT with JFCOM, DIA, etc. Address unique requirements for testing in the joint environment that includes coalition forces, or T&E in support of foreign military sales. D-2 For Official Use Only Appendix D
For Official Use Only Testing in a Joint Environment Roadmap Appendix E – Glossary – Definitions and Acronyms E.1 Definitions − "Joint Mission Environment" – The operational context in which the capability being developed must perform. − "Joint Mission Infrastructure" – Collective term for the hardware/software – the combination of representations of friendly and enemy forces and the geophysical environment, as well as the supporting infrastructure, required to generate the joint mission environment necessary for capability development and T&E. − "Testing" and Test and Evaluation (T&E) – The term "testing" (or test) is used for simplicity/brevity in some cases. Throughout the context of this report, the term "testing", where applied, is synonymous with T&E. − "Testing in a Joint Environment" – A more accurate description of the capability this roadmap will address than the title of the SPG paragraph, "Joint Testing in Force Transformation". The report avoids the term "joint testing" because this terms connotes testing that requires participation of more than one Service, not always true, and is easily confused with the Joint Test and Evaluation (JT&E) program. − “Evolutionary Acquisition (EA)”– The preferred approach that fields an initial operationally useful and supportable capability in as short a time as possible with the explicit intent of delivering the ultimate capability in the future through one or more increments. There are two approaches to evolutionary acquisition: 1) incremental, and 2) spiral. With the incremental approach, a desired capability and end state requirements are known at program initiation, and these requirements are met over time by the development and fielding of increments as technology maturity permits. With the spiral approach, a desired capability has been identified, but end state requirements are not entirely known at program initiation. Each increment of a spiral program provides the user with the best available capability at that time and then future requirements are developed and refined over time based on demonstration, risk management, and continuous user feedback. Spiral development is the preferred approach to evolutionary acquisition. E.2 Acronyms Acronym ACASS Long Title Advanced Close Air Support System E-1 For Official Use Only Appendix E
Page 1 and 2:
For Official Use Only Testing in a
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30: For Official Use Only Testing in a
Page 79: For Official Use Only Testing in a
Page 89 and 90: For Official Use Only Intentionally
show all

Testing in a Joint Environment Roadmap - U.S. Army Operational ...

Create successful ePaper yourself

Delete template?

Save as template?