<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Roboto Light";
panose-1:2 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Roboto Light";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head><body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal" style="margin-top:6.0pt"><span style="font-family:"Roboto Light";color:#365F91;mso-fareast-language:EN-US">In my experience, if Software Reliability is mentioned at a conference, at least one member of the audience will laugh, and if it
is mentioned in a work discussion, at least one member of the group will get angry.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:6.0pt"><span style="font-family:"Roboto Light";color:#365F91;mso-fareast-language:EN-US">Interestingly, some of the same people who say it is impossible to quantify software failure rates will set numerical requirements
for Software Availability – if you get one of those, ask the Customer how (s)he wants you to demonstrate satisfaction of the requirement.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:6.0pt"><span style="font-family:"Roboto Light";color:#365F91;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-top:6.0pt"><span style="font-family:"Roboto Light";color:#365F91;mso-fareast-language:EN-US">John<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> systemsafety <systemsafety-bounces@lists.techfak.uni-bielefeld.de>
<b>On Behalf Of </b>Derek M Jones<br>
<b>Sent:</b> 14 September 2020 12:54<br>
<b>To:</b> systemsafety@lists.techfak.uni-bielefeld.de<br>
<b>Subject:</b> [SystemSafety] What do we know about software reliability?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All,<br>
<br>
What do we know about software reliability?<br>
<br>
The answer appears to be, not a lot:<br>
<a href="http://shape-of-code.coding-guidelines.com/2020/09/13/learning-useful-stuff-from-the-reliability-chapter-of-my-book">http://shape-of-code.coding-guidelines.com/2020/09/13/learning-useful-stuff-from-the-reliability-chapter-of-my-book/</a><br>
<br>
-- <br>
Derek M. Jones Evidence-based software engineering<br>
tel: +44 (0)1252 520667 blog:shape-of-code.coding-guidelines.com<br>
_______________________________________________<br>
The System Safety Mailing List<br>
<a href="mailto:systemsafety@TechFak.Uni-Bielefeld.DE">systemsafety@TechFak.Uni-Bielefeld.DE</a><br>
Manage your subscription: <a href="https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety">
https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety</a><o:p></o:p></p>
</div>
<br>
<br>
<hr width="100%">
<font face="Verdana" style="font-size: 9pt">If you are not the intended recipient, please notify our Help Desk at Email Information.Solutions@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.
<br>
<br>
NATS computer systems may be monitored and communications carried on them recorded, to
secure the effective operation of the system.
<br>
<br>
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.
<br>
<br>
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.</font>
<hr>
</body></html>