[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
article
Free access

Determinants of program repair maintenance requirements

Published: 01 August 1984 Publication History

Abstract

Considerable resources are devoted to the maintenance of programs including that required to correct errors not discovered until after the programs are delivered to the user. A number of factors are believed to affect the occurrence of these errors, e.g., the complexity of the programs, the intensity with which programs are used, and the programming style. Several hundred programs making up a manufacturing support system are analyzed to study the relationships between the number of delivered errors and measures of the programs' size and complexity (particularly as measured by software science metrics), frequency of use, and age. Not surprisingly, program size is found to be the best predictor of repair maintenance requirements. Repair maintenance is more highly correlated with the number of lines of source code in the program than it is to software science metrics, which is surprising in light of previously reported results. Actual error rate is found to be much higher than that which would be predicted from program characteristics.

References

[1]
Akiyama, F. An example of software system debugging. Proceedings of the IFIPS Congress, 1971, 353-359.
[2]
Bell, D.E., and Sullivan, J,E. Further investigations into the complexity of software. MITRE Technical Report MTR 2874, vol. IL Bedford, Maine, 1974.
[3]
Bowen, J.B. Are current approaches sufficient for measuring software quality? Proc. Softw. Quality Assurance Workshop, 3, 5, 148-155.
[4]
Burch, J.G., Strater, F.R. and Grudnitski, G. Information Systems: Theory and Practice. New York: John Wiley and Sons, Inc., 1983.
[5]
Canning, R.G. Modular COBOL programming. EDP Anal. 10, 7 (July 1972). 1-14.
[6]
Canning, R.G. That maintenance "iceberg." EDP Anal. 10, 10 (Oct. 1972), 1-14.
[7]
Christensen, K., Fitsos, G.P., and Smith, C.P. A perspective on software science. IBM Syst. J. 20, 4 (1981), 372-387.
[8]
Curtis, B., Sheppard, S.B., Milliman, P., Borst, M.A., and Love, T. Measuring the psychological complexity of software maintenance tasks with the Halstead and McCabe metrics. IEEE Trans. Softw. Eng. SE-5, 2 (Mar. 1979), 96-104.
[9]
Elshoff, J.L. Measuring commercial PL/I programs using Halstead's criteria. SIGPLAN Not. (May 1976}, 38-46.
[10]
Endres, A. An analysis of errors and their causes in systems programs. IEEE Trans. Softw. Eng. SE-1, 2 (June 1975), 140-149.
[11]
Fitzsimmons, A. and Love, T. A review and evaluation of software science. Comput. Surv. 10, 1 (Mar. 1978), 3-18.
[12]
Funami, Y., and Halstead, M.H, A software physics analysis of Akiyama's debugging data. CSD-TR-144, Purdue University, Lafayette, Ind., May 1975.
[13]
Gilb, T. Software Metrics. Winthrop Publishers, Cambridge, Mass., 1977.
[14]
Halstead, MH. Elements of Software Science. Elsevier North-Holland, Inc., New York, 1977.
[15]
Lientz, B.P., and Swanson, E.B. Software Maintenance Management. Addison-Wesley Publ. Co. Inc., Reading, Mass., 1980.
[16]
Lientz, B,P., Swanson. E.B., and Tompkins, G.E. Characteristics of application software maintenance. Commun. ACM, 21, 6 (July 1978), 466-471.
[17]
Littlewood, B. How to measure software reliability and how not to. Proc. Third International Conf. Softw. Eng., Apr. 1978, 37-55.
[18]
McCabe, T.J. A complexity measure. IEEE Trans. Soft. Eng. SE-2, 4 (Dec. 1976), 308-320.
[19]
Moore, T.E. The Traveling Man. Doubleday & Co., Inc. Garden City, N.Y., 1972.
[20]
Musa, J,D. The use of software reliability measures in project management. Proceedings: COMPSAC '78, 493-498.
[21]
Ottenstein, L.M, Schneider, V.B., and Halstead, M.H. Predicting the number of bugs expected in a program module. CSD-TR-205, Purdue University, Lafayette, Ind., Oct. 1976.
[22]
Sheil, B.A. The psychological study of programming. ACM Comput. Surv. 13, 1 (Mar. 1981), 101-120.
[23]
Stevens, S.S. On the theory of scales of measurement. Science 103 (1946), 677-680.
[24]
Swanson, E.B. On the user-requisite variety of computer application software. IEEE Trans. Reliab. R-28, 3 (Aug. 1979), 221-226.
[25]
Swanson, E.B. The dimension of maintenance. Proc. Second International Con. Soflw. Eng., Oct. 1976, 492-497.
[26]
Thayer, T.A. et el., Software reliability study. RADC-TR-76-2238, Rome Air Development Center, Grifiss Air Force Base, N.Y., Aug. 1976,
[27]
Vessey, I., and Weber, R. Some factors affecting program repair maintenance. Commun. ACM 26, 2 (Feb. 1983), 128-134.

Cited By

View all
  • (2020)Immersive light field video with a layered mesh representationACM Transactions on Graphics10.1145/3386569.339248539:4(86:1-86:15)Online publication date: 12-Aug-2020
  • (2020)MEgATrackACM Transactions on Graphics10.1145/3386569.339245239:4(87:1-87:13)Online publication date: 12-Aug-2020
  • (2020)Variable-width contouring for additive manufacturingACM Transactions on Graphics10.1145/3386569.339244839:4(131:1-131:17)Online publication date: 12-Aug-2020
  • Show More Cited By

Recommendations

Reviews

Agnes Marguerite Decroix

The author presents his reflection on the number of delivered bugs in a software package out of a particular study he made (346 programs written in PL/1). The relation of number of buys with program size and complexity, usage and age, and code style is reviewed. The discrepancy between predicted and actual results leads to a few thoughts about the choice of data to be captured in a given context. This paper offers its contribution to the well-known questions: “How much bug is delivered__?__” and “What is the maintenance cost__?__” A suggestion for further studies is sketched since the results are unsatisfactory using actual methods. But not attempt is made to find out which of the parameters are misleading in one's computation.

Access critical reviews of Computing literature here

Become a reviewer for Computing Reviews.

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image Communications of the ACM
Communications of the ACM  Volume 27, Issue 8
Aug 1984
90 pages
ISSN:0001-0782
EISSN:1557-7317
DOI:10.1145/358198
Issue’s Table of Contents
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 August 1984
Published in CACM Volume 27, Issue 8

Permissions

Request permissions for this article.

Check for updates

Author Tags

  1. program complexity
  2. program maintenance
  3. repair maintenance
  4. software science

Qualifiers

  • Article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)72
  • Downloads (Last 6 weeks)13
Reflects downloads up to 19 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2020)Immersive light field video with a layered mesh representationACM Transactions on Graphics10.1145/3386569.339248539:4(86:1-86:15)Online publication date: 12-Aug-2020
  • (2020)MEgATrackACM Transactions on Graphics10.1145/3386569.339245239:4(87:1-87:13)Online publication date: 12-Aug-2020
  • (2020)Variable-width contouring for additive manufacturingACM Transactions on Graphics10.1145/3386569.339244839:4(131:1-131:17)Online publication date: 12-Aug-2020
  • (2020)Quad-mesh based isometric mappings and developable surfacesACM Transactions on Graphics10.1145/3386569.339243039:4(128:1-128:13)Online publication date: 12-Aug-2020
  • (2018)E-WOM’s Impact on App DevelopmentJournal of Computer Information Systems10.1080/08874417.2018.151728360:5(418-427)Online publication date: 14-Sep-2018
  • (2017)Plane Formation by Synchronous Mobile Robots in the Three-Dimensional Euclidean SpaceJournal of the ACM10.1145/306027264:3(1-43)Online publication date: 16-Jun-2017
  • (2015)The interplay among software volatility, complexity and development outcomesInternational Journal of Information Technology and Management10.1504/IJITM.2015.06846214:2/3(160-171)Online publication date: 1-Apr-2015
  • (2015)A New Approach to Incremental Cycle Detection and Related ProblemsACM Transactions on Algorithms10.1145/275655312:2(1-22)Online publication date: 8-Dec-2015
  • (2014)STRUCTURAL CHANGES ASSOCIATED WITH TEMPORAL DISPERSION IN SOFTWARE DEVELOPMENT TEAMS: EVIDENCE FROM OPEN SOURCE SOFTWARE PROJECT TEAMSInternational Journal of Innovation Management10.1142/S136391961450030318:05(1450030)Online publication date: Oct-2014
  • (2014)Structural Changes Associated with the Temporal Dispersion of TeamsProceedings of the 2014 47th Hawaii International Conference on System Sciences10.1109/HICSS.2014.45(300-309)Online publication date: 6-Jan-2014
  • Show More Cited By

View Options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Login options

Full Access

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media