| Pass | Fail | Checklist for Measurement |
| □ | □ | Is the software validated (tested) as a complete system in an environment as similar as possible to the final operating environment? Is this done prior to delivery and acceptance? |
| □ | □ | If field-testing is required, are the responsibilities of the supplier and the purchaser defined? Is the user environment restored following the test? |
| □ | □ | Are product metrics collected and used to manage the testing effort? |
| □ | □ | Are product defects measured and reported? |
| □ | □ | Is corrective action taken if metric levels exceed established target levels? |
| □ | □ | Are improvement goals established in terms of metrics |
| □ | □ | Are process metrics collected to measure the effectiveness of the testing process in terms of schedule and in terms of fault prevention and detection? |
| Pass | Fail | Checklist for Tools / Techniques |
| □ | □ | Are tools and techniques used to help make testing and management processes more effective? |
| □ | □ | Are the used tools and techniques reviewed, as required, and improved upon? |
| Pass | Fail | Checklist for Training |
| □ | □ | Are training needs identified according to a procedure? |
| □ | □ | Is training conducted for all personnel performing work related to quality? |
| □ | □ | Are personnel who are performing specific tasks qualified on the basis of appropriate education, training, and/or experience? |
| □ | □ |
| Pass | Fail | Checklist for Documentation |
| □ | □ | Are test plans, requirements, and other documents revision controlled? |
| □ | □ | Do procedures exist to control document approval and issue? |
| □ | □ | Are changes to controlled documents reviewed and approved? |
| □ | □ | Are current versions of test documents identifiable by a master list or document control procedures? |
| Pass | Fail | Checklist for Configuration Management |
| □ | □ | Is there a Configuration Management (CM) system that identifies and tracks versions of the software under test, software components, build status, and changes? Does the system control simultaneous updates? |
| □ | □ | Does the configuration management plan include a list of responsibilities, CM activities, CM tools and techniques, and timing of when items are brought under CM control? |
| □ | □ | Is there a mechanism and procedure that enables software, hardware, and files to be uniquely identified throughout the entire software development lifecycle? |
| □ | □ | Is there a documented mechanism to identify, record, review, and authorize changes to software items under configuration management? Is this process always followed? |
| □ | □ | Are affected personnel notified of software changes? |
| □ | □ | Is the status of software items and change requests reported? |
