A representative set of scenarios, or use cases with their actors, goals and needs, is defined to reveal every capability the expected operating and other life cycle concepts call for, to bound the range of use, environment and interfacing systems, and to set critical and desired performance thresholds. The preliminary OpsCon, acquisition, deployment, support and retirement concepts are elaborated in detail with the stakeholders, at levels of abstraction suited to acquirer, user and supplier. The interactions between users and the system, and the factors affecting them (workplace, normal and unusual use, users' skills and knowledge), are identified, applying human systems integration so that human-centred disciplines (staffing levels, personnel selection, training, human factors, environmental, health and safety concerns, habitability, survivability) shape the requirements.
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.