[SystemSafety] A Fire Code for Software?

WALTER, Dariusz dariusz.walter at baesystems.com
Sun Mar 18 23:06:45 CET 2018


Martyn, et. al.

Can you point me to some examples of what you think a good SFAIRP argument (or equivalent for not UK folks) looks like? (Doesn’t have to be software based, but that would be ideal)

Also, if anyone has some examples of how SFAIRP arguments were challenged in court, I would greatly appreciate the links.

Best wishes,
Dariusz

From: systemsafety [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf Of Martyn Thomas
Sent: Monday, 19 March 2018 3:15 AM
To: systemsafety at lists.techfak.uni-bielefeld.de
Subject: Re: [SystemSafety] A Fire Code for Software?

… SFAIRP has been legally defined to mean
… I doubt that many developers of safety-related systems would be able to pass that test. Notice that the burden of proof rests on the party seeking to rely on the claim that the risks have been reduced SFAIRP.

… It is a criminal offence to breach HSWA 1974 and the sentencing guidelines for convictions under HSWA 1974 were revised a couple of years ago. In several cases last year the duty holder was fined more than £1m and in a few cases the duty holder was sent to prison.

Martyn



This email has been sent on behalf of one of the following companies within the BAE Systems Australia group of companies:

    BAE Systems Australia Limited - Australian Company Number 008 423 005
    BAE Systems Australia Defence Pty Limited - Australian Company Number 006 870 846
    BAE Systems Australia Logistics Pty Limited - Australian Company Number 086 228 864

Our registered office is Evans Building, Taranaki Road, Edinburgh Parks,
Edinburgh, South Australia, 5111. If the identity of the sending company is
not clear from the content of this email please contact the sender.

This email and any attachments may contain confidential and legally
privileged information.  If you are not the intended recipient, do not copy or
disclose its content, but please reply to this email immediately and highlight
the error to the sender and then immediately delete the message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20180318/300d0e5a/attachment.html>


More information about the systemsafety mailing list