The OpsCon contains scenarios: step-by-step accounts, for a stated set of circumstances, of the way the proposed system is meant to work with users and with external interfaces, which may also show what it must not do. They are arranged in sections, cover every operating mode and every user class, set out the events, actions, stimuli, information and exchanges involved, and come in variations for normal operation, stress load, exception handling and degraded mode; prototypes, storyboards or other media may supplement them. Scenarios bind the parts of the system into a whole, provide operational detail, support simulation models for defining and allocating derived requirements, and give a starting point for the initial users' manual and for acceptance test planning; they may be organized by processing function, by thread or transaction type, or by information or control flow. Their number and depth are proportional to the perceived risk and criticality of the project.
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.