Table A.2 lists the techniques for expressing the software requirements specification: formal methods (mathematically based, D.28) R at SIL 1 and 2, HR at SIL 3 and 4; modelling (Table A.17), structured methodology (D.52) and decision tables (D.13) each R at Basic Integrity, SIL 1 and 2 and HR at SIL 3 and 4. Requirements: the specification includes a plain-language statement of the problem with whatever formal or semi-formal notation is needed; one or more of the techniques is selected to satisfy the SIL.
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.