DO-178C / ED-12C - Software Considerations in Airborne Systems
Table A-8: Software configuration management process – DO-178C / ED-12C - Software Considerations in Airborne Systems

DO-178C / ED-12C - Software Considerations in Airborne Systems A-8.3: Problem reporting, change control, change review and status accounting in place

Problems are recorded and tracked, changes are controlled and reviewed, and the configuration status is reported. Table A-8 objective 3, described in 7.1.c, 7.1.d, 7.1.e, 7.1.f; applies at levels A, B, C, D, no independence required; activities 7.2.3, 7.2.4, 7.2.5, 7.2.6; outputs Problem Reports, SCM Records. FAA AC 00-71 (2022) sets best practices for managing open problem reports, complementing AC 20-189.

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.

  • 6.6 Modification and change control
  • 9.2 Software maintenance
  • 8:8.4.1 8.4.1 Planning and initiating change management

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-8: Software configuration management 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.