Dan C. Boger
Abstract
This paper discusses and analyzes approaches to the problem of software quality assurance. The approaches offered in the literature usually focus on "designing in" quality. This can be a productive approach, but there are also benefits to be gained by establishing an independent quality assurance (QA) group to review all aspects of the software development process. This paper discusses the organization of such a group using the function of an operations auditing group as a model.
- Baker, F. T., "System quality through structured programming", Proceedings of the 1972 FJCC, 41, 1, AFIPS Press, Montvale, NJ, 1972.Google Scholar
Digital Library
- Brooks, Fredrick P., The Mythical Man-Month, Addison-Wesley Publishing Co., Inc., Reading, Mass., 1975. Google ScholarDigital Library
- Conroy, James, Fuqua, Michael and Sisco, Julius, A Survey of Software Quality Assurance Methods and an Evaluation of Software Quality Assurance at Fleet Material Support Office, Master's Thesis at the Naval Postgraduate School, Administrative Sciences Department, December 1982.Google Scholar
- Cooper, John D. and Fisher, Matthew J. (eds.), Software Quality Management, Petrocelli Books, Inc., 1979. Google ScholarDigital Library
- Daly, Edmund B., "Organizing for Successful Software Development," Datamation, 25, 14, (1979), 106--120.Google Scholar
- Quality Assurance, Department of Defense Directive 4155.1 (1972), Enclosure 2.Google Scholar
- Gustafson, G. G. and Kerr, Roberta J., "Some Practical Experience with a Software Quality Assurance Program", Communications of the Association for Computing Machinery, 25, 1, (1982), 4--12. Google ScholarDigital Library
- Herbert, Leo, Auditing the Performance of Management, Lifetime Learning Publications, Belmont, CA, 1979.Google Scholar
- Jensen, Randall W. and Tonies, Charles C., Software Engineering, Prentice-Hall, Inc., Englewood Cliffs, NJ, 1979.Google Scholar
- Jones, Capers, "Program Quality and Programmer Productivity", IBM Technical Report TR 02.764, pp i, 42--78, also pp. 124--161 in Jones, Programming Productivity: Issues for the Eighties. Google ScholarDigital Library
- Jones, Capers, "Measuring Programming Quality and Productivity", IBM Systems Journal, 17, 1, (1978), 39--63, also pp. 9--33 in Jones, Programming Productivity: Issues for the Eighties. Google ScholarDigital Library
- Jones, Capers (ed.), Programming Productivity: Issues for the Eighties, IEEE Catalog No. EHO 186--7, IEEE Computer Society, P.O. Box 80452, Los Angeles, California 1981. Google ScholarDigital Library
- Lewis, Robert O., "Software Verification and Validation", Chapter 15 in Cooper, John D. and Fisher, Matthew J. (eds.), Software Quality Management, Petrocelli Books, Inc. 1979.Google Scholar
- Mair, William C., Wood, Donald R., and Davis, Keagle W., Computer Control and Audit, The Institute of Internal Auditors, 249 Maitland Ave., Altamonte Springs, Florida, 1978.Google Scholar
- McCall, James A., "An Introduction to Software Quality Metrics", Chapter 8 in Cooper, John D. and Fisher, Matthew J. (eds.), Software Quality Management, Petrocelli Books, Inc., 1979.Google Scholar
- Metzger, Phillip, Managing a Programming Project, Prentice-Hall, Inc., Englewood Cliffs, NJ, 1973. Google ScholarDigital Library
- Miller, Edward and Howden, William E., (eds.), Software Testing and Validation Techniques, IEEE Computer Society Press, IEEE Catalog No. EHO 180-0, IEEE Computer Society, 10662 Los Vaqueros Circle, Los Alamitos, CA 90720, 1981.Google Scholar
- Meyers, G. J., Software Reliability, John Wiley and Sons, Inc., New York, 1976. Google ScholarDigital Library
- Meyers, G. J., The Art of Software Testing, John Wiley and Sons, Inc., New York. 1979. Google ScholarDigital Library
- Reifer, D. J., and Trattner, S., "A Glossary of Software Tools and Techniques", pp. 344--352 in Jones, Programming Productivity: Issues for the Eighties.Google Scholar
- Reifer, D. J., "Software Quality Assurance Tools and Techniques", Chapter 14 in Cooper, John D. and Fisher, Matthew J., (eds.), Software Quality Management, Petrocelli Books, Inc., 1979.Google Scholar
- Scantlebury, D. L. and Raaum, Ronell B., Operational Auditing, AGA Monograph Series, Number one, Association of Government Accountants, 727 South 23rd Street, Arlington, Virginia, 1978.Google Scholar
- Shneiderman, Ben, Software Psychology, Winthrop Publishers, Inc., Cambridge, Mass., 1980.Google Scholar
- Thayer, R. H., Pyster, A. B., and Wood, R. C., "Major Issues in Software Engineering Project Management", IEEE Transactions on Software Engineering, SE-7, 4, (1981), 333--342.Google ScholarDigital Library
- Walters, Gene F., "Application of Metrics to a Software Quality Management (QM) Program", Chapter 9 in Cooper, John D. and Fisher, Matthew J. (eds.), Software Quality Management, Petrocelli Books, Inc., 1979.Google Scholar
- Yourdon, Edward, Managing the Structured Techniques, Second Edition, Prentice-Hall, Englewood Cliffs, New Jersey, 1979. Google ScholarDigital Library
Index Terms
- The organization of the software quality assurance process
Recommendations
State of the art in software quality assurance
The authors present a summary of their understanding of the publications that appeared in the computing literature during the last five-year period, with the word quality as part of their title and dealing with some or other aspects of software quality ...
Software Quality Assurance
This paper describes the status of software quality assurance as a relatively new and autonomous field. The history of its development from hardware quality assurance programs is discussed, current methods are reviewed, and future directions are ...
Information and Quality Assurance: An Unsolved, Perpetual Problem for Past and Future Generations
Quality assurance is well understood in the hardware/manufacturing community but not necessarily within the software community. The meaning of Information assurance depends on who you ask; those in the computer security field interpret information ...
Comments