Dan@DCLConsult.com
402.598.6859
Software Test Readiness Review (TRR) – Best Practice
This activity is performed to ensure the software is ready to enter system level testing. This event is
handled as a technical interchange between the knowledgeable systems engineers, software developers,
business analysts, test analysts, and users.
The developer’s software development deliverables and the system test plan are the inputs to the TRR.
Key features and subsystems, interfaces with existing or planned systems required for mission
accomplishment, identification of critical system characteristics, explicit technical performance
measurements, user defined requirements, developmental test schedules that include statutory tests, and
other salient information must all be considered during the TRR.
Typical documents, or their equivalents, reviewed during this activity may include the software
requirements specification (SRS), interface requirements specification (IRS), test plans, data conversion
tools, test input data, and the Software Users Manual (SUM).
Other items that may be addressed include lower level (unit) test and integration results; system test
procedures; other documentation updates; software problem reports; and software test tools, facilities, and
schedules including sufficient resources availability over the planned schedule.
During the TRR, test procedures are evaluated for compliance with the software requirements
specification (SRS), interface requirements specification (IRS), system test plan, and other documentation
as applicable. Results of lower level (unit) testing accomplished to date are reviewed to ensure all
functional and performance requirements have been satisfied (no significant deficiencies exist in the
product being tested). Open problem reports against the software being tested are examined to determine
if the test should be delayed until the reports are closed. The process used to develop the software and the
environment/test data being used in the test are reviewed and assured to be acceptable. The TRR is
successful when you have determined the system test plan, lower level test results, and the existent system
documentation form a satisfactory basis for proceeding to system testing.
Need some help? Call me.
Dan Livingston
President, DCLC
WWW.DCLConsult.com
Dan@DCLConsult.com
402.598.6859
Superior Performance – Quality Results – Reasonable Rates