Key issues Validation Testing

During validation, the software is tested against requirements. This checklist addresses some of the key issues that will lead to effective validation. For this checklist, the more questions that elicit a negative response, the higher the risk that validation testing will not adequately achieve its purpose.

{mosgoogle left}

 Is a complete software requirements specification available?
 Are requirements bounded?
 Have equivalence classes been defined to exercise input?
 Have boundary tests been derived to exercise the software at its boundaries.
 Have test suites been developed to validate each software function?
 Have test suites been developed to validate all data structures?
 Have test suites been developed to assess software performance?
 Have test suites been developed to test software behavior?
 Have test suites been developed to fully exercise the user interface?
 Have test suites been developed to exercise all error handling?
 Are use-cases available to perform scenario testing?
 Is statistical use testing (SEPA, 5/e, Chapter 26) being considered as an element of validation?
 Have tests been developed to exercise the software against
{mosgoogle left} procedures defined in user documentation and help facilities?
 Have error reporting and correction mechanisms been established?
 Has a deficiency list been created?