Table A.5 lists ten verification and testing techniques: formal proof R at SIL 1 and 2 and HR at SIL 3 and 4; static analysis (Table A.19) and dynamic analysis and testing (per Table A.13) HR at every SIL above Basic Integrity; metrics R; traceability R at Basic Integrity, HR at SIL 1 and 2 and M at SIL 3 and 4; software error effect analysis R at SIL 1 and 2 and HR above; code test coverage (per Table A.21) R at Basic Integrity and HR above; functional (black-box) testing (per Table A.14) HR to SIL 2 and M at SIL 3 and 4; performance testing (Table A.18) HR above Basic Integrity; interface testing HR at every level. Approved combinations: at SIL 3 and 4 dynamic analysis and testing, traceability, test coverage for code and functional testing plus one of formal proof, static analysis or software error effect analysis; at SIL 1 and 2 traceability plus one of static analysis, dynamic analysis or functional testing. Formal proof, static analysis, metrics, traceability, error effect analysis and coverage serve verification; dynamic analysis, functional, performance and interface testing serve testing.
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.