Tag

iso-26262-part-8

5 articles

A white coupe on a workshop lift with its hood and boot lid open, the front fenders, bumper and wheels removed, exposing the radiator, suspension and body structure.

Most ISO 26262 Projects Are Modifications. Treat Them That Way.

A 150-line software change reopened the hazard analysis. A 4,000-line rewrite on the same drive unit barely touched the safety case. When an existing item is modified, ISO 26262 asks which safety activities have to be repeated. The answer comes from what each piece of old evidence assumed, not from how big the change looks or how close the evidence sits to the changed code. New article, with a one-pedal driving mode added to an electric drive unit as the worked example.

7 minNov 1, 2026

Three engineers share one laptop at a vehicle test rig with a steering wheel and wiring harnesses around them.

Technical

The Development Interface Agreement: Who Owns What in ISO 26262

Nobody develops the whole item. Safety still has to hold across the vehicle maker, the supplier, the chip vendor and the software house. The Development Interface Agreement is how ISO 26262 makes that work: who does which safety activity, who is responsible, what is exchanged, and what happens when something goes wrong. New article, worked through on a battery management system: where an agreement is needed, where it is not, and the four questions it has to answer.

4 minOct 27, 2026

A friendly white robot works at a laptop; two glowing paths lead from it, one to a car driving on a road at dusk and one to a second laptop showing source code

Technical

AI Coding Agents and ISO 26262: Classify the Use, Not the Tool

An agent writes four hundred lines in eleven minutes. Tests included, coverage at target, analyzer clean. ISO 26262 has no clause for AI coding tools, and ISO/PAS 8800 says it does not cover them either. The existing rules already do: generated code is code, and each use of the assistant is a tool use with its own confidence level. Drafting code can sit at TCL1. A model that replaces a human reviewer, with nothing behind it, cannot. New article on where AI assistants and agents help, where they bite, and a policy that fits on one page.

7 minOct 22, 2026

A matrix table illustrating the four quadrants of automotive component reuse in ISO 26262, showing the impact of changed contexts and elements on functional safety requirements.

Miscellaneous

The Hidden Risks of Legacy Software Reuse in ISO 26262

Reusing mature legacy software saves time but introduces hidden functional safety risks when moved to a new vehicle context. Learn how to navigate the four quadrants of ISO 26262 component reuse and ensure your safety arguments remain watertight.

7 minAug 3, 2026

Confidence in Software Tools: A Guide to ISO 26262 Qualification

Discover how to build confidence in your software development tools according to ISO 26262 Part 8. Learn how to calculate Tool Impact, determine Tool Confidence Levels, and apply qualification methods.

8 minMar 5, 2026

Keep learning

Go from article to full guide.

Each guide is a full course with diagrams and worked examples. Open one to see what it covers.

Browse all guides

SoftwareConfidence in the Use of Software ToolsLearn how to classify tools by TCL (1-3) based on Tool Impact, Tool Error Detection, and ASIL requirements. Covers a 7-chapter structure with qualification methods, practical guidelines, and worked examples for common toolchains.Pro plan pricing Expert plan pricing7 chapters
FoundationsDevelopment Interface AgreementLearn how to define clear safety responsibilities and evidence exchange between OEM and supplier per ISO 26262-8. Covers DIA content structure, RASIC matrix, lifecycle from initiation to production, and assessment coordination.Expert plan pricing14 chapters
SoftwareReuse and Legacy Software SafetyHow to argue safety for what you did not develop this time: reuse routes, delta and impact analysis, carryover of unchanged elements, ISO/PAS 8926 qualification, wrappers, assumptions of use, and the rules for reusing verification evidence honestly.Expert plan pricing12 chapters