A project succeeds only if it satisfies the requirements of its customers and other interested parties, so those requirements should be well understood and every process should be able to meet them. Project objectives, product objectives included, should reflect what the customer and other interested parties need and expect; they may be refined as the project proceeds and should be recorded in the project management plan (7.2.2), saying what must be achieved on cost, time and product quality and what will be measured. Any trade-off of cost or time against product quality should consider the effect on the product in light of what the customer requires. Interfaces should be set up with every interested party so that information can be exchanged; conflicting requirements should be resolved, with the customer's requirements usually prevailing unless statutory or regulatory requirements apply; the customer should agree the resolutions, and agreements with interested parties should be documented; and changes in requirements, including those of parties that join after the start, should be monitored throughout.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.