Information needs arise from the technical and management processes and derive from the objectives of the business, the organisation, regulators, the product or the project, and from identified risks, typically as questions about meeting technical objectives, implementation status, product quality during development or future productivity. They are prioritised by or with the stakeholders, often by ranking and averaging, and usually only a subset is pursued, especially on a first attempt where starting small is preferable. A subset is chosen for action, trading resource constraints against criticality and urgency; in large efforts later needs may be identified but defined only when required. The selected needs are recorded in a retrievable form and communicated to all stakeholders so they understand why data is collected and how it is used.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.