Appropriate techniques must be selected for the SIL; where an HR technique is not used (or an NR one is used) the rationale is recorded in safety planning against Annex C and agreed with the assessor, and only one of a set of lettered alternatives need be met. For the software safety requirements spec (SSRS) the table lists semi-formal methods (HR at SIL 3 and 4), formal methods (HR at SIL 4), forward traceability between system safety requirements and software safety requirements, backward traceability from the safety requirements to the safety needs as perceived (both R at SIL 1 and 2, HR at SIL 3 and 4), and computer-aided specification tools.
This control maps to 2 controls across 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.