Software Issues: Risks and Liabilities

  • Joseph Migga Kizza
Part of the Undergraduate Topics in Computer Science book series (UTICS)


In this chapter we focuses on the issues that arise out of the relationship between the developer and the buyer, including claims, user expectations, and the legal ramifications that may follow an unhealthy relationship. The discussion touches on standards, reliability, security, safety, quality of software, quality of service of software products, causes of software failures, developer and buyer protection, and techniques for improving software quality. Causes of software failures or poor performance of a software product are discussed attributing the causes to a variety of reasons but most notably human error, the nature of software itself, and the environment in which software is produced and used. Finally historic examples of software caused accidents are given including the Therac–25, the Space Shuttle Challenger, the Indian Bhopal chemical accident and the Chernobyl Nuclear Power accident. Both consumer protection and techniques for improving software quality are also discussed.


Software Quality Strict Liability Software Producer Product Liability Solid Rocket Motor 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    Hamlet R (1988) Special section on software testing. Commun ACM 31(6):662–667CrossRefGoogle Scholar
  2. 2.
    Parnas D, van Schouwen J, Kwan S (1990) Evolution of safety-critical software. Commun ACM 33(6):636–648CrossRefGoogle Scholar
  3. 3.
    Taylor J (1994) America’s loneliest airport: Denver’s dreams can’t fly. Kansas City Star, 25 August, 1994. NewsBank, Transportation, fiche 43, grids D12–14Google Scholar
  4. 4.
    Neumann P (1995) Computer-related risks. ACM Press, New YorkGoogle Scholar
  5. 5.
    Neumann P (1993) The role of software engineering. Commun ACM 36(5):114CrossRefGoogle Scholar
  6. 6.
    Ahl DL (1985) Employee computer crime on the rise. Creat Comput 11(6):6, Washington, DCGoogle Scholar
  7. 7.
    Leveson N (1995) Safeware: system safety and computers. Addison-Wesley, ReadingGoogle Scholar
  8. 8.
    Littlewood B, Strigini L (1993) Validation of ultrahigh dependability for software-based systems. Commun ACM 36(11):69–80CrossRefGoogle Scholar
  9. 9.
    Ritchie D (1984) Reflections on trusting trust. Commun ACM 27(8):761–763CrossRefGoogle Scholar
  10. 10.
    Haag S, Raju MK, Schkade LL (1996) Quality function deployment usage in software development. Commun ACM 39(1):41–49CrossRefGoogle Scholar
  11. 11.
    Boehm BW (1989) Software risk management: principles and practices. IEEE Computer Society Press, New YorkCrossRefGoogle Scholar
  12. 12.
  13. 13.
    Fitzgerald K (1990) Whistle-blowing: not always a losing game. IEEE Spectr 26(6):49–52CrossRefGoogle Scholar
  14. 14.
    Nuclear accidents. Swedish Nuclear Power Generation.
  15. 15.
    Young S. Netscape bug uncovered. CNNfn, 12 June.–pkg/
  16. 16.
    Computer stock tumble over chip flow. New York Times, 4 December, 1994, section DGoogle Scholar
  17. 17.
    Johnson D (1994) Computer ethics, 2nd edn. Prentice Hall, Englewood Cliffs, p 134Google Scholar
  18. 18.
    Prince J (1980) Negligence: liability for defective software. Okla Law Rev 33:848–855Google Scholar
  19. 19.
    Neitzke F (1984) A software law primer. Reinhold, New YorkGoogle Scholar
  20. 20.
    Linger C, Mills HD, Witts B (1979) Structured programming: theory and practice. Addison-Wesley, ReadingzbMATHGoogle Scholar
  21. 21.
    Knight J, Mayers A (1994) An improved inspection technique. Commun ACM 36(11):51–61CrossRefGoogle Scholar

Further Reading

  1. Banker R, Datar S, Kemerer C, Zeneig D (1993) Software complexity and maintenance costs. Commun ACM 36(11):81–94CrossRefGoogle Scholar
  2. Fetzer J (1988) Program verification: the very idea. Commun ACM 31(9):1048–1063CrossRefGoogle Scholar
  3. Gelperin D, Hetzel B (1988) The growth of software testing. Commun ACM 31(6):687–690CrossRefGoogle Scholar
  4. Grady R (1993) Practical results from measuring software quality. Commun ACM 36(11):50–61CrossRefGoogle Scholar
  5. Laprie J-C, Littlewood B (1992) Probablistic assessment of safety-critical software: why and how? Commun ACM 35(2):13–21CrossRefGoogle Scholar
  6. Leveson N (1991) Software safety in embedded computer systems. Commun ACM 34(2):34–46CrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  • Joseph Migga Kizza
    • 1
  1. 1.Department of Computer ScienceUniversity of TennesseeChattanoogaUSA

Personalised recommendations