Automotive functional safety ISO26262

In the amazing book “ Rework ”, the authors bring up the concept of ‘ Focus on what won’t change ’. This particular concept resonates with us as this is exactly what we emphasize when we consult our clients. When we work on functional safety with our clients, we go back to basics of software engineering and help the client understand the basics better. Even as our clients use AI tools for coding and producing other work products, we keep emphasising the core aspects of SW development. To that end, we created a presentation on SW development principles and did a training for one of our clients; check the slides below.  

If you have heard about Safety manuals but have not read one, or if you have read a Safety manual, tried to apply it and found it very challenging, this article is for you. In this blog, we talk about: Who needs a Safety manual? What is a Safety manual and what does it describe? Best Practices when working with Safety manuals Interestingly, ISO26262 never mentions “Safety manual” except in Part 11 for Semi-conductors, though its parent IEC 61508 describes the role of Safety manuals. Refer this article . Who needs a Safety manual? Let us assume that you are a Safety Manager or a Systems/Software/Hardware architect involved in the start of an Autonomous driving solution and the Safety goals of the program are at ASIL D.   Your technical sales team has already shortlisted two Microcontrollers that are at ASIL D, and now you are asked to evaluate both from a Safety perspective. Your first stop for information is the Safety manual of these Micros. You look through the Safety manua...