[SystemSafety] New paper on MISRA C
Derek M Jones
derek at knosof.co.uk
Wed Sep 12 13:51:46 CEST 2018
Paul,
> As I understand it MIT and others have successfully debunked the notion
> that system safety is correlated with component reliability.
Can you point me at the references for this assertion?
Given enough redundancy you can build a system out of unreliable parts,
but some people prefer less redundancy+more reliable components.
> So a simple question, and sorry for being blunt...
>
> Why is MISRA C still considered relevant to system safety in 2018?
>
> br
> Paul
>
> On 2018-09-04 15:48, David Ward wrote:
>> Derek
>>
>> A further point of clarity here is that you are talking about MISRA C,
>> which MISRA was not "paid" to develop. This has always been a
>> voluntary effort.
>>
>> It is arguable whether a grant-funded project (where industrial
>> partners do not get full costs reimbursed) is being "paid" but I do
>> not want to open a debate on that ...
>>
>> David
>>
>> -----Original Message-----
>> From: systemsafety
>> [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf
>> Of Derek M Jones
>> Sent: 04 September 2018 15:32
>> To: systemsafety at lists.techfak.uni-bielefeld.de
>> Subject: Re: [SystemSafety] New paper on MISRA C
>>
>> David,
>>
>>> Once the grant-funded project was complete, some of the industrial
>>> partners elected to continue working together on a self-funded basis
>>> and one of the first outcomes of this was the publication of MISRA C.
>>> This arose from two automotive companies acknowledging it was better
>>> to have a single industry approach to a C subset than company
>>> specific guidelines.
>>
>> MISRA were paid to do some work, when it took off those involved were
>> flexible enough to find a way for the 'project' to continue.
>>
>> The success story of MISRA C is a result of the efforts of those
>> inside and outside to keep working over many years, on what senior
>> management probably regarded as an inefficient use of resources.
>>
>>
>> --
>> 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
>>
>> HORIBA MIRA Ltd
>>
>> Watling Street, Nuneaton, Warwickshire, CV10 0TU, England
>> Registered in England and Wales No. 9626352
>> VAT Registration GB 100 1464 84
>>
>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they
>> are addressed. If you are not the named addressee you should not
>> disseminate, distribute or copy this e-mail. Please notify the sender
>> immediately by e-mail if you have received this e-mail by mistake and
>> delete this e-mail from your system. If you are not the intended
>> recipient you are notified that disclosing, copying, distributing or
>> taking any action in reliance on the contents of this information is
>> strictly prohibited.
>> _______________________________________________
>> The System Safety Mailing List
>> systemsafety at TechFak.Uni-Bielefeld.DE
> _______________________________________________
> The System Safety Mailing List
> systemsafety at TechFak.Uni-Bielefeld.DE
>
--
Derek M. Jones Software analysis
tel: +44 (0)1252 520667 blog:shape-of-code.coding-guidelines.com
More information about the systemsafety
mailing list