Downloaded from https://www.everyspec.com ADS-65A-HDBK 3.2.2 Preliminary Design Review (PDR). A PDR should be conducted as soon as practical after contract award. When the sensor is part of an air vehicle procurement, the air vehicle PDR should include a separate payload PDR, including senor software and sensor integration with the air vehicle. The PDR should be conducted in order to: 1) Identify all Qualification Requirements using a verification matrix. 2) Ensure the design approach complies with performance specification and TRD requirements, design criteria, airworthiness qualification and other contract requirements. 3) Provide an understanding of any design changes.
4) Identify changes impacting airworthiness qualification, compliance with required specifications, or increased risk. 5) Identify changes to the test program resulting from design changes. 6) Assess the technical program and AQS progress. 7) Provide the Government access to the software trouble report database. 8) Status and presentation of resolutions for all SSR action items. 9) Explanation of any open PCRs against software requirements. 10) Software architecture, including top-level CSCI structure and evidence that the following considerations are incorporated in the software design, per the guidance of RTCA-DO-178B:
compatibility with the high-level requirements, verifiability, conformance to standards, partitioning integrity, and incorporation of necessary logic affecting system safety. 11) Computer resource allocation, including timing, sequencing requirements, and relevant equipment constraints used in determining allocation. 12) Executive control and start/recovery features of each CSCI. 13) Computer software development facilities, software development tools, test tools. 14) Design features providing for life-cycle software supportability. 15) Review of all software management and quality metrics. 16) Update of software milestone schedule.
17) Update of identified risk areas and risk mitigation measures. 18) Results of software quality and process audits and measurement of software quality metrics as provided for in the Software Quality Assurance Plan. The following items should be submitted NLT 45 days prior to the PDR: a. Preliminary layout and preliminary drawings. b. Preliminary AQS with the verification matrix and its modifications and alterations with Army requirements to include an integrated master schedule. c. Preliminary Corrosion Prevention and Control Plan. d. Structural Design Criteria Report using ADS-29, chapter 4 of AMCP 706-201, MIL- S-8698, and section 3.4 of MIL-A-8868B for guidance. e.
Fatigue Methodology Report prepared using section 7-6.3 of ADS-51-HDBK, section 7-4.2.2.2 of AMCP 706-203, section 4-4.2.1.6 of AMCP 706-201, and other appropriate sections of chapter 4 of AMCP 706-201 for guidance. f. Preliminary E3 Control Plan/Integration Analysis including the following Data Items: i) DI-EMCS-80199B 6