Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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 successful 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.

...

  1. No blocker defects were identified as part of the System ValidagionValidation.
  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.