Downloaded from https://www.everyspec.com ADS-65A-HDBK ii) DI-EMCS-81528 iii) DI-EMCS-81542A iv) DI-EMCS-81295 v) DI-RELI-80669A vi) DI-RELI-80671A g. Review of Environmental Qualification Requirements 3.2.3 Critical Design Review (CDR). The requirements specified in this paragraph are applicable to the airworthiness portion of the overall system CDR. The CDR should be conducted prior to release of the payload design for hardware production and/or prior to the initiation of software coding. The CDR should be conducted to determine the characteristics of the design, and to ensure incorporation of requirements prior to commitment to major fabrication.
The contractor, in conjunction with the Government, should develop a detailed agenda NLT 30 days prior to the CDR. The following items should be submitted NLT 45 days prior to the CDR: a. The AQS and verification matrix (Final) – The AQS and verification matrix should show the compliance the aircraft, modifications and alterations with Army requirements to include an integrated master schedule. b. Production Drawing Package. c. Safety Assessment Report. d. Loads and Stress Analysis Damage Tolerance and Fatigue Analyses and Reports. e. Materials and Processes specifications to be used in the manufacture of the payload related modifications. f. Preliminary Material Allowable Report. g.
Fatigue Test Plans as Required. h. Calculated Weight. i. Electrical Loads Analysis. j. Final Electromagnetic Environmental Effects Control/Integration Analysis. k. Draft Human Engineering Design Approach Document. l. Final Software Design Documents. m. Final Interface Design Documents. n. Final Software Test Plan or Software Verification Plan. o. Explosive Hazard Classification Data Report. p. Final Functional Hazard Analysis. q. Final Version of the Software FMECA r. Status and presentation of resolutions for all PDR action items s. Explanation of any open PCRs against software requirements. t.
Software architecture, including assignment of CSCI requirements to specific lower-level software components and units u. Overall information and control flow between software units, and sequencing of software operations. v. Evidence that the following considerations are incorporated in the software design, per the guidance of RTCA-DO-178B: compatibility with the high-level requirements, consistency, verifiability, conformance to standards, partitioning integrity, and incorporation of necessary logic affecting system safety. 7