Testing in a Joint Environment Roadmap - U.S. Army Operational ...
Testing in a Joint Environment Roadmap - U.S. Army Operational ...
Testing in a Joint Environment Roadmap - U.S. Army Operational ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
For Official Use Only<br />
<strong>Test<strong>in</strong>g</strong> <strong>in</strong> a Jo<strong>in</strong>t <strong>Environment</strong> <strong>Roadmap</strong><br />
2.3.2.1 OVERVIEW OF FUNCTIONAL CAPABILITY<br />
A persistent, repeatable, operationally realistic network<strong>in</strong>g <strong>in</strong>frastructure will provide the<br />
ability to create the complex and realistic test environments needed to test <strong>in</strong> a jo<strong>in</strong>t environment.<br />
Figure 6 illustrates the common jo<strong>in</strong>t mission <strong>in</strong>frastructure. The top layer symbolizes the<br />
library of available virtual and constructive representations that, l<strong>in</strong>ked together, provide for<br />
generation of the required mission environments. Each additional layer represents a specific<br />
mission environment. Work<strong>in</strong>g from a persistent <strong>in</strong>frastructure of connectivity, common data<br />
exchange middleware, data description standards, common archiv<strong>in</strong>g, configuration and<br />
execution tools, test planners will be able to select from the library of virtual and constructive<br />
resources to supplement available live systems. System availability and required fidelity will<br />
determ<strong>in</strong>e the appropriate comb<strong>in</strong>ation of LVC representation. Use of this <strong>in</strong>frastructure will<br />
permit rapid, facile and cost-efficient creation and execution of tests over a full range of required<br />
test environments.<br />
Lab<br />
Ocean<br />
Developer<br />
Product<br />
Model<br />
HWIL<br />
Lab<br />
Ocean<br />
Developer<br />
Product<br />
Node<br />
Trng. Range<br />
Live Sim.<br />
HWIL<br />
Lab Terra<strong>in</strong><br />
Test <strong>Environment</strong><br />
#1<br />
T&E Range<br />
Live Sim.<br />
Developer<br />
Product<br />
Node<br />
T&E Range<br />
Live Sim.<br />
Trng. Range<br />
Live Sim.<br />
Each stand-alone site is a<br />
node <strong>in</strong> the Jo<strong>in</strong>t Mission<br />
Infrastructure with<br />
Connectivity, Middleware,<br />
Standards, and Tools...<br />
... enabl<strong>in</strong>g a logical,<br />
common, Range-like<br />
Jo<strong>in</strong>t Task Force<br />
<strong>Operational</strong><br />
<strong>Environment</strong> or<br />
Test <strong>Environment</strong><br />
configured for the<br />
current evaluation ...<br />
Developer<br />
Product<br />
Model<br />
Lab<br />
Terra<strong>in</strong><br />
Test <strong>Environment</strong><br />
#N<br />
HWIL<br />
T&E Range<br />
Live Sim.<br />
... and reconfigurable<br />
and reusable with<br />
other sites for other<br />
tests.<br />
Figure 6. Overview of a Jo<strong>in</strong>t Mission Infrastructure<br />
Each jo<strong>in</strong>t mission environment will resemble a live, real world, s<strong>in</strong>gle-site range, and will be<br />
configured and managed <strong>in</strong> a very similar manner. However, this “virtual range” will generally<br />
be distributed both geographically and organizationally to access the resources needed for test<strong>in</strong>g<br />
<strong>in</strong> the jo<strong>in</strong>t environment, as required by relevant jo<strong>in</strong>t missions, operational architectures, and<br />
desired system attributes from the CDD and CPD. The components l<strong>in</strong>ked via a common<br />
technical framework for a given test event will consist of resources specific to the particular test.<br />
19<br />
For Official Use Only