DO-178C / ED-12C - Software Considerations in Airborne Systems
Table A-10: Certification liaison process – DO-178C / ED-12C - Software Considerations in Airborne Systems

DO-178C / ED-12C - Software Considerations in Airborne Systems A-10.2: Means of compliance proposed and PSAC agreed with the authority

The applicant proposes how compliance will be shown and gets the certification authority to agree the PSAC. Table A-10 objective 2, described in 9.b; applies at levels A, B, C, D, no independence required; activities 9.1.a, 9.1.b, 9.1.c; output: the PSAC.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 3 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

DO-254 / ED-80 - Design Assurance Guidance for Airborne Electronic Hardware · 2 controls

  • 10.1.1 10.1.1 Plan for Hardware Aspects of Certification (PHAC)
  • 9.1 9.1 Means of compliance and planning

SAE ARP4754B / ED-79B - Guidelines for Development of Civil Aircraft and Systems · 1 control

  • 3.3 3.3 Certification Authority coordination

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Table A-10: Certification liaison process – DO-178C / ED-12C - Software Considerations in Airborne Systems

Query this from an agent

The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll DO-178C / ED-12C - Software Considerations in Airborne Systems controls