[SystemSafety] Software Safety Assessment

[Andreoli, Kevin (UK)]

My modified answers:


1.       No - you would have to question any attempt to use an obsolete standard on new product. (Whatever the product is.  Would you access a new car on the standards applicable in 2005?)

2.       Not necessarily, but a re-assessment should surely be done if it is known that the previous assessment may be inadequate.  In long-lived products which have safety considerations I would expect a periodic re-assessment anyway.

3.       No - if the checklist is known to be inadequate it would not be defensible to use it.

Kevin

From: systemsafety-bounces at lists.techfak.uni-bielefeld.de [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf Of Carl Sandom
Sent: 08 July 2015 13:36
To: systemsafety at lists.techfak.uni-bielefeld.de
Subject: Re: [SystemSafety] Software Safety Assessment
It's complicated and I was trying to avoid too much detail to get to the central questions.

It has been 'fielded' and is being 'used' during extended V&V activities (in parallel with the old system) but it is not yet considered fully operational. Safety assessment of some software aspects continues on Program A but not the 'process-based' software development assessment which was the subject of Standard X and the original checklist in 2004. For the scenario, take it as read that Standard X tools and techniques are still valid even though it is now obsolete.

My original questions slightly modified are:

1. Is it acceptable to use an obsolete (but still valid) safety standard to assess new software?

2. Is the SIL1 claim for 10 year old Project A invalid because the checklist could have been better?

3. If Project B used the old checklist from Project A would that be adequate?

Cheers
Carl
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20150708/760105a6/attachment.html>