Possible alternative solutions are studied for feasibility to judge whether each is viable and to choose the preferred one, which may be piloted where suitable to identify improvements: the acquisition or development actions are derived from the enterprise architecture within limits of scope, time and budget; all stakeholders review the alternatives and the best fit is chosen using feasibility criteria that include cost and risk; the chosen course becomes a high-level plan for acquisition or development naming resources and the stages that need a go or no-go decision; and a feasibility study, pilot or simple working version sets out the alternatives and measures how well each meets the business and functional requirements, covering cost, benefits, risk and lessons learned.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.