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. Primary channel of notification for the TRR and ORR is the SRDP-DMS coordination meeting although alternative methods may be used, by prior consent of the SRDP Systems Engineer (Bob Treacy).
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 The announcement for deployment of a release is to the aat-testing email list. The objective is to ensure that all new capabilities are performing as expected. This phase ends with the Test Readiness Review (TRR) gateway review.
...
- 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.
- 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.
- Check that all feature validation is complete (all tickets should be in the pending release stage).
- Review the Validation procedures that will be performed by the team, agree on their sufficiency and necessity.
- Ensure that any test fixtures necessary for the validation are in place in the test environment.
...
- No blocker defects were identified as part of the System Validation.
- Any known defects have a documented mitigation (which may be to ignore but at least we know).
- Documentation exists to support the release of the new software.
Deployment
Assuming a successful ORR the software is ready for deployment to production. This operation will be performed by DMS and stakeholders notified. The announcement for deployment of a release is to the ssa-announcements email list. A deployment test should be performed at this point to ensure that there were no issues introduced as part of the deployment. Deployment testing is a shared responsibility of DMS and SRDP.