The V&V strategy argues that the objectives are achieved and the validation targets met, across the whole intended functionality including electrical and electronic elements and other technologies, and supports monitoring of external data relevant to SOTIF. Validation targets provide evidence that acceptance criteria are met, with a defined and justified development effort for each selected method (for example test length, analysis depth, number of scenarios). Exposure, controllability and severity can reduce effort where justified; variability of triggering condition parameters is considered; changes trigger regression testing with a rationale for any tailoring; complete V&V documentation exists for each production release; and activities are derived from a combination of methods across integration levels, such as requirements, interfaces, equivalence classes, boundary values, corner and edge cases, field experience, ageing and acceptance criteria.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.