[SystemSafety] Component Reliability and System Safety

[SPRIGGS, John J]

In my bit of the industry, there is much less obligation to use specific standards than there is in some others.  If I were using a standard, or following guidance, and wish to use evidence of the activities to support a safety claim, I would also need to justify why use of that standard or guidance is appropriate in the context.

So, if you think MISRA C is relevant, and you are using it to support assurance claims, justify this use to your assurees.  If you do not think it relevant, do not use it.


John

-----Original Message-----
From: systemsafety [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf Of Derek M Jones
Sent: 14 September 2018 15:16
To: systemsafety at lists.techfak.uni-bielefeld.de
Subject: Re: [SystemSafety] Component Reliability and System Safety

Paul,

>>>> [Paul Sherwood, I think] Why is MISRA C still considered relevant 
>>>> to system safety in 2018?
>>
>> (Banal question? Banal answer!)
> 
> I'm sorry you consider my question banal. I mentioned your comment to 
> an

I would have said it was a blinkered question.

There is no one solution to building safe systems.  Lots of things have to be done.

-- 
Derek M. Jones           Software analysis
tel: +44 (0)1252 520667  blog:shape-of-code.coding-guidelines.com
_______________________________________________
The System Safety Mailing List
systemsafety at TechFak.Uni-Bielefeld.DE

***************************************************************************
If you are not the intended recipient, please notify our Help Desk at Email information.solutions at nats.co.uk
immediately. You should not copy or use this email or attachment(s) for any purpose nor disclose
their contents to any other person.

NATS computer systems may be monitored and communications carried on them recorded, to 
secure the effective operation of the system.

Please note that neither NATS nor the sender accepts any responsibility for viruses or any losses
caused as a result of viruses and it is your responsibility to scan or otherwise check this email
and any attachments.

NATS means NATS (En Route) plc (company number: 4129273), NATS (Services) Ltd 
(company number 4129270), NATSNAV Ltd (company number: 4164590) 
or NATS Ltd (company number 3155567) or NATS Holdings Ltd (company number 4138218). 
All companies are registered in England and their registered office is at 4000 Parkway, 
Whiteley, Fareham, Hampshire, PO15 7FL.

***************************************************************************