Defines documents, reports and activities needed while executing a series of tests with the primary purpose of fully exercising the software release being created.
What this is
This phase covers documents, reports and activities needed while executing a series of tests to fully exercise the entire software release. Different tests will have different purposes, such as functional tests versus stress tests. All the tests performed during this phase are for the purpose of verifying that all the modules or "parts" of the software release have been correctly integrated and the functions specified perform properly.
Why it's useful
The customer will receive the software release as a single entity. This single entity needs to meet Quality Goals and Standards and system testing is part of the verification to that end.
To that end, this phase will possibly include:
How to use it
Review the phase deliverables suggested in this document. Adjust for your particular organization, project type, or company. See the included checklist for documents included in this phase. Use these deliverables to ensure that the team stays focused on critical release issues, reduces scope creep, and provides a quality product to the customer.
©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail firstname.lastname@example.org