DO-178C / ED-12C - Software Considerations in Airborne Systems A-4.2: Low-level requirements precise and free of conflict

Each low-level requirement is exact, detailed enough and unambiguous, and the set contains no conflicts. Table A-4 objective 2, described in 6.3.2.b; applies at levels A, B, C, independence required at levels A, B; activities 6.3.2; outputs Software Verification Results.

Maintained by Gerard BlokdykControl text last updated 21 May 2026

Other controls in Table A-4: Verification of outputs of software design process – DO-178C / ED-12C - Software Considerations in Airborne Systems

A-4.1 Low-level requirements satisfy the high-level requirements
A-4.10 Architecture fits the target hardware
A-4.11 Architecture verifiable
A-4.12 Architecture follows the design standards
A-4.13 Partition breaches shown to be prevented
A-4.3 Low-level requirements fit the target hardware
A-4.4 Low-level requirements verifiable
A-4.5 Low-level requirements follow the design standards

Query this from an agent

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

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