The standards that govern how software requirements are written, how the software is designed and how code is written, including language subsets, complexity limits and constraints suited to the software level.
Guide or manual Work product in the Avionics and airborne electronics lifecycle
DO-178C requires these standards so requirements, design and code are consistent, reviewable and verifiable. Code that uses constructs hard to verify, reviewers arguing style instead of correctness and structural coverage that is difficult to achieve are the alternative.
The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.