Hi,

Functional safety is a complex topic with multiple different standards 
depending upon what you are creating. In essence the needed measures are 
depending upon how likely someone is to get hurt when something goes wrong. The 
need depends upon what is done and typically there are multiple ways to achieve 
what is needed.

Here is a few years old presentation on the topic: https://youtu.be/AaU0OcOKlFk

In the Qt website there is also further info on the topic: 
https://www.qt.io/product/functional-safety-and-qt

Yours,

                Tuukka

From: Interest <interest-boun...@qt-project.org> on behalf of Benjamin TERRIER 
<b.terr...@gmail.com>
Date: Monday, 3. May 2021 at 19.22
To: eric.fedosej...@gmail.com <eric.fedosej...@gmail.com>
Cc: Qt Interest <interest@qt-project.org>
Subject: Re: [Interest] L Word

Le lun. 3 mai 2021 à 18:03, 
<eric.fedosej...@gmail.com<mailto:eric.fedosej...@gmail.com>> a écrit :
So basically open source/standard Qt was considered appropriate for safety 
critical devices prior to the introduction of Safe Renderer in 2017, but now 
only commercial Qt with Safe Renderer is appropriate for that purpose.

Before anyone says otherwise, Qt was widely used in safety critical 
applications before Safe Renderer existed. See for example the text from 
introductory blog post about Safe Renderer:
“Industries such as automotive, medical and industrial automation, where Qt is 
the leading UI framework, can now satisfy safety critical requirements with Qt 
easier than before.”

Qt never came with functional safety guarantee, so if you want to use Qt for 
that you have to audit and certify a specific Qt version (or whatever the 
regulator asks you to do). That's what had to be done before the introduction 
of Qt Safe Renderer, and that is something you can still do.

As the blog post says, the Qt Safe Renderer make it easier to use Qt in 
functional safety products because you only need to have the Qt Safe Renderer 
audited/certified an possibly it is something that TQC already does, removing 
the burden from its clients.
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Reply via email to