Software for an item shall be developed with processes and environments fit for safety-related embedded software, covering methods, guidelines, languages and tools; these support consistency across the sub-phases and their work products, and match the system-level and hardware-level development phases in interaction and exchange of information; the criteria for picking the language used for design, modelling or programming are an unambiguous and comprehensible definition, fitness for specifying and managing safety requirements per ISO 26262-8 clause 6 where modelling is used, support for modularity, abstraction and encapsulation, and support for structured constructs (assembly permitted where high-level languages are inappropriate, with tailoring of the development phases); criteria not sufficiently addressed by the language shall be covered by guidelines or the development environment, considering Table 1's topics: enforcement of low complexity, use of language subsets, enforcement of strong typing (all highly recommended at every ASIL), defensive implementation techniques, well-trusted design principles, unambiguous graphical representation, style guides, naming conventions and concurrency aspects (MISRA C and modelling style guides such as MISRA AC are the examples, and the tool qualification or criteria evaluation report of part 8 clause 11 informs tool usage).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.