 |
Sunday, October 31, 1993 |
I ran across a report that may be of interest to RISKS readers. It is a SEI
report: Software Product Liability (CMU/SEI-93-TR-13) by Jody Armour (School
of Law, U. of Pittsburgh) and Watts S. Humphrey (SEI Fellow, Software
Engineering Institute). It is available (Postscript, but without figures) via
anonymous FTP from ftp.sei.cmu.edu in directory pub/documents/93.reports as
file tr13.93.ps. The abstract starts with a reference to an accident
involving a radiation machine [Therac 25], although it is not specifically
identified, is likely to be an accident already extensively discussed in
RISKS, so I have omitted it. The rest of the abstract follows:
Software defects are rarely lethal and the number of injuries
and deaths is now very small. Software, however, is now the
principle controlling element in many industrial and consumer
products. It is so pervasive that it is found in just about
every product that is labeled "electronic." Most companies
are in the software business whether they know it or not.
The question is whether their products could potentially
cause damage and what their exposures would be if they did.
While most executives are now concerned about product
liability, software introduces a new dimension. Software,
particularly poor quality software, can cause products to do
strange and even terrifying things. Software bugs are
erroneous instructions and, when computers encounter them,
they do precisely what the defects instruct. An error could
cause a 0 to be read as a 1, an up control to be shut down,
or, as with the radiation machine, a shield to be removed
instead of inserted. A software error could mean life or death. [youman@umiacs.UMD.EDU (Charles Youman) via risks-digest Volume 15, Issue 20]
1:50
#
G!
| |
Maximillian Dornseif, 2002.
|
|
|