In automotive software development, the functional safety (FuSa) audit plays a crucial role in the safety assessment of the system before it can be approved. It ensures the system being developed meets the Automotive Safety Integrity Level (ASIL) required by the ISO 26262 standard. The audit processes are typically conducted independently using discrete tools that haven’t been integrated into the software development/release pipeline, while the audit artefacts relevant to the software is often manually generated, which means they can be slow, and often become a cumbersome exercise carried out at the end of a development lifecycle.
Continuous compliance relevant to automotive is the process for continuous functional safety assessment of an automotive application to ensure that it always meets regulatory requirements and industry best practices. The Practice also helps streamline the audit process by keeping the development team up-to-date on your compliance requirements throughout the development cycle. Also, it reduces mean-time-to-recovery whenever there is non-compliance identified.
Speaker
Vignesh Radhakrishnan
Vignesh is a developer, with over 8 years of experience in building software for hardware for various industries including semi-conductor, automotive, etc. specialising in rapid-prototyping. As part of Thoughtworks SDV team, currently working on technologies of future to crack the complexities on various layers of the Software Defined Vehicle ecosystem.
Atri Sarkar
Atri Sarkar, a software engineer at Thoughtworks with a passion for systems programming, writing high performance code and a serious case of Rust love. During the day he leverages Rust to help build rock-solid software for the next generation of cars. By night, you’ll find him tinkering with game engines, microcontrollers, and audio programming. A firm believer in the power of open source, Atri tries to actively contributes to open source projects, fostering collaboration and knowledge sharing within the developer ecosystem.