Inputs to design and development are identified as the requirements that matter for the particular kind of product or service, taking account of: functional and performance requirements; what was learned from earlier, similar work; statutory and regulatory requirements; codes of practice or standards the organization has undertaken to apply; what could result from failure; and, under 9100, what could result if materials, processes, components, equipment or products become obsolete. Inputs must be adequate, complete and unambiguous, conflicts among them must be settled, and records kept. Benchmarking, feedback from providers, internal data and data from products in service may also serve as inputs.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.