The plan should say: how requests to change design and development outputs are controlled; who may raise a change request; how the effect of a change is reviewed; who may approve or reject a change; and how implementation of a change is checked. Even where the plan contains no design and development requirement, the organization may still have to control changes to the outputs it planned, for example to allow substitute materials, to react to shifts in available resources, or to tailor service outputs to a particular customer.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.