Software Component Qualification

Software component qualification, defined in ISO 26262-8 Clause 12, is the route for using existing software that was not developed in compliance with ISO 26262 - commercial libraries, AUTOSAR Basic Software, real-time operating systems - in safety-related applications. Instead of redeveloping the component to Part 6, you build a qualification argument from evidence about the component as it exists: its specification and safety context, analysis of its development history, field experience, and targeted verification. The output is an evidence package demonstrating the component behaves as required in its intended safety context, with assumptions verified at integration.

Direction of development. A Safety Element out of Context is developed according to ISO 26262 from the start, against assumed requirements and an assumed context - the integrator later validates those assumptions. Qualification is post-hoc: the component already exists, was built outside the standard, and you construct evidence that it is nonetheless fit for its safety context. SEooC gives stronger, cleaner arguments but requires the supplier to have followed the standard; qualification is the pragmatic route for the vast installed base of pre-existing code. The course opens with exactly this distinction and when each applies.

The course structures it as 3 evidence streams. Development history analysis evaluates the process maturity, defect history, code quality metrics, and change history behind the component. Field experience builds a statistical argument from deployment history - operational profile definition, failure rate estimation, and confidence intervals, with the fielded configuration matching the one you ship. Targeted testing fills the remaining gaps with requirement-based tests, fault injection, and structural coverage. Real qualifications combine streams, weighted by ASIL and by what evidence actually exists - the method applicability matrix in chapter 3 maps the choice.

For an RTOS: validate the exact OS configuration you deploy, analyze task scheduling behaviour, verify interrupt handling, and assess freedom-from-interference implications - a vendor safety manual helps but its assumptions of use still need validation in your context. For AUTOSAR BSW, the practical path runs through vendor qualification packages for the COM, memory, and diagnostic stacks, supplemented by your own analysis of the modules and configuration you actually use. Both get dedicated chapters, and the RTOS case runs as the course's worked example from safety context through evidence package.

The guide has 12 chapters: the Clause 12 framework, component taxonomy and method applicability, the qualification workflow, one chapter per evidence stream (development history, field experience, targeted testing), AUTOSAR BSW qualification, RTOS validation, documentation and evidence, integration context, and best practices. It includes 6 interactive tools such as the qualification method selector, the field experience calculator, and the evidence completeness matrix, with an RTOS worked example and an AUTOSAR BSW focus throughout. A free account starts you off, and the Pro and Expert plans unlock more of the library.