Environment_Test_Harness_Requirements_20150731_final.pdf

FOR OFFICIAL USE ONLY

(U) Environment Test Harness (ETH)

Requirements

31 July 2015

DISTRIBUTION STATEMENT C: Distribution authorized to the Department of Defense and U.S.

DoD contractors only; Administrative or Operational Use; 31 July 2015. Other requests shall be referred to MDA/ESP, Core Truth Models Lead

Environment Test Harness (ETH) Requirements

Objective: Provide the capability to conduct comparative analysis between the outputs of environment model(s) (referred to as virtual data) and physical measurement data.

Compare Virtual Model Data and/or Physical Measured Data

1.0 Model and/or Data Input Requirements

1.1 The Environment Test Harness (ETH) shall have the capability to input physical measurement data and environment models.

1.1.1 The ETH shall have the capability to input multiple environment models that are capable of being built using a modern* C, C++, or Java compiler and that will run on a modern version of Windows or Linux. *For the purposes of these requirements, modern is defined as non-end-of-life, non-deprecated software.

Example: dBTools Gravity Example: CEM Gravity

Environment Model (Experimental)

Environment Model (Control)

Environment Model (Experimental) Environment Model

(Experimental) Environment Model (Experimental)

Percentage of Simulation Data Points Outside Error Bounds

Harmonic Set Telemetry BET Smoothed BET

X Y Z X Y Z X Y Z

0,0

2,0

2,2

3,0

4,0

4,4

8,8 17.10 79.27 0.73

16,16

36,36

Measured Physical

Data

1.1.2 The ETH shall have the capability to input individual subroutines (functions or methods) from an environment model provided that the model has been sufficiently decomposed (if necessary) to allow access to those subroutines.

1.1.3 The ETH shall have the capability to input physical measurement data delivered in a defined format.

2.0 Model Execution Requirements

2.1 The ETH shall have the ability to modify variable settings (e.g., corresponding to environment model parameters) prior to executing a model run.

2.1.1 The ETH shall provide the capability to save a group of variable settings to a file.

2.1.2 The ETH shall provide the capability to reconfigure variable settings for each run.

2.1.3 The ETH shall have the capability to execute a single independent model run.

2.1.4 The ETH shall have the capability to execute batches of model runs using a single group of variable settings.

2.1.5 Model execution shall incur no additional processing overhead. Overhead shall only result from sending and receiving input/output information.

3.0 Comparative Plot Requirements

3.1 The ETH shall have the capability to plot virtual outputs from disparate models, single models, and/or physical measurement data onto the same graphical plot for comparative purposes.

3.1.1 Disparate data sources shall be clearly distinguishable on plots by color and symbology.

3.1.2 Visual representations of data shall be scalable by user, and shall provide sufficient granularity to view items of interest when scaled.

3.1.3 User shall be able to visually zoom in on areas of interest within the plots.

3.2 The ETH shall produce output tables that show comparisons for virtual model and/or measured physical data by some common increments (e.g., time, range, etc.) that is advisable for the particular data or model source used in the analysis.

3.2.1 Disparate data sources shall be clearly distinguishable on data tables.

3.2.2 Data tables shall be exportable into data formats usable by other software (i.e., Excel or MATLAB) for further data manipulation.

4.0 Classification Level Requirements

4.1 The ETH shall operate primarily at the UNCLASSIFIED level.

4.2 ETH shall provide data independence from software such that an ETH instance can support both UNCLASSIFIED and CLASSIFIED processing requirements.

5.0 Hardware Requirements

5.1 ETH software shall not require any specialty hardware.

5.2 ETH software shall run on a scientific workstation class desktop computer with capabilities equivalent or superior to those indicated on the Army Computer Hardware Enterprise Software and Solutions (CHESS) web site at URL https://chess.army.mil/ConsolidatedBuy/Default/ListProduct?categoryId=4

5.3 ETH shall be scalable to multi-core computing hardware architectures.

5.4 ETH shall have the capability to archive and retrieve data from data archives. Data shall be in defined formats.

6.0 Logical Architecture