In preparation
System Architectural Design and Safety Architecture
A list of technical safety requirements does not tell you what to build. This guide turns them into elements, boundaries and interfaces, allocates every requirement with a reason, and verifies the result before hardware exists.
This guide is still being written, so it is not in any subscription yet. Vote for its release: we count the votes when we choose what to release next, and we email you when it is published.
Continue with
Where this topic leads next.
- System levelThe Hardware-Software Interface (HSI)The HSI is the bilateral contract where ISO 26262 hardware and software meet. Learn to specify registers, allocate diagnostics, budget timing against the FTTI, and run joint reviews so safety mechanisms actually work at the boundary.
- System levelFreedom from Interference (FFI)Learn how to ensure elements of different ASILs do not interfere through temporal, spatial, and data partitioning. Covers MPUs, hypervisors, bus monitoring, multi-core strategies, and evidence generation for assessments.
- HardwareHardware Engineering in ISO 26262Learn the complete hardware development lifecycle per ISO 26262-5 from requirements through design and verification. Covers HSI specification, SPFM/LFM/PMHF achievement, dependent failure analysis, and ASIC/FPGA/PCB considerations.