DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware A: Appendix A Modulation of life cycle data by design assurance level, and verification independence

Table A-1 sets, for Levels A to D, which data items are submitted to the authority (the PHAC, the verification plan, the top-level drawing and the HAS) and the control category (HC1 or HC2) of each; data used for credit but not submitted must be available. For example, hardware requirements, top-level, assembly and installation drawings and hardware/software interface data are HC1 at every level; traceability data is HC2 at every level, with Level C and D needing only requirement-to-test traceability; test coverage of derived or lower-level requirements is not needed at Level D; the design, validation and process assurance plans, standards and conceptual design data fall away at the lower levels. Level A and B functions need independent verification, at the level where design is verified against requirements, by an individual, process or tool independent of the designer (for example independent review of requirements or design, test cases written or reviewed by someone else, independent review of the designer's analysis, a different confirming test, or tool-verified results); organisational separation is not required, and the designer may still run automated tests once independently developed or evaluated.