ACM Home Page
Please provide us with feedback. Feedback
Some factors affecting program repair maintenance: an empirical study
Full text PdfPdf (820 KB)
Source
Communications of the ACM archive
Volume 26 ,  Issue 2  (February 1983) table of contents
Pages: 128 - 134  
Year of Publication: 1983
ISSN:0001-0782
Authors
Iris Vessey  Univ. of Queensland, St. Lucia, Queensland, Australia
Ron Weber  Univ. of Queensland, St. Lucia, Queensland, Australia
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 9,   Downloads (12 Months): 46,   Citation Count: 17
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/358024.358057
What is a DOI?

ABSTRACT

An empirical study of 447 operational commercial and clerical Cobol programs in one Australian organization and two U.S. organizations was carried out to determine whether program complexity, programming style, programmer quality, and the number of times a program was released affected program repair maintenance. In the Australian organization only program complexity and programming style were statistically significant. In the two U.S. organizations only the number of times a program was released was statistically significant. For all organizations repair maintenance constituted a minor problem: over 90 percent of the programs studied had undergone less than three repair maintenance activities during their lifetime.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Boehm, B.W. Software and its impact: A quantitative assessment. Datamation 19, 5 (May 1973), 48-59.
 
2
Buckley, W. Sociology and Modern Systems Theory. Prentice-Hall, Englewood Cliffs, N.J., 1967.
 
3
Canning, R.G. Modular COBOL programming. EDP Analyzer 10, 7 (July 1972), 1-14.
 
4
Canning, R.G. That maintenance "iceberg." EDP Analyzer 10, 10 (Oct. 1972), 1-14.
 
5
Curtis, B., Sheppard, S.B., Milliman, P., Burst, M.A., and Love T. Measuring the psychological complexity of software maintenance tasks with the Halstead and McCabe metrics. IRER Transactions on Software Engineering SE-5, 2 (March 1979), 96-104.
 
6
7
 
8
Endres, A. An analysis of errors and their causes in systems programs. IEEE Transactions on Software Engineering SE1, 2 (June 1975), 140- 149.
 
9
10
11
12
 
13
 
14
McCabe, T.J. A complexity measure. IEER Transactions on Software Engineering SE2, 4 (Dec. 1976), 308-320.
15
 
16
Naftaly, S.M., Cohen, M.C., and Johnson, B.G. COBOL Support Packages: Programming and Productivity Aids. Wiley, New York, 1972.
 
17
Neter, J., and Wasserman, W. Applied Linear Statistical Models. Irwin, Homewood, Ill., 1974.
 
18
Sheppard, S.B., Curtis, B., Milliman, P., and Love, T. Modern coding practices and programmer performance. Computer 12, 12 (Dec. 1979), 41-49.
19
20
 
21
 
22
Thayer, T.A., Lipow, M., and Nelson, E.C. Software Reliability. North- Holland, Amsterdam, 1978.
 
23
 
24

CITED BY  17