Tag

seooc

2 articles

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

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 line of commit dots labelled as the mainline runs off the right edge. One dot is ringed in red, and a dashed line drops from it into a card holding five chips: source revision, patch list, configuration, toolchain, build recipe.

Technical

Qualifying Linux for ISO 26262: Pinning the Open-Source Element

You cannot qualify Linux. You can qualify one build of it. ISO 26262 allocates requirements to elements, and an element has to hold still. A mainline kernel does the opposite. Open source gives you more visibility than any commercial supplier will. What it does not give you is traceability from a safety requirement to the test that shows it is met. So the first work product is not a gap analysis. It is a definition: exact source revision, vendor patches, reviewed configuration, toolchain, build recipe. Hand those to an engineer who was not in the room. If they cannot arrive at your binary, or explain every difference, you do not have an element. New article on the prerequisites, and why no qualification route can be chosen before the element exists.

9 minSep 2, 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

System levelSafety Element out of Context (SEooC)Learn how to develop reusable safety elements with documented assumptions and guaranteed safety capability. Covers assumption management, integration constraints, safety manuals, and supplier-integrator collaboration workflows.Expert plan pricing
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
SoftwareLinux and Open-Source SafetyBuilding an ISO 26262 safety case for software nobody developed for you: pin down the exact kernel as an element, choose between qualification, proven-in-use and ISO PAS 8926, and guard Linux with external safety mechanisms.Expert plan pricing13 chapters