NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/software/4356

Text File | 1992-11-17 | 1.6 KB | 39 lines

Newsgroups: comp.software-eng
Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!saimiri.primate.wisc.edu!caen!batcomputer!rpi!newsserver.pixel.kodak.com!kodak!clpd.kodak.com!jimminy!figueroa
From: [e-mail] (Janet Figueroa (x37973))
Subject: Software Reliability - how to calculate?
Message-ID: <[e-mail]>
Followup-To: comp.software-eng
Summary: Require reference for software reliability calculation
Keywords: software reliability reference calculation
Sender: [e-mail]
Nntp-Posting-Host: jimminy
Reply-To: [e-mail]
Organization: Clinical Diagnostics Division, Eastman Kodak Company
Distribution: na
Date: Tue, 17 Nov 1992 18:21:19 GMT
Lines: 22


I just had an interesting discussion with a peer who is an electrical engineer.
It was about our reliability budget in which we have set a goal of a certain
number of service calls per year upon the introduction of the instrument.
She asked if there was a methodology followed in calculating relaibility for
software.  One of the examples we were discussing was code that resides in
a PROM.  If there was an error in the software and our service representative
will have to replace the PROM, how would that be looked at?

I told her point blank that I was not aware of any process used to
calculate software reliability.  Is there one?  I would be very
interested to know how the reliability is measured in an application
programming environment as compared to how it is determined for a
device driver, for example.

Any insights would be appreciated.  Thank you very much

Janet C. Figueroa
[e-mail]