Establish the Validation Environment (User Story)

Purpose:

Establish and maintain the environment needed to support validation.

Objective:

Execute and run the System and Acceptance Tests in order to validate that the developed system or the acquired system (COTS or SaaS) meets the specified requirements and to demonstrate that the system fulfills its intended use when placed in the intended environment.

Description:

The requirements for the validation environment are driven by the product or product components selected, by the type of the work products (e.g., design, prototype, final version), and by the methods of validation. These selections can yield requirements for the purchase or development of equipment, software, or other resources. These requirements are provided to the requirements development processes for development. The validation environment can include the reuse of existing resources. In this case, arrangements for the use of these resources should be made.

Example types of elements in a validation environment include the following:

    • Test tools interfaced with the product being validated (e.g., scope, electronic devices, probes)
    • Temporary embedded test software
    • Recording tools for dump or further analysis and replay
    • Simulated subsystems or components (e.g., software, electronics, mechanics) Simulated interfaced systems (e.g., a dummy warship for testing a naval radar)
    • Real interfaced systems (e.g., aircraft for testing a radar with trajectory tracking facilities)
    • Facilities and customer-supplied products
    • Skilled people to operate or use all the preceding elements
    • Dedicated computing or network test environment (e.g., pseudo-operational telecommunications network testbed or facility with actual trunks, switches, and systems established for realistic integration and validation trials)

Early selection of products or product components to be validated, work products to be used in validation, and validation methods are needed to ensure that the validation environment will be available when necessary.

The validation environment should be carefully controlled to provide for replication, results analysis, and revalidation of problem areas.

Inputs:

  • System Test Plan

Outputs:

  • Release Audit Document

Controls:

  • <?>

Task Instructions:

Install Test Environment

    1. Using the Baseline System Test Plan, [the Project Manager], with support from [the System Deployment Manager], is responsible for setting up the test environment.
    2. Using the Risk Log, [the Project Manager], with support from [the System Deployment Manager], is responsible for identifying and documenting risks associated with the lack of a proper testing environment.

Apply Infrastructure Changes

    1. Using the Baseline System Test Plan, [the System Deployment Manager], with support from [the Project Manager] is responsible for installing all computer and network hardware, software, and cabling components possible in preparation for the test.

Apply Security Changes

    1. Using the Baseline System Test Plan, [the Security Manager], with support from the [Project Manager], is responsible for configuring various security access Levels to enable the new system to be used and tested.

Convert and Migrate Data

    1. Using the Baseline System Test Plan, [the Project Manager], with support from [the Operations and Support Manager], is responsible for ensuring that data extracts, conversions, and loads needed to create the test data for the new system are performed.
    2. It is the responsibility of [the Quality Assurance Lead], with support from [the Project Manager], to verify the success and readiness of the data conversions and loads performed.
    3. When additional data interface components are required, it is the responsibility of [the Quality Assurance Lead], with support from [the Project Manager], to coordinate and resolve the dependencies from the Deployment and Operations Team.

Verify Test Environment

    1. Using the Baseline System Test Plan, [the Quality Assurance Lead], with support from [the Project Manager], is responsible for ensuring that the Test environment is as per the requirements and specifications document.

Fix Gaps Related to Test Environment

    1. [The Project Manager], with support from the needed resources, is responsible for fixing gaps identified during the test environment verification.

Verify and Audit Test Environment

    1. Using the Baseline System Test Plan, [the Project Manager], with support from [the Quality Assurance Analyst], is responsible for verifying and auditing the Test environment to check if the environment is as per the specifications described in the System Test Plan.

Conduct Release Audit

    1. Using the Release Audit Template, [the Project Manager], with support from [the Quality Assurance Analyst], is responsible for verifying the integrity of the system baseline.
    2. Using the Release Audit Document, [the Supplier] is responsible for closing issues before building the system from the Configuration Management repository.
    3. NOTE: If several issues are identified, it is the responsibility of [the Project Manager], with support from the Configuration Management Lead to conduct another Configuration Management Audit to ascertain the system’s integrity before building it.