About Us


  Process Models

  SE Resources


  Contact us

Breaking News!

A new blog ... visit OnCenter, Roger Pressman's running commentary on the world at large

A new edition ... the 6th edition of Software Engineering is available now

A first novel ... Roger Pressman's first novel is a technothriller -- The Aymara Bridge

A new training curriculum! RSP&A has partnered with QAI to develop a comprehensive Internet-based software engineering curriculum.

A redesigned Web site ... we've done a major redesign and added many new features

Adaptable Process Model
Conducting Validation Tests

IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.

Conducting Validation Tests

    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.

    • 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 procedures defined in user documentation and help facilities?
    • Have error reporting and correction mechanisms been established?
    • Has a deficiency list been created?

      Return to Checklist Table of Contents

Site search! We've added links to a search engine that will enable you to search our entire site for information you need. Enter the appropriate word or phrase below.


Home About us Products Product Models SE Resources Commentary Contact us

Web site and all contents R.S. Pressman & Associates, Inc. 2001 - 2006, All rights reserved.
Free website templates