Why Software Systems Fail
<b>1.0 Introduction</b><br>In this report I will be concentrating on the failure of software systems. To understand why software systems fail we need to understand what are software systems. Software systems are a type of information system. This is because a software system is basically a means for hardware to process information. Flynn 's definition of an information system is:<br><br>"An information system provides procedures to record and make available information, concerning part of an organization, to assist organization-related activities."<br><br>Humans have been processing information manually for thousands of years, but with the vast increase of demand for knowledge this century has meant that a new method of information processing has been needed. Software systems have provided a new means that is much faster and efficient. As a result a huge number of organisations have become software dependent. Some of these systems are used to safeguard the lives of many people. This means that if these systems were to fail they could lead to devastating consequences. Here are some examples of where software systems are used heavily and could be very dangerous if they were to fail - aviation, hospitals, space exploration, nuclear power stations and communications. I will be looking at some examples of actual software failure in these fields to explain the reasons why systems fail.<br><br><b>2.0 Reasons for Systems Failure</b><br>If software systems failure can be so dangerous why can they not be completely eliminated? According to Parnas, "The main reason is that software can never be guaranteed to be 100% reliable. Software systems are discrete-state systems that do not have repetitive structures. The mathematical functions that describe the behaviour of software systems are not continuous, and traditional engineering mathematics do not help in their verification." In other words some software can be so large that thorough testing can be almost
Bibliography: /b><br><li>Flynn, Donal J.; "Information Systems Requirements: Determination and Analysis"; McGraw-Hill Book Company; 1992<br><li>Parnas; 1985; taken from: Sherer, Susan A.; "Software Failure Risk – Measurement and Management"; Plenum Press; 1992<br><li>Jones, Carpers; "Patterns of Software Systems Failure and Success"; Thomson computer press; 1996<br><li>Neumann, Peter G.; "Computer Related Risks"; Addison-Wesley publishing company; 1995<br><li>Petroski, Henry; "To Engineer is Human"; MacMillan Publishing; 1985<br><li>Flowers, Stephen; "Software failure: management failure"; Chichester: John Wiley and Sons; 1996.<br><li>Report of the Inquiry into the London Ambulance Service; February 1993. <br><li>Simpson, Moira (1994); "999!: My computers stopped breathing !"; The Computer Law and Security Report, 10; March – April; pp 76-81<br><li>Dr. Dobbs Journal; January 1997 edition<br><li><a href="http://catless.ncl.ac.uk/Risks">http://catless.ncl.ac.uk/Risks</a><br><li><a href="http://www.scit.wlv.ac.uk ">http://www.scit.wlv.ac.uk </a><br><li><a href="http://www.bbc.co.uk/news">http://www.bbc.co.uk/news</a><br><li><a href="http://abcnews.go.com/sections/travel">http://abcnews.go.com/sections/travel</a>