The context of use is set out inside the ConOps and the early life cycle concepts produced by business or mission analysis (an ISO/IEC 25063 context-of-use description may serve). Stakeholder needs are identified by eliciting them directly, by inferring implicit needs from domain knowledge and context, and from gaps documented earlier; measures of effectiveness, functional analysis and the ISO/IEC 25010 and 25030 quality models help surface non-functional needs. Needs are prioritized and down-selected using decision management, with measurement, system analysis and risk management for insight. The needs and their rationale are defined after evaluating every source: goals, mission profile, operational scenarios (including day-in-the-life walk-throughs), operational environment and context of use, deployment, performance, effectiveness, operational life, organizational environment, and user and operator characteristics including accessibility.
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.