Robustness tests show the executable object code responds correctly to abnormal inputs and conditions defined at the high level. Table A-6 objective 2, described in 6.4.b; applies at levels A, B, C, D, no independence required; activities 6.4.2, 6.4.2.2, 6.4.3, 6.5; outputs: Trace Data, Software Verification Results, and Software Verification Cases and Procedures. Robustness tests are requirements-based, not added on top of requirements-based testing; defensive programming does not replace requirements specifying the response to abnormal conditions.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.