Interfaces between hardware and software systems are described so the integrated system is safe in the specified operational design domain, and each element's boundaries are carefully evaluated. Development is classed as in-context (whole system, all activities), SOTIF-related element out of context (assumptions about use, output insufficiencies and allowed target rates are documented, evidence is produced that targets are met, triggering conditions and output insufficiencies are recorded, and validity of assumptions is checked at vehicle level at integration) or non-specific development where requirements cannot be estimated without the using context, such as a graphics processor.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.