Supporting Processes

Supporting processes are the infrastructure activities defined in ISO 26262-8 that every lifecycle phase depends on but no single phase owns: requirements management with traceability, configuration management, change management, documentation management, confidence in the use of software tools, qualification of components, proven in use arguments, interfaces within distributed developments, and competence management. They do not produce the safety design themselves - they make the design work products consistent, reproducible, and auditable. Weak supporting processes are a classic assessment failure mode: the technical work may be sound, but without traceability, baselines, and controlled documents there is no way to demonstrate it.

A DIA is the contract that makes distributed safety development work: it defines, between customer and supplier, who performs which ISO 26262 activities, who produces which work products, and how evidence flows across the company boundary. It covers responsibilities, deliverables, milestones, and the interfaces for joint activities such as safety assessments. The distributed development chapter pairs the DIA with SEooC deliveries and a simple interface map showing who owes whom which evidence.

Proven in use is an argument that an existing component can be relied on in a safety context because of its accumulated field history, as an alternative to developing it fresh to ISO 26262. The argument needs a defined candidate with a stable configuration, relevant and sufficient field data, and a statistical evaluation showing the observed failure rate supports the target. The guide walks the proven-in-use process steps and includes a statistical analysis example showing what the numbers must actually demonstrate.

Through two questions: can a tool malfunction introduce or fail to detect an error in a safety-related work product (tool impact, TI), and how likely is such an error to be detected (tool error detection, TD)? The TI and TD combination yields a tool confidence level, which determines whether qualification is needed and how rigorous it must be. The tools chapter presents the classification matrix, the qualification strategies, and an evidence completeness view for planning the qualification work.

Twelve chapters: an overview with the ISO 26262-8 cross-reference map, then requirements management, configuration management, documentation, proven in use, distributed development, tools, and competence, plus a start-here glossary, four practical checklists, clause references, and a closing electric power steering case study that maps ISO 26262-6 work products onto their V-model dependencies. A free account starts you off, and the Pro and Expert plans unlock more of the concept library.