Recommended Article: How to derive Software Safety Requirements from Technical Safety Requirements
top of page

Recommended Article: How to derive Software Safety Requirements from Technical Safety Requirements

Writer: AutoEconnect SessionsAutoEconnect Sessions

Updated: Mar 19, 2022

We recently conducted a training on Functional Safety Software. We started to discuss Software Safety requirements (SSRs), stating something like “SSRs are derived from the Technical Safety requirements (TSRs). Start by looking into those requirements in TSR that are assigned to SW”. Immediately, one of the trainees asked “oh, all we need to do is to filter out the TSRs for SW, and put them into a new document, name this document as SSR and that’s it we are done?” No marks for guessing that we shouted a loud and clear “NOOOO!!!”

This is the subject of this blog. Once you have the TSR, how should you derive the SSR? We will tell you the actionable steps that you can take and also give you an example of how we have derived SSRs from TSRs. Read the complete article here


CONTACTUS

AutoEConnect Limited

Tel. +44-750 819 6789

 1 Parker Close, Rugby
Warwickshire, United Kingdom

CV21 1NY

Social Media Links
  • LinkedIn
  • Facebook
  • YouTube

TELLUS

AutoEConnect.com: Suggestions & Feedbacks help us stay motivated and to do better. We would love to hear from you.

AutoEConnect Limited: For collaborations or enquiries on our services, please connect with us using the form below.

 

Thanks for contacting us. We will get back to you shortly!

©2025  AutoEConnect.com

bottom of page