The programme or project manager selects a technical requirements definition process that the Engineering Technical Authority has approved and puts it into practice: its activities, requirements, guidelines and documentation are tailored and customised so that technical requirements are defined from the agreed stakeholder expectations for the product layer. The process converts the baselined expectations into technical requirements that are each unique, quantified and measurable, written as shall statements, usable for designing the product.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.