All stages of the life cycle are considered to identify the stakeholders, or stakeholder classes, with a legitimate interest in the system, including those with strong influence on goals, strategies and operations; representatives of each class are named, drawing on several organizational levels, because input from a single class or level gives a biased picture. A strategy is defined for eliciting needs and turning them into stakeholder requirements, covering approach, milestones, resources and how conflicting interests will be handled (for example building out from the subset on which stakeholders agree, or accepting operational, logical or physical variants). The enabling tools and repositories for elicitation, capture and transformation, including baseline information about the organization's portfolio of systems, are planned and access to them obtained.
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.