DO-178C: Software Considerations in Airborne Systems and Equipment Certification¶
RTCA. (2011). DO-178C: Software Considerations in Airborne Systems and Equipment Certification.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Surjectivity
- The structural payoff is the completeness guarantee the standard demands: a requirements-traceability matrix is exactly a check for surjectivity, and a requirement with no covering test is an orphaned codomain element — the prime's characteristic failure — flagged as a coverage gap that must be closed before sign-off.
This sourceRequirements-to-test traceability and structural coverage obligations in safety-critical software, where a requirement with no covering test is a flagged coverage gap.
- The structural payoff is the completeness guarantee the standard demands: a requirements-traceability matrix is exactly a check for surjectivity, and a requirement with no covering test is an orphaned codomain element — the prime's characteristic failure — flagged as a coverage gap that must be closed before sign-off.
Mechanisms¶
- Test-Case-to-Requirement Linker
- A flight-control software team works under DO-178C, which requires bidirectional traceability between requirements and the tests that verify them.
This sourceThe FAA's DO-178C comparison confirms bidirectional traceability between software requirements and the verification cases that test them.
- A flight-control software team works under DO-178C, which requires bidirectional traceability between requirements and the tests that verify them.
- Test Coverage Link
- High structural code coverage — even a rigorous criterion like MC/DC, which requires each condition in a decision to independently affect the outcome — proves the code was exercised, not that it does what the requirement demanded
This sourceDO-178C. RTCA, Inc. (2011). Defines MC/DC through each condition's independent effect and distinguishes structural exercise from requirements-based verification.
- High structural code coverage — even a rigorous criterion like MC/DC, which requires each condition in a decision to independently affect the outcome — proves the code was exercised, not that it does what the requirement demanded
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:ee8b5bf12137 · see in the full table