Re: [SystemSafety] Modelling and coding guidelines: "Unambiguous Graphical Representation"

From: Matthew Squair < >
Date: Thu, 17 Mar 2016 23:44:54 +1100

Strangely that COTS low number has been 'used in anger' on a project of mine. Any idea were it came from?

Matthew Squair

MIEAust, CPEng
Mob: +61 488770655
Email; Mattsquair_at_xxxxxx

> On 17 Mar 2016, at 9:23 PM, SPRIGGS, John J <John.SPRIGGS_at_xxxxxx >
> Peter wrote: "... let me refer you to the current edition of IEC 61508, Parts 2 and 3. The conditions on "proven in use" for SW are to my mind incoherent. "
> IEC61508 is not alone in being incoherent on this matter, EUROCAE Document ED-109 (RTCA/DO-278, if you prefer) sets assurance levels on the basis of the severity of the risk that is being mitigated but, in a note about using service history to support assurance for COTS and the like, it suggests a (low) numbers of failure-free hours that can be used to claim achievement of some assurance levels. But, surely, that is "likelihood", which should be orthogonal to severity.
> The newer version, ED-109A (RTCA/DO-278A) does not have this note, which may be why some have said that the COTS requirements are much more onerous than in the original...
> John
> -----Original Message-----
> From: systemsafety [mailto:systemsafety-bounces_at_xxxxxx > Sent: 16 March 2016 07:23
> To: Les Chambers; systemsafety_at_xxxxxx > Subject: Re: [SystemSafety] Modelling and coding guidelines: "Unambiguous Graphical Representation"
> ***************************************************************************
> If you are not the intended recipient, please notify our Help Desk at Email information.solutions_at_xxxxxx > 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.
> ***************************************************************************
> _______________________________________________
> The System Safety Mailing List
> systemsafety_at_xxxxxx

The System Safety Mailing List
systemsafety_at_xxxxxx Received on Thu Mar 17 2016 - 13:45:26 CET

This archive was generated by hypermail 2.3.0 : Tue Jun 04 2019 - 21:17:08 CEST