HDL code coverage gathered during requirements-based simulation is recognised as a way to perform DO-254 Appendix B elemental analysis for digital devices (it measures whether code was exercised, not whether requirements testing is complete). For DAL A or B, where it is used, the planning documents define the detailed coverage criteria for the HDL constructs used (for example branches and conditions), and every case or element not covered is analysed and justified, with additional analysis where code coverage cannot reach, as can happen with COTS IP.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.