Applicable wherever success criteria and test methods have been prescribed-1.e., where there is a specification or comparable document. This Data Item Description is applicable for both flight and ground tests. Tests will usually have been identified in an overall test plan (e.g., DI-T3704 A through DI-T-3714A). Normally used for engineering test and evaluation, prequalification, qualification, and other development tests in the specifications. For system programs, planning information is normally obtained under Data Item Description T-3702A with the cverall test report being covered by Data Item Description T-3716 A. This D supersedes DI-T-3718. 12. PREPARATION INSTRUCTIONS REFERENCES (Mondatory es cited in AFR 80-14, AFSC Sup 1 MCBL NUNDERIN 1. Separate reports will be prepared for each independent test designed to satisfy a specific objective of the program test plan. The following types of reports may be submitted in contractor format: a. "Cuick Look" Report. This report is to be prepared in TX form announcing the accomplishment/occurrence of a significant test event. The specific test will be ideatified, along with salient test conditions and important results/happenings affecting program objectives. Problems requiring immediate attention by the program office will be identified. The complete details of the test will be provided in follow-up formal test reports. b. Final Test Reports. Final reports shall include: (1) Identification of specific test as defined by the program test plan or other contractual document. (2) Functional purpose of test (1.e., developmental, engineering evaluation, pret qualification, qualification, etc). (3) Identification of test objectives, including applicable requirement, specifi cation title, number, and date, as appropriate. (4) Description of test article, including test configuration identification and photographs as appropriate. (5) Summary of test results (details provided in later sections), stating what tests were performed and the results of each test. Where these tests were to show compliance with a given specification, a catrix will be provided comparing test results with specification requirement. DD.1664 (6) Description of test facility and test procedures, including a detailed description of how the test item was operated during the test, and any control conditions imposed. (7) Test set-up diagrams/photos, showing arrangement of test item in relation to test equipment used. (8) A list of all test equipment, identifying manufacturer, model, calibration status, and serial number. (9) Recorded test data or logs, as appropriate, including instrument readings, correction factors, and reduced results, presented in tabular and graphic form. If value of the data has been compromised due to test conditions, the reason and implication should be related. (10) Identification of ambient and other test conditions. (11) Discussion of test result analyses, including calculation examples as appropriate, and conclusions relative to test effectivity and problems. When tests failed to meet objectives, discuss probable impact, design changes, and intended actions. (12) Certification that the test results are authentic, accurate, current, and in accordance with related specifications and test plans. c. Final Report Addendum. These reports are used to update final reports when design changes are made and tests are performed after the final report has been published. The update information will be related to the previous data provided in the final report. d. Interim Test Report. Interim reports are prepared when the test period is long and reporting of test status is required. (1) Initial interim reports will contain the same scope of coverage as for firal reports, except that results and conclusions will be preliminary. (2) Subsequent interim reports need not include descriptive data provided in the initial report, but only changes thereto. 7.1 To be used on contracts which require formal technical reviews and audits. 10. packages shall be provided for design review meetings to be held on the d submitted as indicated on DD Form 1423. The data packages shall be to peovill duequate preparation information for design reviews organized tance with N-375-1521 and Appendices B, C, D, and G. The detail contents zi moon package ».... include, but not be limited to, the material required for the atau ment design review, an agenda, and a status of pertinent (if any) action items Erum panviou、 desi¿ reviews or other meetings. B008 TITLE DATA ITEM DESCRIPTION Users Manual (Computer Program) 3 DESCRIPTION PURPOSE 762269-7-8-130 This manual is used to provide Air Force and/or contractor 7. APPLICATION INTERRELATIONSHIP .. REFERENCES (Mandatory as cited in block 10) This data item description is for application to those systems which contain computer program Cls. The basis for the development of the Users Manual is the Computer Program Development and Product Specifications. The manual will normally be submitted to the procuring activity at the time of AFSCM/AFLCM 375-7 physical configuration audit/acceptance of the computer program CI to which it relates. The Technical Order Publications Plan will include this data requirement when both are contractually incorporated. NOTE: Computer Program User's Manuals are not Technical MCSL NUMBER:S 10 PREPARATION INSTRUCTIONS Content. The users manual for a computer program system shall contain the following: a. Introduction. A description of the manual's purpose, scope, organization and content. b. Glossary. Terms used in the manual. c. Computer Program System Capabilities: (1) Purpose. A description of the purpose of the computer program CI. (2) General Description. A description of the system, giving an overview of the system and its operation. (3) Functions Performed. Identification of the specific functions performed by the computer program Cl. (This may be in terms of systems operations, uses, Cutputs, etc.) 2. Function Description. A description of each specific function within the Ci The following subparagraphs shall be repeated for each function: (1) Title of function. A descriptive title of the specific function. DI-M-310/H-110-2 (Continued) Preparation Instructions (Continued) W62269-79R-0499. (2) Description of function. A summary description of the specific function, including: (a) Purpose and uses of function. (b) Description of system inputs. (c) Description of expected output and results. (d) Relationship to other functions. (e) Summary of function operation. e. Usage Instructions. How to use each specific function. following: This shall include the (1) Preparation of inputs. A definition of the system inputs, other than those required to operate the computer program (see paragraph lf(2). These inputs constitute the basic data that are to be processed by the computer program. The definition shall'include: (a) Title of inputs. (b) Description of inputs. (c) Purpose and use. (d) Input media. (e) Limitation/restrictions. (f) Format and content. (g) Sequencing (e. g., formalized deck structure). (h) Special instructions. (i) Relationship of inputs to outputs. (2) Results of Operation. A definition of expected results after completion of computer program operation. |