test results and evaluation report checkLIST

GUIDELINES FOR THE TEST RESULTS AND EVALUATION REPORT CHECKLIST:

This checklist is provided as part of the evaluation process for the Test Results and Evaluation Report. The checklist assists designated reviewers in determining whether specifications meet criteria established in HUD’s System Development Methodology (SDM). The objective of the evaluation is to determine whether the document complies with HUD development methodology requirements.

Attached to this document is the DOCUMENT REVIEW CHECKLIST. Its purpose is to assure that documents achieve the highest standards relative to format, consistency, completeness, quality, and presentation.

Submissions must include the following three documents, and must be presented in the following order: (First) Document Review Checklist, (Second) the Test Results and Evaluation Report Checklist, and (Third) the Test Results and Evaluation Report.

Document authors are required to complete the two columns indicated as “AUTHOR X-REFERENCE Page #/Section #” and “AUTHOR COMMENTS” before the submission. Do NOT complete the last two columns marked as “COMPLY” and “REVIEWER COMMENTS” since these are for the designated reviewers.

Document reviewers will consult the HUD SDM and the SDM templates when reviewing the documents and completing the reviewer’s portions of this checklist.

AUTHOR REFERENCE (Project Identifier):
Designated Reviewers: / Start Date: / Completed Date: / Area Reviewed: / Comments:
1:
2:
3:
4:
Summary Reviewer:

12 April 2002Peer ReviewPage 1

test results and evaluation report checkLIST
The Test Results and Evaluation Report documents the results of system testing and provides a basis for assigning responsibility for deficiency correction and follow-up.

TABLE OF CONTENTS

1.0General Information

1.1Purpose

1.2Scope

1.3System Overview

1.4Project References

1.5Acronyms and Abbreviations

1.6Points of Contact

1.6.1Information

1.6.2Coordination

2.0Test Analysis

2.1Security Considerations

*2.x[Test Identifier]

2.x.1Expected Outcome

2.x.2Functional Capability

2.x.3Performance

2.x.4Deviations from Test Plan

/

3.0Summary and Conclusions

3.1Demonstrated Capability

3.2System Deficiencies

3.3Recommended Improvements

3.4System Acceptance

* Each test should be under a separate header. Generate new sections and subsections as necessary for each test from 2.1 through 2.x.

12 April 2002Peer ReviewPage 1

test results and evaluation report checkLIST
To be completed by Author / To be completed by Reviewer
REQUIREMENT / AUTHOR XREFERENCE Page #/Section # / AUTHOR COMMENTS / COMPLY / REVIEWER COMMENTS
Y / N
1.0GENERAL INFORMATION
1.1 / Purpose: Describe the purpose of the Test Results and Evaluation Report.
1.2 / Scope: Describe the scope of the Test Results and Evaluation Report as it relates to the project.
1.3 / System Overview: Provide a brief system overview description as a point of reference for the remainder of the document, including responsible organization, system name or title, system code, system category, operational status, and system environment or special conditions.
1.4 / Project References: Provide a list of the references that were used in preparation of this document.
1.5 / Acronyms and Abbreviations: Provide a list of the acronyms and abbreviations used in this document and the meaning of each.
1.6 / Points of Contact:
1.6.1 Information: Provide a list of the points of organizational contact (POCs) that may be needed by the document user for informational and troubleshooting purposes.
1.6.2 Coordination: Provide a list of organizations that require coordination between the project and its specific support function (e.g., release testing, installation coordination, security, etc.). Include a schedule for coordination activities.
To be completed by Author / To be completed by Reviewer
REQUIREMENT / AUTHOR XREFERENCE Page #/Section # / AUTHOR COMMENTS / COMPLY / REVIEWER COMMENTS
Y / N
2.0TEST ANALYSIS
2.1 / Security Considerations: Provide a detailed description of the security requirements that have been built into the system and verified during system acceptance testing. Identify and describe security issues or weaknesses that were discovered as a result of testing.
2.x / [Test Identifier]: (Each test in this section should be under a separate section header. Generate new sections and subsections as necessary for each test from 2.1 through 2.x.) Identify the functions that were tested and are subsequently being reported on.
2.x.1 Expected Outcome: Describe or depict the expected result of the test.
2.x.2 Functional Capability: Describe the capability to perform the function as it has been demonstrated.
2.x.3 Performance: Quantitatively compare the performance characteristics of the system with the requirements stated in the FRD.
2.x.4 Deviations from Test Plan: Describe any deviations from the original Validation, Verification, and Testing Plan that occurred during performance of the test, listing reasons for the deviations.
To be completed by Author / To be completed by Reviewer
REQUIREMENT / AUTHOR XREFERENCE Page #/Section # / AUTHOR COMMENTS / COMPLY / REVIEWER COMMENTS
Y / N
3.0SUMMARY AND CONCLUSIONS
3.1 / Demonstrated Capability: Provide a general statement of the capability of the system as demonstrated by the test, compared with the requirements and security considerations contained in the FRD. An individual discussion of conformance with specific requirements must be cited.
3.2 / System Deficiencies: Provide an individual statement for each deficiency discovered during the testing.
3.3 / Recommended Improvements: Provide a detailed description of any recommendation discovered during testing that could improve the system, its performance, or its related procedures.
3.4 / System Acceptance: State whether the testing has shown that the system is ready for release testing and subsequent production operation.

12 April 2002Peer ReviewPage 1