The StRS states the user requirements, the requirements for use that are the basis for designing and evaluating the system against identified user needs: requirements on the quality of use, usability included (the outcomes intended and the criteria for judging them), user-system interaction requirements needed to reach those outcomes, and any constraints on the freedom of design and implementation; they can serve as the basis for operational scenarios. The context of use the design assumes is written into the user requirements so that it is clear when they apply, and usability requirements and objectives carry criteria for effectiveness, efficiency and satisfaction that can be measured in named contexts of use.
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.