You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Software being accepted by the SRDP Program for deployment should go through the following stages prior to deployment.  The SRDP Systems Engineer is responsible for documenting that this process is followed.  This is not meant to be a burdensome process, Readiness Reviews may be through e-mail or parts of other meetings the objective is to ensure the consistency and quality of the produced software products.


Add Notification

Testing and Capability Validation


During this phase the software may be repeatedly deployed to the test environment for partial validation and testing by the users and development team.  The objective is to ensure that all new capabilities are performing as expected.  This phase ends with the Test Readiness Review (TRR) gateway review.

Test Readiness Review (TRR):

The purpose of this review is to:

  1. Specify the software system under test.  Generally a tag should be set on the deployed software to provide revision control and allow specific description of the software under test.
  2. Certify by the development team that work on the system is complete.  Internal verification has been successfully performed and the system is ready for validation. 
  3. Review the Validation procedures that will be performed by the team, agree on their sufficiency and necessity.
  4. Ensure that any test fixtures necessary for the validation are in place in the test environment.

System Validation

The system is deployed in the test environment, test fixtures are in place.  The accepting team performs a full system validation based on the procedures defined in the TRR.  The tests should cover both new features as well as regression testing of previously validated procedures.  Automated regression testing during verification may obviate the need for some manual regression testing during this phase.  This phase ends with the Operations Readiness Review (ORR).

Operation Readiness Review (ORR):

The purpose of this review is to certify that all stakeholders agree the software system is ready for deployment.  In particular:

  1. No blocker defects were identified as part of the System Validation.
  2. Any known defects have a documented mitigation (which may be to ignore but at least we know).
  3. Documentation exists to support the release of the new software.

  • No labels