The SRS defines the fundamental actions the software takes in accepting and processing inputs and generating outputs: validity checks on inputs; the exact sequence of operations; responses to abnormal situations, including overflow, communication facilities, hardware faults and failures, and error handling and recovery; the effect of parameters; and the relationship of outputs to inputs, including input-output sequences and conversion formulas. Functional requirements may be partitioned into sub-functions or sub-processes without implying that the design is partitioned the same way.
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.