DO-178C / ED-12C - Software Considerations in Airborne Systems
Table A-2: Software development processes – DO-178C / ED-12C - Software Considerations in Airborne Systems

DO-178C / ED-12C - Software Considerations in Airborne Systems A-2.4: Low-level requirements produced

The design process refines the high-level requirements into low-level requirements from which source code can be written directly, with trace data to the high-level requirements. Table A-2 objective 4, described in 5.2.1.a; applies at levels A, B, C, no independence required; activities 5.2.2 (items a, e, f and g), 5.2.3 (a and b), 5.2.4 (a, b and c) and 5.5 b; outputs Design Description, Trace Data. This objective also covers design for software that users can modify (5.2.3) and design for deactivated code (5.2.4, new): the protection mechanisms are developed to the software level of the whole item, and deactivated code is developed in the same way as all other code.

Maintained by Gerard BlokdykControl text last updated

Other controls in Table A-2: Software development processes – DO-178C / ED-12C - Software Considerations in Airborne Systems

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.