ISO 26262 and Automotive SPICE
Automotive SPICE asks whether your engineering is under control; ISO 26262 asks whether the product is safe. Run them as one engineering flow with one V-model, one trace backbone and one set of work products, with safety attributes on top.
- Chapters
- 12
- Chapters
- Figures and interactive visuals
- 8
- Figures and interactive visuals
- Integrated V worked thread
- 1
- Integrated V worked thread
Quick answers
- What is Automotive SPICE and how does it relate to ISO 26262?
- Automotive SPICE (ASPICE) is a process assessment model maintained by the VDA QMC, rooted in ISO/IEC 15504 and the ISO/IEC 330xx family. It measures whether engineering processes are under control, rated on a capability scale from level 0 to 5. ISO 26262 asks a different question: whether the product is functionally safe, with rigor scaled by ASIL. They are two lenses on one engineering flow. Both follow the same V-model, both demand bidirectional traceability, and most work products can be shared, with safety attributes such as the ASIL carried on the common artifacts.
- Does ASPICE capability level 3 mean a product is safe?
- No. A capability level measures how well a process is managed and established, not whether the product achieves its safety goals. A team can run the software processes at level 3 and still ship a design that violates a safety goal, because ASPICE does not look at HARA quality, ASIL-dependent method rigor, hardware metrics or confirmation measures. ISO 26262 adds those safety-specific demands on top of a controlled process. A joint assessment can share interviews and evidence, but the capability rating and the safety judgement are issued separately.
Why it pays for itself
Decode a dual-standard statement of work
Read an OEM requirement that asks for an ASPICE capability level and ISO 26262 compliance in one sentence, and know which demands are process, which are safety, and where one artifact satisfies both.
Overlay the two V-models node for node
Map the SYS and SWE processes onto their Part 4 and Part 6 counterparts, so one work breakdown and one verification plan serve the assessor and the safety auditor alike.
Stop writing artifacts twice
Build one traceability backbone with an ASIL on every safety link and one safety-tagged documentation set, instead of parallel safety and quality specifications that drift apart.
What you’ll be able to do
Decode an OEM statement of work
Tell which demands in a dual-standard requirement are process, which are safety, and where one artifact serves both.
Overlay the two V-models
Map the SYS and SWE processes to their Part 4 and Part 6 counterparts and plan one set of verification.
Build one traceability backbone
Keep a single trace graph with a safety-relevant flag and an ASIL on every node.
Merge work products without duplication
Maintain one safety-tagged documentation set while keeping safety-only artifacts distinct.
Prepare a joint assessment
Pull evidence once for the assessor and the safety auditor while each verdict stays independent.
Chapter by chapter
- 01
Why Two Frameworks
See why ASPICE and ISO 26262 are two lenses on the same engineering and what running them as separate silos costs.
- Two lenses, one engineering
- Cost of silos
- Braided flow
- 02
What ASPICE Actually Is
Learn where Automotive SPICE comes from, how one process is described, and three things it is often mistaken for.
- Where it comes from
- Anatomy of one process
- What ASPICE is not
- 03
The Process Landscape
Walk the process groups and find out which processes an OEM actually puts into an assessment scope.
- Process groups
- Typical assessment scope
- Engineering processes
- 04
The Capability Dimension
Understand the capability levels, how each process attribute is rated, and why OEMs usually ask for level 2 or 3.
- Six capability levels
- N, P, L, F ratings
- Why level 2 or 3
- 05
The Two V-Models Are One
Map the ASPICE system and software processes onto the ISO 26262 system and software clauses and see where the fit is only close.
- Node-for-node mapping
- Close but not identical
- Baselines as relations
- 06
Traceability, the Shared Backbone
Separate traceability from consistency and break a trace graph yourself to see what coverage metrics miss.
- Traceability versus consistency
- Break it yourself
- Four gaps both hunt
- 07
Mapping the Work Products
Keep one documentation set that answers both frameworks, with one requirement record projected into two views.
- One documentation set
- Requirement record projection
- Safety-only artifacts
- 08
Where Safety Extends the Process
See how the ASIL method tables raise rigor on shared activities and which work is safety-only territory.
- ASIL method tables
- Safety-only territory
- Coverage criteria compared
- 09
Supporting and Management Processes
Map the supporting and management processes to ISO 26262 and avoid the two mappings that regularly cost teams findings.
- Where the mapping is clean
- Two costly traps
- Configuration and change
- 10
Running a Joint Assessment
Plan a capability assessment and the confirmation measures against one evidence set while keeping two separate verdicts.
- Two verdicts
- Three confirmation measures
- One evidence set
- 11
An Integration Blueprint
Assemble the building blocks of an integrated program and follow one safety requirement down and back up the integrated V.
- Seven building blocks
- One requirement down the V
- Pedal plausibility monitor
- 12
Pitfalls and Myths
Replace common myths about combining the frameworks and check readiness before a joint assessment.
- Six myths replaced
- Readiness checklist
- Common misreadings
Read all 12 chapters with Expert.
Start with a free account: the complete Functional Safety Concept guide and 5 practice exams a month, then upgrade when you need this guide.
Expert plan pricingNot just text: the visual toolkit
Braided frameworks
ASPICE and ISO 26262 shown as two strands braiding into one engineering flow.
Capability roll-up
The level rule evaluated live over the process attributes.
Trace graph pathology
A trace graph that passes coverage and still fails consistency.
Requirement record projection
One requirements record queried as an SWE.1 view and as a safety view.
Pedal plausibility monitor
An integrated V thread bound to the physical features of a simplified monitor.
One ASIL D requirement down the integrated V
A simplified E-Gas style safety goal is followed through the integrated flow, showing how each node answers an ASPICE process and an ISO 26262 clause with the same artifact.
- Safety goal and its ASIL from the concept phase
- System requirement for redundant pedal sensing
- Software requirement and architecture for a plausibility monitor
- Unit verification with structural coverage
- System integration and vehicle-level validation
Unlock in course
Who this guide is for
- Suppliers whose OEM contract demands ASPICE CL 2 or CL 3 plus ISO 26262 compliance
- Safety managers merging a separate safety program and quality program into one flow
- Process and quality engineers preparing for a joint capability assessment and safety audit
- Engineers unsure where MAN.5 risk management ends and HARA begins
Frequently Asked Questions
Common questions about ISO 26262 and Automotive SPICE
Start the course today
A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov and RBD simulators, and 5 practice exams per month. The Pro and Expert plans unlock more of the 93-guide library. No credit card required.
Continue with
Where this topic leads next.
- 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 qualification methods, practical guidelines, and worked examples for common toolchains.
- 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.
- Safety analysesSafety AnalysesLearn how HARA, FMEA, FTA, STPA, DFA, and HAZOP complement each other across the ISO 26262 lifecycle. Covers method selection criteria, analysis sequencing, and a guide to choosing the right technique for each risk.