# Quality Assurance/Quality Control

The work performed for the Savannah River Site Dose Reconstruction
Project (SRS DRP) was done in accordance with the following Quality
Assurance Procedures:

-   QAP 1 -- Work Process Controls

-   QAP 2 -- QA Training Procedure

-   QAP 3 -- Work Product Review

-   QAP 4 -- Records Management

-   QAP 5 -- Assessment

-   QAP 6 -- Information Control

Additionally, other tiered procedures were used including:

-   QAP 4.2 - Production of Electronic Records from Hardcopy Documents

-   QAP 4.3 - Quality Assurance Review of Scanned Documents

Prior to initiation of any work activities on the project, a Work Plan
was developed by the Project Director in accordance with QAP 1. This
Work Plan detailed project description, project schedule, project
budget, project personnel, applicable technical standards and
regulations, training requirements, subcontractor QA requirements, and
technical review requirements. This plan was maintained electronically
and was available to all project personnel.

All data used in this project was quality checked. Quality checks
include verifying that original data from source documents were properly
copied, all calculations and manipulations done to original data were
performed correctly, and that revised data was entered into computer
files correctly. All quality checks were documented on the form
available in QAP 3.0. The forms, along with a copy of the data that was
checked and any pertinent formulas that were used for calculations, were
provided to the Project QA Manager. The forms were sequentially numbered
and information from the forms was input into the QA Tracking Database.
The forms and associated data are maintained in the QA project files.

## Quality Control (QC) Activities

There were several activities that were performed in support of the
SRSDRP that required extensive quality control reviews to assure the
accuracy and defensibility of the work product. These activities were
source term development; transfer, exposure, usage, and transportation
factor development, software development, and output from the computer
code. The QC activities associated with each of these work activities is
described below:

### Source Term Development

The process used in developing the air and liquid source terms is
presented in Figure P-1.

![](media/image1.wmf){width="6.497916666666667in"
height="7.751388888888889in"}

Figure P‑1 Source Term Development Process

The development of source term information required two quality control
processes; review of source term data to determine if the data was
traceable back to an original source document after any manipulations or
calculations, and a review of the inputted data files to determine if
any errors arose during the data input process.

Original source term data for air and liquid releases was derived from
SRS Environmental Reports and from the Phase II report as detailed in
[Chapters 5](../Chapter_05_Ready%20for%20CDC%20031405.doc) and
[7](../Chapter_07_Ready%20for%20CDC%20031405.doc). For air releases,
these data were adjusted to account for modifications to the original
data used in the Phase II report. The data that resulted from the
adjustment process was quality checked and the reviews documented. Any
errors found during the quality review were noted and the data returned
to the author(s) for correction. Also, in order for the computer code to
proper read the data input files, the input files that to be transformed
into a specific file structure. This process did not involve any data
calculations but entailed transferring data within an Excel spreadsheet.
The data spreadsheets that resulted from this transformation process
were quality checked and the review documented. Any errors found during
the quality review were noted and the data returned to the author(s) for
correction. For liquid releases, the source term data for radionuclide
concentrations in the Savannah River was based on direct releases to
onsite streams and direct releases to seepage and containment basins.

Data that was input into files for processing by the pre-processor were
quality checked to ensure that no errors occurred during the input
activity. All input files were quality checked and any errors or
inconsistent data were returned to the author(s) for correction.
Documentation of the source term data quality checks is maintained in
the QA project files.

### Transfer, Exposure, Usage, and Transportation Variable Quality Reviews

Approximately 109 radionuclide transfer, exposure, usage, and
transportation variables had to be defined prior to running the computer
model. The majority of the variables used in the modeling for this
project consist of default values incorporated into the GENII code.
Transfer variables not available in GENII were derived from *Handbook of
Parameter Values for the Prediction of Radionuclide Transfer in
Temperate Environments, Technical Reports Series No.364, International
Atomic Energy Agency, Vienna, Austria, 1994* and numerous other
documents that are referenced in the applicable Chapters.

The factors that were input into the computer files were quality checked
against the original source documents. Any errors found during the
quality review were noted and the data returned to the author(s) for
correction.

### Software Development

Two major software efforts were completed for the SRS DRP. The first was
the development, testing and implementation of the pre-processor code
and the second was the development, testing, and implementation of the
post-processor code. A description of how these codes functioned is
included in [Appendix G](../Appendix_G_ready%20for%20CDC%20031405.doc).
The quality assurance activities for the development and testing of
these two codes included:

-   Preparation of the software selection decision document

-   Preparation of software requirements documents for the pre- and
    post-processor,

-   Detailed design requirements documents for the pre- and
    post-processor, and

-   Preparation and execution of the Quality Assurance Application Test
    Plan for the Pre- and Post-Processors to GENII-V2.

The Software Selection Document (SSD) details the basis for selecting
the computational code to be used for the dose calculation. One of the
selection criteria was the capability to calculate dose and risks for
individuals. Additionally, the code needed to have the versatility to
accept a pre- and post-processor in order to perform all the required
calculations. The SSD was reviewed by The GENII Version 2 code was
selected based on these requirements.

Once the modeling software was selected, the requirements for the pre-
and post-processors had to be developed so that the software designers
would have a design structure. Software Requirements Documents for the
Pre- and Post-processors were developed and quality reviewed to ensure
that all the elements needed to perform the dose calculation for the SRS
were adequately addressed. Comments from the technical reviewers were
provided back to the authors of the requirements documents for responses
and revising the documents if necessary.

When the requirements for the pre- and post-processors were considered
adequate for the all the planned dose and risk calculations, detailed
design documents were developed to guide the software designers. These
detailed design documents were also reviewed to ensure that they
addressed all the elements required for the calculations. Comments from
the technical reviewers were provided back to the authors of the
requirements documents for responses and revising the documents if
necessary.

After the software design for the pre- and post-processors was
completed, a Quality Assurance (QA) Application plan was developed. The
purpose of the QA Application Plan was to assess the accuracy and
completeness of the pre- and post-processor applications. The projected
boundaries of the planned tests included limiting test data to a base
case of input values with discrete scenario modifications that contained
minimal attribute changes. These modifications satisfied the data
permutations necessary to test the functional capabilities of the
software design without creating unmanageable volumes of test data. The
Quality Assurance Applications Test Plan is included in Attachment A to
this Appendix.

After performing the testing as required by the QA Application Test
Plan, all identified errors or faults detected in the pre- and
port-processor software were documented and fully addressed. This
documentation is maintained in the QA project files.

### GENII V2 Output

After the pre- and post-processors were verified as functioning properly
with the GENII V2 model, the actual dose and risk computer calculations
were performed. A copy of each of the thousands of computer code runs
that were done in support of the SRS DRP was electronically stored as a
QA record. These files were reviewed by project staff for any obvious
anomalies in the output data. When an anomaly was suspected, the
computer code run was performed repeated and corrective actions were
determined as a result of the second run. The QA records for the
computer code runs are maintained in the QA project files.

### Document Scanning

A part of the SRS DRP was to scan over 140 boxes of documents, reports,
and pages of information. The goal of this process is to accurately
duplicate the information into an electronic format so that the images
could be uploaded to the appropriate CDC website and made available to
the public. QAP 4.2 was followed to ensure that all documents were
visually inspected prior to the scanning process to assess the physical
integrity of the documents, if the document pages were in sequential
order, and if the document identification number was on the first page
of the document. The procedures also details activities for scanning
preparation and operations to ensure that the scanned documents are
properly identified, oriented on the image, and that the size of the
document doesn't exceed the capacity of the scanner.

QAP 4.3 was followed to ensure that the scanning process was performed
correctly, that the scan image is readable, properly labeled and
identified, and retrievable from the electronic storage media, i.e.
compact disc.

An assessment by a person independent of the scanning process was
performed to determine if any errors or problems existed with the
scanned images. Assessment of every page of every document contained in
over 140 boxes was not feasible but one document from every two boxes
was reviewed. No errors or problems were detected during the assessment.
The assessment results were documented and maintained in the QA project
files.

> **ATTACHMENT A**
>
> **Quality Assurance Application Test Plan for the Pre- and
> Post-Processors to GENII-V2 For the Generation of the Dose
> Reconstruction at the Savannah River Plant**

**Date: September 22, 2003**

**Revision 4**

**CONTENTS**

[1. PURPOSE 3](#__RefHeading___Toc88362776)

[2. BACKGROUND 3](#__RefHeading___Toc88362777)

[3. SCOPE 3](#__RefHeading___Toc88362778)

[4. LIMITATIONS AND TRACEABILITY 3](#__RefHeading___Toc88362779)

[4.1 Limitations 3](#__RefHeading___Toc88362780)

[4.1.1 Pre-Processor 3](#__RefHeading___Toc88362781)

[4.1.2 Post-Processor 4](#__RefHeading___Toc88362782)

[4.2 Traceability 5](#__RefHeading___Toc88362783)

[5. TEST PLANS 7](#__RefHeading___Toc88362784)

[5.1 Test Levels 7](#__RefHeading___Toc88362785)

[5.2 User Acceptance Test 7](#__RefHeading___Toc88362786)

[5.3 Test Methods and Evaluation 7](#__RefHeading___Toc88362787)

[5.3.1 Pre-Processor 7](#__RefHeading___Toc88362788)

[5.3.2 Post-Processor 8](#__RefHeading___Toc88362789)

[6. TEST DESCRIPTION 9](#__RefHeading___Toc88362790)

[6.1 Pre-Processor 9](#__RefHeading___Toc88362791)

[6.1.1 Run 0.000: Baseline Facility 10](#__RefHeading___Toc88362792)

[6.1.2 Run 1.000-.100: Point Estimate & Uncertainty
10](#__RefHeading___Toc88362793)

[6.1.3 Run 2.000: Alternate Facility 2 12](#__RefHeading___Toc88362794)

[6.1.4 Run 3.000: Alternate Facility 3 13](#__RefHeading___Toc88362795)

[6.1.5 Run 4.000: Alternate Year 2 14](#__RefHeading___Toc88362796)

[6.1.6 Run 5.000: Error Messages 15](#__RefHeading___Toc88362797)

[6.2 Post-Processor 16](#__RefHeading___Toc88362798)

[6.2.1 Setup Run 1.000: Point Estimate Multi-Year
17](#__RefHeading___Toc88362799)

[6.2.2 Setup Run 2.000: Point Estimate Single-Year
17](#__RefHeading___Toc88362800)

[6.2.3 Setup Run 3.000: Point Estimate Multi-Year Gender-Assignment
18](#__RefHeading___Toc88362801)

[6.2.4 Setup Run 4.000: Liquid Pathways and Decay Products
18](#__RefHeading___Toc88362802)

[6.2.5 Setup Run 5.000: Facility Identification
19](#__RefHeading___Toc88362803)

[6.2.6 Run 1.000: Point Estimate Multi-Year
19](#__RefHeading___Toc88362804)

[6.2.7 Run 2.000: Point Estimate Single-Year
21](#__RefHeading___Toc88362805)

[6.2.8 Run 3.000: Point Estimate Multi-Year Gender-Assignment
22](#__RefHeading___Toc88362806)

[6.2.9 Run 4.000: Liquid Pathways and Decay Products
23](#__RefHeading___Toc88362807)

[6.2.10 Run 5.000: Facility Identification
24](#__RefHeading___Toc88362808)

1.  []{#__RefHeading___Toc88362776 .anchor}PURPOSE

The purpose of this QA test plan is to assess the accuracy and
completeness of the Pre- and Post-Processor applications that have been
developed to utilize the GENII-V2 dose calculation software. The overall
goal of systems integrated testing is to confirm that the working
applications, or groups of components, can be fully integrated and
satisfy functional and technical requirements.

2.  []{#__RefHeading___Toc88362777 .anchor}BACKGROUND

Two applications (a Pre-Processor and a Post-Processor) have been
developed to help automate the dosage analysis process using the
GENII-V2 dose calculation software as a primary component. The
pre-processor has been designed take a standardized GENII-V2 input file
(GID file) and make changes in the standardized GID to account for
varying facilities with releases by isotope, year of operation and
receptor combination. In addition, for each facility and year and
receptor combination, there could be up to 101 GID files generated as
required by the uncertainty analysis (one for the point estimate data
and 100 for the uncertainty data). The post-processor will use a
two-step process to create the input files for the
uncertainty/sensitivity analysis software. The post-processor will first
read a set of GENII-V2 output files (HIF files) for a given facility and
prepare a set of dose/risk results for the receptors designated in the
scenario requirements for that facility. It will then combine the
facility based results to form results for the entire site once all the
facility results are available.

3.  []{#__RefHeading___Toc88362778 .anchor}SCOPE

The projected boundaries of the planned tests include limiting test data
to a base case of input values with discrete scenario modifications that
contain minimal attribute changes. These modifications will satisfy the
data permutations necessary to test the functional capabilities of the
software design without creating unmanageable volumes of test output.

While actual input data could have variations that yield potentially
millions of output data points from the Pre-Processor alone, it is
obviously unfeasible to test every possible permutation within a
reasonable time-frame and completely unnecessary based on the objectives
of the testing. Given that initial input data varies primarily on
facility, year and uncertainty, these are the major areas that will be
used to group variations in the test scenario data.

4.  []{#__RefHeading___Toc88362779 .anchor}LIMITATIONS AND TRACEABILITY

    1.  []{#__RefHeading___Toc88362780 .anchor}Limitations

        1.  []{#__RefHeading___Toc88362781 .anchor}Pre-Processor

General limitations for the Pre-Processor will be that Media, Isotopes
and Exposure Locations will remain constant while data test scenarios
will be grouped and generated as a function of facility, year and
uncertainty combinations. More specific limitations to the Pre-Processor
are as follows:

1.  Media

Media will be limited to atmospheric, while liquid and soil will not be
addressed by this QA test since there are still outstanding requirement
questions surrounding those two media as of the writing of this
document.

2.  Isotopes

Since isotopes are limited by release facility, the subset of isotopes
corresponding to selected facility data will be tracked for correct
values while the remaining isotopes not available in the facility data
will be checked to confirm zero values.

3.  Exposure Locations

All exposure location data available within the subset of the standard
GID template containing the first 10 locations will be tracked to
provide confirmation of distance values both near and far from chosen
Facilities.

4.  Facilities

Three facilities (one centralized for control and two in opposing
directions) will be used to capture and confirm changes in distance and
direction. A fourth facility will be used to distinguish filenames for
error trapping. The same source term data will be used for all
facilities to maintain a control constant.

5.  Years

Two specific years will be used to capture changes in source term
release amounts for a given facility over time.

6.  Uncertainty

A total of three uncertainty runs (one point estimate baseline and two
uncertainty sets) will be tracked to confirm uncertainty values, while
all 101 runs will actually need to be executed to confirm the
uncertainty execution process.

7.  Source Term Uncertainty

All facility source term data will be checked for uncertainty factor
calculations and compared to the point estimate baseline values for
accuracy.

8.  Parameter Uncertainty

A discrete subset of parameter variables will be checked for value
replacement and will include isotope independent variables, isotope
dependent variables and exposure location dependent variables for the
selected uncertainty runs.

2.  []{#__RefHeading___Toc88362782 .anchor}Post-Processor

All of the limitations for the Pre-Processor input data will also apply
to the Post-Processor with the following exceptions:

1.  Facilities

Only one facility will be used since risk and dose output files are
facility specific.

2.  Years

Five years will be used to allow risk and dose factor differences to be
seen for receptors across all factor groupings based on age.

Limitations specific only to the Post-Processor are as follows:

3.  Location

All seven locations will be selected crossing different age groups to
account for all receptor age group combinations.

4.  Receptor

Ten receptors will be selected, one for each combination of age group.

5.  Pathway

All pathways for all available isotopes will be reviewed for one
particular receptor during one particular year.

6.  Risk by Organ

All risk by organs will be accounted for one receptor and pathway.

7.  Dose by Organ

All dose organs will be accounted for one receptor and pathway.

8.  Total Risk

Total risk will be reviewed in all comparison scenarios.

9.  Total Dose

Total dose will be reviewed in all comparison scenarios.

2.  []{#__RefHeading___Toc88362783 .anchor}Traceability

Traceability of test scenarios to individual requirements will be
maintained through a functional requirements traceability matrix. The
requirements will be obtained directly from the detailed design
documentation. Each requirement will be numbered based on the outline
paragraph number within the detailed design. If paragraphs contain more
than one potential requirement a sub paragraph number will be assigned.
There will be separate spreadsheet tabs within the RTM for the
Pre-Processor and for the Post-Processor as well as associated Failed
History. The Requirements Traceability Matrix spreadsheet document will
contain the following columns:

  -----------------------------------------------------------------------
  Column Name           Column Description
  --------------------- -------------------------------------------------
  Paragraph \#          Outline number of the requirement from the
                        detailed design.

  Sub Paragraph \#      A more detailed number indicating that the
                        paragraph contains more than one discrete
                        requirement and must be broken down into
                        individual test scenarios.

  Requirement           Actual requirement text from the detailed design.
  Description           

  Requirement Section   Outline title of the requirement section.

  Requirement Sub       Outline titles of the requirement sub sections.
  Section(s) \[x3\]     

  Test Run \#           Number of the execution run for the given test
                        input data set.

  Test Scenario         Title of the scenario that distinguishes the
                        various test cases within the given Test Run.

  Test Sub Scenario(s)  A more detailed title indicating that the
  \[x2\]                scenario must be broken down into more discrete
                        sub scenarios.

  Verification          Flag indicating results of the comparison between
                        actual output data and expected values (passed,
                        failed, n/a).

  File Name             Name of the file containing the output data being
                        compared if applicable.

  Row \#                Number of the row within the output file
                        containing the data being compared.

  GID Row Values        The following columns are only on the
  (Pre-Processor only)  Pre-Processor RTM spreadsheet and apply to the
                        GID input file.

  Field Name            Name of the field in the row within the GID file
                        being compared.

  1, 2, 3, 4, 5, 6, 7   Indices for the given row within the GID file
                        having various meanings (see detailed design).

  Text 1, Text 2        Unit of measure used for the row within the GID
                        file.

  Dose and Risk Row     The following columns are only on the
  Values                Post-Processor RTM spreadsheet and apply to the
  (Post-Processor only) Dose and Risk results TXT file.

  Organ Name            Name of the Organ column within the Dose and Risk
                        file being compared.

  Location              Receptor Location for the row within the Dose and
                        Risk file being compared.

  Receptor              Receptor Name for the row within the Dose and
                        Risk file being compared.

  CurrYear              Current Year (1954-1992) for the row within the
                        Dose and Risk file being compared.

  RunNum                Uncertainty Run Number (000-100) for the row
                        within the Dose and Risk file being compared.

  Isotope               Isotope value for the row within the Dose and
                        Risk file being compared.

  Pathway               Pathway value for the row within the Dose and
                        Risk file being compared.

  Route                 Route value for the row within the Dose and Risk
                        file being compared.

  Comparison Values     The following columns are on both Pre- and
  (Pre and Post         Post-Processor RTM spreadsheets.
  Processor)            

  Actual                Output value of the test scenario to be compared
                        with expected value (corresponds to Field Name
                        for Pre-Processor and Organ Name for
                        Post-Processor).

  Expected              Expected value of the test scenario to be
                        compared with actual value.

  Tolerance %           Percent difference between actual and expected
                        values (for value comparison test cases where
                        null or zero constitutes a passed test, very
                        small values indicate differences due to
                        acceptable rounding or truncation and large
                        values or "#DIV/0!" errors indicate a failed
                        test).

  Notes                 Additional detail that provides indication of
                        duplicate requirements (e.g. "duplicate of
                        n.n.n"), indication of general requirements
                        confirmed by more specific requirements (e.g.
                        "see n.n.n through n.n.n."), exact text within a
                        message or QA file, or why a test scenario passed
                        or failed.
  -----------------------------------------------------------------------

5.  []{#__RefHeading___Toc88362784 .anchor}TEST PLANS

    1.  []{#__RefHeading___Toc88362785 .anchor}Test Levels

        1.  Subsystem Integration Test

The Pre-Processor and Post-Processor will be tested as individual
subsystems. Execution of each application is manually driven and
requires human intervention to select the setup criteria at each stage.
There will be no automated end-to-end integration test. The
Pre-Processor will be used to generate upstream test files that will
process through GENII-V2 prior to being used as input for the
Post-Processor testing.

2.  []{#__RefHeading___Toc88362786 .anchor}User Acceptance Test

These applications are designed to be run only once for all data, not as
an ongoing end-user-driven process. The production-level execution will
be performed by the QA team. Since there is no end-user involvement, no
user acceptance test will be necessary.

3.  []{#__RefHeading___Toc88362787 .anchor}Test Methods and Evaluation

Testing will be accomplished through multiple execution runs of the
application using a variety of input data sets. The requirements
traceability matrix will be the solitary driver for all test scenarios.
Test data sets will be created for each scenario to meet the needs of
the requirements as defined in the detailed design documentation.

1.  []{#__RefHeading___Toc88362788 .anchor}Pre-Processor

    1.  Input Data Creation

The test data for the Pre-Processor will be set up to address specific
test scenarios and will be contained in a combination of standard GID
templates for given exposure location sets and facility specific source
term data files. Reference data will be contained in pre-defined isotope
description files, dispersion factor files, exposure description files,
facility description files, parameter uncertainty files and source term
uncertainty files. The appropriate combination of input files will be
set up for each execution run as they pertain to the test scenarios
within that particular run. Many input reference files will remain
constant across test scenarios and will be re-used by multiple test runs
as necessary. Any variation of input files will be documented and kept
for reference.

2.  Expected Results Calculation

Expected results for each test scenario will be determined through both
manual calculations and other tool-assisted methods. In the most basic
scenario, the application obtains data directly from a source term file
for a given media and facility, then multiplies by a unit conversion
factor and places the data in a specific row within the GID output file
based on corresponding variable names and row indices for a given
isotope or exposure location. These calculations are relatively simple,
self-explanatory and will not require additional explanation beyond
referencing the detailed design requirement. Distance calculations are
slightly more complex and a separate tool will be developed using
Microsoft Excel to determine values for expected results. Since user
interface requirements typically affect all test runs and only occur
during execution setup, they have no particular test scenarios and no
specific expected results to compare. Visual verification will suffice
to confirm application functionality for most user interface
requirements.

3.  Error Messages Confirmation

Error message functionality will be confirmed by setting up various
error scenarios within the input files and capturing output text within
message files. Since the same message output filename may be used for
several error scenarios, the message output files will be re-named after
each error run to include the corresponding scenario for easy
traceability.

4.  Output Data Comparison Analysis

Once each test execution run has completed successfully, the output
files for each run will be captured and analyzed using a text editor or
Microsoft Excel to assist in the analysis.

For each test scenario within the corresponding GID output file, the
specific field name and index values will be matched to find the actual
quantity, distance or setup values. The row number will be noted and the
entire row of data will be captured and the actual values will be placed
in the traceability matrix for comparison with the expected values.

If the actual value matches expected results within acceptable
tolerances, the scenario is marked as passed in the verification column.
If the value does not match the expected results, the scenario is marked
as failed in the verification column and placed in the failed history.
Failed scenarios must be retested as fixes are made available.

2.  []{#__RefHeading___Toc88362789 .anchor}Post-Processor

    1.  Input Data Creation

The test data for the Post-Processor will need to be generated by the
GEN-II V2 dose calculation software and will be contained in a
combination of HIF files based on selected media, facility, year range
and uncertainty criteria. Reference data will be contained in
pre-defined receptor description files, isotope description files, risk
factor files, dose factor files and behavior pathway usage files. The
appropriate combination of input files will be set up for each execution
run as they pertain to the test scenarios within that particular run.

2.  Expected Results Calculation

Expected results for each test scenario will be determined through both
manual calculations and other tool-assisted methods. In the most basic
scenario, the application obtains data directly from an HIF file for a
given media, exposure set, facility, year and uncertainty, then
multiplies by a series of risk, dose and usage factors and places the
data by organ and total in a specific row within the XLS output file
based on corresponding row indices for a given location, receptor, year,
uncertainty, pathway and isotope. These calculations are relatively
simple, self-explanatory and will not require additional explanation
beyond referencing the detailed design requirement. A tool will be
developed using Microsoft Excel to determine risk and dose values for
expected results.

3.  Error Messages Confirmation

\[TBD\]

4.  Output Data Comparison Analysis

Once each test execution run has completed successfully, the output
files for each run will be captured and analyzed using a text editor or
Microsoft Excel to assist in the analysis.

For each test scenario within the corresponding XLS output file, the
index values will be matched to find the actual risk and dose values for
specific organ name or total. The row number will be noted and the index
portion of the row of data will captured including the organ name or
total and the actual risk or dose values will be placed in the
traceability matrix for comparison with the expected values.

If the actual value matches expected results within acceptable
tolerances, the scenario is marked as passed in the verification column.
If the value does not match the expected results, the scenario is marked
as failed in the verification column and placed in the failed history.
Failed scenarios must be retested as fixes are made available.

6.  []{#__RefHeading___Toc88362790 .anchor}TEST DESCRIPTION

    1.  []{#__RefHeading___Toc88362791 .anchor}Pre-Processor

There will be a total of 6 execution runs setup for particular sets of
test scenarios. Each Pre-Processor run will create the necessary
permutations of data output to allow confirmation of the particular
requirements that correspond to the given test scenarios. The runs will
be as follows:

-   Run 0.000: Baseline Facility (F Canyon 1954)

-   Run 1.000-.100: Point Estimate & Uncertainty (F Canyon 1954)

-   Run 2.000: Alternate Facility 2 (A Area 1954)

-   Run 3.000: Alternate Facility 3 (L Reactor 1954)

-   Run 4.000: Alternate Year 2 (F Canyon 1955)

-   Run 5.000: Error Messages (C Area 1954)

Reference and Input files will be labeled as version Q for control setup
values and as version X for error message setup values.

1.  []{#__RefHeading___Toc88362792 .anchor}Run 0.000: Baseline Facility

    1.  Test Description

Test Run 0.000 will be the testing baseline and be used to confirm that
a single point estimate can be executed successfully with multiple
exposure location sets using no uncertainty. No additional data
confirmation will be addressed by this run. Setup will be as follows:

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year: 1954

  Uncertainty: No

  Exposure Location Sets: A1STANDQ.txt and A2STANDQ.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

3.  Outputs

Output files: A1F54000.GID and A2F540000.GID

4.  Procedures

Input files will be developed for the baseline with dummy data as
specified by the detailed design. The application will be started and
execution will be setup by selecting the input files with the user
interface. Media will be set to Atmospheric, facility will be set to F
Canyon and year will be set to 1954. Uncertainty will not be selected.
The run will be executed to create the GID(s). Output files will be
identified and confirmed. Content of each output file will be reviewed
and analyzed as needed to confirm specific scenarios.

5.  Scenarios

-   Run 0.000 (Baseline Facility F)

Baseline: A single point estimate will be executed successfully with
multiple exposure location sets using no uncertainty.

1.  []{#__RefHeading___Toc88362793 .anchor}Run 1.000-.100: Point
    Estimate & Uncertainty

    1.  Test Description

Test Run 1 is actually 3 runs in one. Test Run 1.000 will be used to
confirm that the point estimate can be executed successfully during an
uncertainty run. It will also be used to confirm all data values for the
point estimate. Setup and execution will also create files for 100
uncertainty test runs. Two of these uncertainty runs (1.001 and 1.100)
will be used to confirm source term uncertainty factors and parameter
uncertainty values. Setup will be as follows:

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year: 1954

  Uncertainty: Yes

  Exposure Location Set: A1STANDQ.txt and A2STANDQ.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

3.  Outputs

Output files: A1F54000.GID, A1F54001.GID through A1F54100.GID

4.  Procedures

Original input files developed for the baseline will be used. The
application will be started and execution will be setup by selecting the
input files with the user interface. Media will be set to Atmospheric,
facility will be set to F Canyon and year will be set to 1954.
Uncertainty will be selected. The run will be executed to create the
GID(s). Output files will be identified and confirmed. Content of each
output file will be reviewed and analyzed as needed to confirm specific
scenarios

5.  Scenarios

-   Run 1.000 (Point Estimate)

General Setup: Basic setup procedures will be reviewed for accuracy of
the user interface, reading standard files and generating the GID
file(s).

F Canyon: Reading facility description and exposure location description
files will be confirmed. Release height and distance calculations for
baseline facility will be confirmed.

Source Term Point Estimate: Correct values for cflux lines will be
confirmed for all isotopes as defined in the source term file for the
given year. It will also be confirmed that no cflux lines are written
for daughter isotopes.

Parameter Point Estimate: Correct values for three types of parameters
will be confirmed. The Isotope Independent variable checked will be
BIOMA2 (Animal feed standing biomass (wet)). The Isotope Dependent
variable checked will be CLBFF (Bioaccumulation in Freshwater Fish)
which applies to AM241 and I131. Both BIOMA2 and BIOMAS (Standing
biomass (wet)) will be checked as the Exposure Location Dependent
variable.

1954: The correct directory path and file name of the Meteorological
file will be checked.

Exposure Set 1: Values will be checked for correct exposure name and
label.

Exposure Set 2: The second exposure set will generate GID files and the
values for unused exposure locations remain unchanged from the template.

Model State: Correct values will be checked for "xxxModelStat" and
"ModState". All values should be "1" except for Con1 which should be
"2".

QA File: Confirm that the QA file is created and contains correct
information.

Batch File: Confirm that the Batch file is created and contains correct
information.

Informational Messages: Confirm that the Message file is created and
contains correct information for non-error messages that occur during
normal execution without aborting, such as an isotope not included in
the Facility Release File.

-   Run 1.001 (Uncertainty 001)

Source Term Uncertainty 001: New values for cflux lines will be
confirmed for all isotopes to ensure application of the source term
uncertainty factor.

Parameter Uncertainty 001: New values for three types of parameters will
be confirmed to ensure application of the parameter uncertainty values.

-   Run 1.100 (Uncertainty 100)

Source Term Uncertainty 100: Correct values for cflux lines will be
confirmed for all isotopes including the application of the source term
uncertainty factor.

Parameter Uncertainty 100: New values for three types of parameters will
be confirmed to ensure application of the parameter uncertainty values.

1.  []{#__RefHeading___Toc88362794 .anchor}Run 2.000: Alternate Facility
    2

    1.  Test Description

Test Run 2.000 will be used to confirm distance calculations for a
second facility. Setup will be as follows:

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmosphere

  Facility: A Area

  Year: 1954

  Uncertainty: No

  Exposure Location Set: A1STANDQ.txt

  Pre-Processor Input files: AA5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

3.  Outputs

Output files: A1A54000.GID

4.  Procedures

Original input files developed for the baseline will be used except a
copy of Facility F Canyon data will be created and labeled as A Area
with appropriate file name that matches naming standards. The
application will be started and execution will be setup by selecting the
input files with the user interface. Media will be set to Atmospheric,
facility will be set to A Area and year will be set to 1954. Uncertainty
will not be selected. The run will be executed to create the GID(s).
Output files will be identified and confirmed. Content of each output
file will be reviewed and analyzed as needed to confirm specific
scenarios

Scenarios

-   Run 2.000 (Alternate Facility 2)

A Area: New values will be confirmed for release height, distance to
each exposure location, northing and easting. New Sitename value will
also be confirmed.

1.  []{#__RefHeading___Toc88362795 .anchor}Run 3.000: Alternate Facility
    3

    1.  Test Description

Test Run 3.000 will be used to confirm distance calculations for a third
facility. Setup will be as follows:

Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: L Reactor

  Year: 1954

  Uncertainty: No

  Exposure Location Set: A1STANDQ.txt

  Pre-Processor Input files: AL5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

2.  Outputs

Output files: A1L54000.GID

3.  Procedures

Original input files developed for the baseline will be used except a
copy of Facility F Canyon data will be created and labeled as L Reactor
with appropriate file name that matches naming standards. The
application will be started and execution will be setup by selecting the
input files with the user interface. Media will be set to Atmospheric,
facility will be set to L Reactor and year will be set to 1954.
Uncertainty will not be selected. The run will be executed to create the
GID(s). Output files will be identified and confirmed. Content of each
output file will be reviewed and analyzed as needed to confirm specific
scenarios.

Scenarios

-   Run 3.000 (Alternate Facility 3)

L Reactor: New values will be confirmed for release height, distance to
each exposure location, northing and easting. New Sitename value will
also be confirmed.

1.  []{#__RefHeading___Toc88362796 .anchor}Run 4.000: Alternate Year 2

    1.  Test Description

Test Run 4.000 will be used to confirm source term data changes for a
given year. Setup will be as follows:

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year: 1955

  Uncertainty: No

  Exposure Location Set: A1STANDQ.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

3.  Outputs

Output files: A1F55000.GID

4.  Procedures

Original input files developed for the baseline will be used. The
application will be started and execution will be setup by selecting the
input files with the user interface. Media will be set to Atmospheric,
facility will be set to F Canyon and year will be set to 1955.
Uncertainty will not be selected. The run will be executed to create the
GID(s). Output files will be identified and confirmed. Content of each
output file will be reviewed and analyzed as needed to confirm specific
scenarios.

5.  Scenarios

-   Run 4.000 (Alternate Year 2)

1955: New Sitename value will be confirmed to include alternate year.
Different value will be confirmed for Meteorological file name. New
cflux values will be confirmed as indicated by the alternate year column
in the original source term file.

1.  []{#__RefHeading___Toc88362797 .anchor}Run 5.000: Error Messages

    1.  Test Description

Test Run 5.000 will actually be a series of unique runs that will
designed to correspond to specific error message scenarios. Setup will
be as follows:

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: C Area or D Area

  Year: 1954 or 1993

  Uncertainty: No or Yes

  Exposure Location Set: A1STANDX.txt

  Pre-Processor Input files: AC5492X.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACX.xls,
  EXPDESCX.xls, FACDESX.xls, PAUNCERX.xls, STUNCERX.xls
  -----------------------------------------------------------------------

> Note: Input files for version X will only be used for specific test
> scenarios where applicable, otherwise control files for version Q will
> be used.

3.  Outputs

Output files: AC1954Q.MES, AC1954X.MES, AC1993Q.MES, AD1954Q.MES, and
AF1955Q.MES

4.  Procedures

Procedures will vary greatly since each scenario requires a different
setup. In general the original input files developed for the baseline
will be used. However, each error scenario may require a modification to
an input file. In general, media will be set to Atmospheric, facility
will be set to C Area and year will be set to 1955. Uncertainty will not
be selected. Each run will be executed to create the GID(s). Output
files will be identified and confirmed. Content of each output file will
be reviewed and analyzed as needed to confirm specific scenarios. Any
variation from this procedure will be listed in the scenarios.

Scenarios

-   Run 5.000 (Error Messages)

No C Area Facility: The facility description file will be modified to
remove the C Area facility line. A run will be setup to utilize this
file and should abort.

No D Area File: A run will be setup to utilize the D Area facility
without a release file. More specifically, a dummy release file will be
created to be selected during the setup, but removed from the directory
just prior to execution. The process should abort and write an error.

Bad 1993 Year: A run will be setup to select 1993 which is outside the
range of the standard release file. The process should abort and write
an error.

Empty GID File: The standard GID file will be modified to be empty prior
to a run. The process should abort and write an error.

Blank Air3: The Air3 section within the standard GID file will be
removed prior to a run. The process should abort and write an error.

Bad Facility Isotope: A dummy isotope "BADISO" will be placed in the
facility source term file. The process should abort and write an error.

Mismatch Uncertainty: The source term uncertainty file will be modified
to contain less that the typical 100 uncertainty rows. This will be run
simultaneously with a parameter uncertainty file with the typical 100
rows. Uncertainty must be selected. The process should abort and write
an error.

Bad Parameter Isotope: A dummy isotope "BADISO" will be placed in the
parameter uncertainty file. The process should abort and write an error.

Parameter Not Used: A dummy parameter "NOTUSED" will be placed in the
parameter uncertainty file. The process should abort and write an error.

No Exp4: The exposure location description file will be modified to
remove exposure location 4, (Jackson, SC). The process should abort and
write an error.

Blank C Data: The facility source term data file for C Area will be
modified to be empty prior to a run. The process should abort and write
an error.

No MET File: The dispersion facility file will be modified to contain an
invalid Meteorological file. The process should abort and write an
error.

1.  []{#__RefHeading___Toc88362798 .anchor}Post-Processor

There will be 4 Pre-Processor execution runs setup to feed GENII-V2 the
Post-Processor as follows:

-   Run 1.000: Point Estimate Multi-Year (F Canyon 1964-1966)

-   Run 2.000: Point Estimate Single Year (F Canyon 1969)

-   Run 3.000: Point Estimate Multi-Year Gender Assignment (F Canyon
    1972-73, 1981-82, 1989)

-   Run 4.000: Liquid Pathways and Isotope Decay Products

-   Run 5.000: Facility Identification

This will generate a series of GID files that will feed the GENII-V2
dose calculation software. GENII-V2 will then be used to generate the
corresponding HIF files to be used as input for all Post-Processor test
scenarios.

There will be 4 Post-Processor execution runs that will create the
necessary permutations of data output to allow confirmation of the
particular requirements that correspond to the given test scenarios.
These runs will contain the following receptors:

-   Run 1.000: Point Estimate Multi-Year (F Canyon 1964-1966)

    -   Rural Family #1 Child born 1964

    -   Rural Family #2 Child born 1964

    -   Urban Family Child born 1964

    -   Delivery Family Child born 1954

    -   Outdoor Family Child born 1954

    -   Migrant Family Adult Male

    -   Near Water Family Adult Female

-   Run 2.000: Point Estimate Single Year (F Canyon 1969)

    -   Rural Family #1 Child born 1964

    -   Rural Family #2 Child born 1954

-   Run 3.000: Point Estimate (F Canyon 1971-72, 1981-82, 1989)

    -   Urban Family Child born 1955

    -   Urban Family Child born 1964

-   Run 4.000: Liquid Pathways and Isotope Decay Products

    -   Urban Family Child born 1964

-   Run 5.000: Facility Identification

Reference files are static and will remain constant.

1.  []{#__RefHeading___Toc88362799 .anchor}Setup Run 1.000: Point
    Estimate Multi-Year

    1.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year Range: 1964-1966

  Uncertainty: No

  Exposure Location Set: A1STANDA.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

2.  Outputs

Pre-Processor Output files (GENII-V2 Input files): A1B64000.GID,
A1B65000.GID, and A1B66000.GID

GENII-V2 Output files (Post-Processor Input files): A1B64000.HIF,
A1B65000.HIF, and A1B66000.HIF

2.  []{#__RefHeading___Toc88362800 .anchor}Setup Run 2.000: Point
    Estimate Single-Year

    1.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year Range: 1969

  Uncertainty: No

  Exposure Location Set: A1STANDA.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

2.  Outputs

Pre-Processor Output files (GENII-V2 Input files): A1B69000.GID

GENII-V2 Output files (Post-Processor Input files): A1B69000.HIF

3.  []{#__RefHeading___Toc88362801 .anchor}Setup Run 3.000: Point
    Estimate Multi-Year Gender-Assignment

    1.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year Range: 1972-73, 1981-82, 1989

  Uncertainty: Yes

  Exposure Location Set: A1STANDA.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

2.  Outputs

Pre-Processor Output files (GENII-V2 Input files): A1B72000.GID,
A1B73000.GID, A1B81000.GID, A1B82000.GID, A1B89000.GID.

GENII-V2 Output files (Post-Processor Input files): A1B72000.HIF,
A1B73000.HIF, A1B81000.HIF, A1B82000.HIF, A1B89000.HIF

4.  []{#__RefHeading___Toc88362802 .anchor}S**etup Run 4.000: Liquid
    Pathways and Decay Products**

    1.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year Range: 1972-73, 1981-82, 1989

  Uncertainty: Yes

  Exposure Location Set: A1STANDA.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

2.  Outputs

Pre-Processor Output files (GENII-V2 Input files): LZ65000.GID

GENII-V2 Output files (Post-Processor Input files): LZ65000.HIF

5.  []{#__RefHeading___Toc88362803 .anchor}Setup Run 5.000: Facility
    Identification

    1.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon, B

  Year Range: 1964-1965

  Uncertainty: No

  Exposure Location Set: A1STANDA.txt

  Pre-Processor Input files: AF5492Q.xls

  Pre-Processor Reference files: AISOTDEQ.xls, DISPFACQ.xls,
  EXPDESCQ.xls, FACDESQ.xls, PAUNCERQ.xls, STUNCERQ.xls
  -----------------------------------------------------------------------

2.  Outputs

Pre-Processor Output files (GENII-V2 Input files): A1B64000.GID,
A1B65000.GID

GENII-V2 Output files (Post-Processor Input files): A1B64000.HIF,
A1B65000.HIF

6.  []{#__RefHeading___Toc88362804 .anchor}Run 1.000: Point Estimate
    Multi-Year

    1.  Test Description

Test Run 1.000 will be used to confirm point estimate values for the
given receptors in the scenario over a period of years. Receptors have
been selected to capture the largest portion of possible age factor
group permutations within the shortest range of years.

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year Range: 1964-1965

  Dose: by Organs (All)

  Risk: by Organs (All)

  Pathways: by Pathway (All)

  Isotope: by Isotope (All)

  Receptors:\
  Rural Family #1 Child born 1964\
  Rural Family #2 Child born 1964\
  Urban Family Child born 1964\
  Delivery Family Child born 1954\
  Outdoor Family Child born 1954\
  Migrant Family Adult Male\
  Near Water Family Adult Female

  Post-Processor Input files: A1B64000.HIF, A1B65000.HIF, and
  A1B66000.HIF

  Post-Processor Reference files: pathways.xls
  -----------------------------------------------------------------------

3.  Outputs

Post-Processor Output files: A1B(year)(receptor name).XLS

4.  Procedures

3 HIF files resulting from previous execution of the GENII-V2
application will be used as input for the Post Processor. The
application will be started and execution will be setup by selecting the
pathways reference file with the user interface. Media will be set to
Atmospheric, facility will be set to F Canyon and year will be set to
range of 1964-1966. Dose will be by Organs, selecting all. Risk will be
with cancer results including Cancer Incidents by Organs, selecting all,
and Cancer Fatalities by Organs, selecting all. Pathway will be by
Exposure Pathways, selecting all. Isotopes will be by Isotope, selecting
all. Receptors will be selected as identified in the Input matrix. The
run will be executed to create the XLS files. Output files will be
identified and confirmed. Content of each output file will be reviewed
and analyzed as needed to confirm specific scenarios.

5.  Scenarios

Scenarios have been identified to capture combinations of Risk factors,
Dose factors and Usage factors based on Receptor age. The following
table illustrates the scenarios that will be tested with this run.

  ---------- -------- ------------- ------------------------ -------- -----
  Risk       Dose     Behavior      Receptor                 Run Year Age
  Factor     Factor   Pathways                                        
                      (Usage)                                         

  0-5 y      Infant   Infant        Rural Family #1 Child    1964     0
                                    born 1964                         

  0-5 y      1 y old  Pre-school    Rural Family #2 Child    1965     1
                      Child         born 1964                         

  0-5 y      5 y old  Pre-school    Urban Family Child born  1966     2
                      Child         1964                              

  5-15 y     10 y old School Child  Delivery Family Child    1964     10
                                    born 1954                         

  5-15 y     15 y old Teenager      Outdoor Family Child     1966     12
                                    born 1954                         

  25-70 y    Adult    Adult Male    Migrant Family Adult     1964     35
                                    Male                              

  25-70 y    Adult    Adult Female  Near Water Family Adult  1964     35
                                    Female                            
  ---------- -------- ------------- ------------------------ -------- -----

7.  []{#__RefHeading___Toc88362805 .anchor}Run 2.000: Point Estimate
    Single-Year

    1.  Test Description

Test Run 2.000 will be used to confirm point estimate values for the
given receptors in the scenario within the specific year and will
account for additional factor combinations.

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year Range: 1969

  Dose: by Organs (All)

  Risk: by Organs (All)

  Pathways: by Pathway (All)

  Isotope: by Isotope (All)

  Receptors:\
  Rural Family #1 Child born 1964\
  Rural Family #2 Child born 1954

  Post-Processor Input files: A1B69000.HIF

  Post-Processor Reference files: pathways.xls
  -----------------------------------------------------------------------

3.  Outputs

Post-Processor Output files: A1B(year)(receptor name).XLS

4.  Procedures

1 HIF file resulting from previous execution of the GENII-V2 application
will be used as input for the Post Processor. The application will be
started and execution will be setup by selecting the pathways reference
file with the user interface. Media will be set to Atmospheric, facility
will be set to F Canyon and year will be set to 1969. Dose will be by
Organs, selecting all. Risk will be with cancer results including Cancer
Incidents by Organs, selecting all, and Cancer Fatalities by Organs,
selecting all. Pathway will be by Exposure Pathways, selecting all.
Isotopes will be by Isotope, selecting all. Receptors will be selected
as identified in the Input matrix. The run will be executed to create
the XLS files. Output files will be identified and confirmed. Content of
each output file will be reviewed and analyzed as needed to confirm
specific scenarios.

5.  Scenarios

Scenarios have been identified to capture combinations of Risk factors,
Dose factors and Usage factors based on Receptor age. The following
table illustrates the scenarios that will be tested with this run.

  -------- ---------- --------------- ------------------------ ------ -----
  Risk     Dose       Behavior        Receptor                 Run    Age
  Factor   Factor     Pathways                                 Year   
                      (Usage)                                         

  5-15 y   5 y old    School Child    Rural Family #1 Child    1969   5
                                      born 1964                       

  5-15 y   15 y old   Teenager        Rural Family #2 Child    1969   15
                                      born 1954                       
  -------- ---------- --------------- ------------------------ ------ -----

8.  []{#__RefHeading___Toc88362806 .anchor}Run 3.000: Point Estimate
    Multi-Year Gender-Assignment

    1.  Test Description

Test Run 3.000 will be used to confirm point estimate for the given
receptors in the scenarios as they age from teenagers to adults. Setup
will be as follows:

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon

  Year Range: 1972,-73, 1981-82, 1989

  Dose: by Organs (All)

  Risk: by Organs (All)

  Pathways: by Pathway (All)

  Isotope: by Isotope (All)

  Receptors:\
  Urban Family Child born 1954, Urban Family Child born 1955, Urban
  Family Child born 1964

  Post-Processor Input files: A1B72000.HIF, A1B73000.HIF, A1B81000.HIF,
  A1B82000.HIF, A1B89000.HIF

  Post-Processor Reference files: pathways.xls
  -----------------------------------------------------------------------

3.  Outputs

Post-Processor Output files: AB(year)(receptor name).XLS

4.  Procedures

HIF files resulting from previous execution of the GENII-V2 application
will be used as input for the Post Processor. The application will be
started and execution will be setup by selecting the pathways reference
file with the user interface. Media will be set to Atmospheric, facility
will be set to F Canyon and year will be set to 1972-1973, 1981-1982, or
1989 depending on the scenario. Dose will be by Organs, selecting all.
Risk will be with cancer results including Cancer Incidents by Organs,
selecting all, and Cancer Fatalities by Organs, selecting all. Pathway
will be by Exposure Pathways, selecting all. Isotopes will be by
Isotope, selecting all. Receptors will be selected as identified in the
Input matrix. The run will be executed to create the XLS files. Output
files will be identified and confirmed. Content of each output file will
be reviewed and analyzed as needed to confirm specific scenarios.

5.  Scenarios

Scenarios have been identified to capture combinations of Risk factors,
Dose factors and Usage factors based on Receptors aging from teenagers
to adults when a gender is assigned based on their birth year. The
following table illustrates the scenarios that will be tested with this
run.

  -------- --------- --------------- ------------------------ ------ ------
  Risk     Dose      Behavior        Receptor                 Run    Age
  Factor   Factor    Pathways                                 Year   
                     (Usage)                                         

  15-25    Adult     Adult Female    Urban Family Child born  1982   18
                                     1964                            

  15-25    15 y old  Teenager        Urban Family Child born  1981   17
                                     1964                            

  15-25    Adult     Adult Male      Urban Family Child born  1972   18
                                     1955                            

  15-25    15 y old  Teenager        Urban Family Child born  1973   17
                                     1955                            

  25-70    Adult     Adult Male      Urban Family Child born  1989   35
                                     1954                            
  -------- --------- --------------- ------------------------ ------ ------

9.  []{#__RefHeading___Toc88362807 .anchor}Run 4.000: Liquid Pathways
    and Decay Products

    1.  Test Description

Test Run 4.000 will be used to confirm the Liquid Media and isotope
decay product calculations.

2.  Inputs

  -----------------------------------------------------------------------
  Media: Liquid

  Facility: F Canyon

  Year Range: 1965

  Dose: by Organs (All)

  Risk: by Organs (All)

  Pathways: by Pathway (All)

  Isotope: by Isotope (All)

  Receptors:\
  Urban Family Child born 1964

  Post-Processor Input files:LZ65000.HIF

  Post-Processor Reference files: pathways.xls
  -----------------------------------------------------------------------

3.  Outputs

Post-Processor Output files: LZ(year receptor name).XLS

4.  Procedures

The HIF file resulting from a previous execution of the GENII-V2
application will be used as input for the Post Processor. The
application will be started and execution will be setup by selecting the
pathways reference file with the user interface. Media will be set to
Liquid, facility will be set to F Canyon and year will be set to 1965.
Dose will be by Organs, selecting all. Risk will be with cancer results
including Cancer Incidents by Organs, selecting all, and Cancer
Fatalities by Organs, selecting all. Pathway will be by Exposure
Pathways, selecting all. Isotopes will be by Isotope, selecting all.
Receptors will be selected as identified in the Input matrix. The run
will be executed to create the XLS file. The output file will be
identified and confirmed. The content of the output file will be
reviewed and analyzed as needed to confirm the specific scenario.

5.  Scenarios

The scenario was identified to capture combinations of isotopes and
their decay products in addition to utilizing the Liquid pathways. The
following table illustrates the scenario that will be tested with this
run.

  -------- --------- ----------------- ---------------------- ------- -----
  Risk     Dose      Behavior Pathways Receptor               Run     Age
  Factor   Factor    (Usage)                                  Year    

  0-5 y    1 y old   Pre-school Child  Urban Family Child     1965    1
                                       born 1964                      
  -------- --------- ----------------- ---------------------- ------- -----

10. []{#__RefHeading___Toc88362808 .anchor}Run 5.000: Facility
    Identification

    1.  Test Description

Test Run 5.000 will be used to confirm the facility identified in the
GENII-V2 output file is correctly output in the Post-Processor output
file.

2.  Inputs

  -----------------------------------------------------------------------
  Media: Atmospheric

  Facility: F Canyon, B

  Post-Processor Input files:A1B64000.HIF, A1B65000.HIF, A1F64000.HIF
  A1F65000.HIF
  -----------------------------------------------------------------------

3.  Outputs

Post-Processor Output files: A1(facility)(year)(receptor name).XLS

4.  Procedures

The HIF file resulting from a previous execution of the GENII-V2
application will be used as input for the Post Processor. The
application will be started and execution will be setup by selecting the
pathways reference file with the user interface. Media will be set to
Liquid, facility will be set to F Canyon or B and year will be set to
1964 or 1965. Pathway will be by Exposure Pathways, selecting all.
Isotopes will be by Isotope, selecting all. The run will be executed to
create the XLS files. The output files will be identified and confirmed.
The content of the output files will be reviewed and analyzed as needed
to confirm the specific scenario.

5.  Scenarios

The scenario was identified to confirm that the Facility identifier
located in the GENII-V2 output file is correctly inserted in the
Post-Processor output file. Multiple years and facilities will be used
and the Post-Processor output file and GENII-V2 facility identifier
values will be compared.