Software Issues

  • Joseph Migga Kizza
Part of the Undergraduate Texts in Computer Science book series (UTCS)


Software are computer programs made up of a sequence of short commands called instructions that tell the computer what to do. Normally software is in two forms, either built into the computer’s more permanent memory, called ROM (read-only memory), or loaded on demand in less permanent but more volatile memory called RAM (random access memory). A software producer,or developer, creates or develops a set of programs to meet the specifications of either a user, if there is a contract, or of a specific problem if it is general software. Developers are either individuals working alone or companies like Microsoft, which employ hundreds of software engineers such as analysts and programmers. Software buyers, or customers, obtain the finished software from the developer to satisfy a need, basing their decision on developer claims. The buyer may be an individual or a company.


Consumer Protection Software Quality Total Quality Management Strict Liability Software Producer 
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.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Hamlet, Richard. “Special Section on Software Testing.” Communications of the ACM, 31 (6), 1988, pp. 662–667.CrossRefGoogle Scholar
  2. 2.
    Pamas, David, John van Schouwen, and Shu Kwan. “Evolution of Safety-Critical Software.” Communications of the ACM, 33 (6), 1990, pp. 636–648.CrossRefGoogle Scholar
  3. 3.
    Taylor, Jeff. “America’s Loneliest Airport: Denver’s Dreams Can’t Fly.” Kansas City Star, August 28, 1994. NewsBank, Transportation, 1994, fiche 43, grids D12–14.Google Scholar
  4. 4.
    Neumann, Peter. Computer Related Risks. New York: ACM Press, 1995.Google Scholar
  5. 5.
    Neumann, Peter. The Role of Software Engineering.“ Communications of the ACM,36(5), 1993, p. 114.Google Scholar
  6. 6.
    Davis, Ahl. “Employee Computer Crime on the Rise.” Creative Computing, June 1985, p. 6.Google Scholar
  7. 7.
    Leveson, Nancy. Safeware: System Safety and Computers. Reading, MA: Addison-Wesley, 1995.Google Scholar
  8. 8.
    Littlewood, Bev, and Lorenzo Strigini. “Validation of Ultrahigh Dependability for Software-Based Systems.” Communications of the ACM, 36 (11), 1993, pp. 69–80.CrossRefGoogle Scholar
  9. 9.
    Ritchie, Davis. “Reflections on Trusting Trust.” Communications of the ACM, 27 (8), 1984, pp. 761–763.CrossRefGoogle Scholar
  10. 10.
    Haag, Stephen, M.K. Raju, and L.L. Schkade. “Quality Function Deployment Usage in Software Development.” Communications of the ACM, 39 (1), 1996, pp. 41–49.CrossRefGoogle Scholar
  11. 11.
    Young, Steven. “Netscape Bug Uncovered,” CNNfn, June 12 Available:
  12. 12.
    Computer Stock Tumble over Chip Flow.“ New York Times, December 4, 1994, section D.Google Scholar
  13. 13.
    Prince, Jim. “Negligence: Liability for Defective Software.” Oklahoma Law Review 33, 1980, pp. 848–855.Google Scholar
  14. 14.
    Johnson, Deborah. Computer Ethics ( 2nd ed. ). Englewood Cliffs, NJ: Prentice Hall, 1994, p. 134.Google Scholar
  15. 15.
    Neitzke, Frederick. A Software Law Primer. New York: Van Nostrand Reinhold, 1984.Google Scholar
  16. 16.
    Linger, C., H.D. Mills, and B. Witts. Structured Programming: Theory and Practice. Reading, MA: Addison-Wesley, 1979.zbMATHGoogle Scholar
  17. 17.
    Knight, Jack, and Ann Mayers. “An Improved Inspection Technique.” Communications of the ACM 36 (11), 1994, pp. 51–61.CrossRefGoogle Scholar

Further Reading

  1. Banker, Rajiv, Srikant Datar, Chris Kemerer, and Dani Zeneig. “Software Complexity and Maintenance Costs.” Communications of the ACM 36(11), 1993, pp. 81–94.Google Scholar
  2. Fetzer, James. “Program Verification: The Very Idea.” Communications of the ACM 31(9), 1988, pp. 1048–1063.Google Scholar
  3. Gelperin, David, and Bill Hetzel. “The Growth of Software Testing.” Communications of the ACM 31(6), 1988, pp. 687–690.Google Scholar
  4. Grady, Roberts. “Practical Results from Measuring Software Quality.” Communications of the ACM. 36(11), 1993, pp. 50–61.Google Scholar
  5. Laprie, Jean-Claude, and Bev Littlewood. “Probablistic Assessment of Safety-Critical Software: Why and How?” Communications of the ACM 35(2), 1992, pp. 13–21.Google Scholar
  6. Leveson, Nancy. “Software Safety in Embedded Computer Systems.” Communications of the ACM 34(2), 1991, pp. 34–46.Google Scholar

Copyright information

© Springer Science+Business Media New York 1998

Authors and Affiliations

  • Joseph Migga Kizza
    • 1
  1. 1.Department of Computer Science and Electrical EngineeringUniversity of Tennessee at ChattanoogaChattanoogaUSA

Personalised recommendations