System structure and software maintenance performance

Communications of the ACM

Volumn 32, Issue 3, 1989, Pages 347-358

  Gibson, Virginia R ^a   Senn, James A ^b  

^a UNIVERSITY OF MAINE   (United States)

^b GEORGIA STATE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER PROGRAMMING;

RIPPLE EFFECT ERRORS; SOFTWARE COMPLEXITY; SOFTWARE DEVELOPMENT MANAGEMENT; SOFTWARE METRICS;

COMPUTER SOFTWARE;

EID: 0024620293     PISSN: 00010782     EISSN: 15577317     Source Type: Journal    
DOI: 10.1145/62065.62073     Document Type: Article

References (52)

1. Agresti, W.W. Managing program maintenance, J. Syst. Manage. 33, 2 (Feb. 1982), 34-37.
2. Agresti, W.W. Measuring program maintainability. J. Syst. Manage. 33, 3 (Mar. 1982), 26-29.
3. Baroudi. J.J., and Ginzberg, M.J. impact of the technological environment on programmer/analyst job outcomes. Commun. ACM 29, 6 (June 1986), 546-555.
4. Basili, V.R. Tutorial on Models and Metrics for Software Management and Engineering. IEEE, New York, 1980.
5. Basili, V.R., and Reiter, R.W. Evaluating automatable measures of software development. In Workshop on Quantitative Software Models for Reliability, Complexity, and Cost. IEEE, New York, 1979, pp. 107-116.
6. Basili, V.R., Selby, R.W., and Hutchens, D.H. Experimentation in software engineering. IEEE Trans. Softw. Eng. 12, 7 (July 1986), 733-743.
7. Benyon-Tinker, G. Complexity measures in an evolving large system. In Workshop on Quantitative Software Models. IEEE, New York, 1979, pp. 117-127.
8. Berns, G.M. Assessing software maintainability. Commun. ACM 27, 1 (Jan. 1984), 14-24.
9. Boehm, B.W. Software engineering economics. IEEE Trans. Softw. Eng. 10, 1 (Jan. 1984), 4-21.
10. Bryan, W., and Siegel, S. Making software visible, operational, and maintainable in a small project environment. IEEE Trans. Softw. Eng. 10, 1 (Jan. 1984), 59-67.
11. Canning, R. Easing the software maintenance burden. EDP Analyzer 19, 8 (Aug. 1981) 1-13.
12. Chen, E.T. Program complexity and programmer productivity. IEEE Trans. Softw. Eng. 4, 3 (May 1978), 187-194.
13. Clapp, J.A. Designing software for maintainability. Computer Design 20, 9 (Sept. 1981) 197-202.
14. Curtis, B. et al. Measuring the psychological complexity of software maintenance tasks with the Halstead and McCabe metrics. IEEE Trans. Softw. Eng. 5, 2 (Mar. 1979), 96-104.
15. Curtis, B., Sheppard, S.B., and Milliman, P. Third time charm: Stronger prediction of programmer performance by software complexity metrics. In Proceedings of the 4th International Conference on Software Engineering. (Munich, Germany, Sept. 17-19, 1979), pp. 356-370.
16. Denning, P.J. Throwaway programs. Commun. ACM 24, 2 (Feb. 1981), 57-58.
17. Dijkstra, E.W. How do we tell truths that might hurt? SIGPLAN Notices 17, 5 (May 1982), 13-15.
18. Edwards, C. Information systems maintenance: An integrated perspective. MIS Quarterly 8, 4 (Dec. 1984), 237-256.
19. Elshoff, J.L., and Marcotty, M. Improving computer program readability to aid modification. Commun. ACM 25, 8 (Aug. 1982), 512-521.
20. Evans, M. Software engineering for the COBOL environment. Commun. ACM 25, 12 (Dec. 1982), 874-882.
21. Federal agencies’ maintenance of computer programs: Expensive and undermanaged, GAO Report to Congress AFMD-81-25, Feb. 26, 1981.
22. Gaffney, J.E., Jr. Program control complexity and productivity. In Workshop on Quan itative Software Models, IEEE, New York, 1979.
23. Gibson, V.R. A study of complexity metrics as surrogate measures of software maintainability. Ph.D. Dissertation. University Microfilms. 1986.
24. Glass, R.L., and Nciseux, R.A. Software maintenance guidebook. Prentice-Hall, Engewood Cliffs, NJ, 1981.
25. Gremillion, L.L. Determinants of program repair maintenance requirements. Commun. ACM 27, 8 (Aug. 1984), 826-832.
26. Guidance on software maintenance, National Bureau of Standards Publication no. 500-106, U.S. Government Printing Office, Washington, D.C., 1983.
27. Halstead, M.H. Elements of software science. Elsevier North-Holland, New York, 1977.
28. Harrison, W. Structured programming with COBOL. J. Syst. Manage. 32, 3 (Mar. 1981), 13-20.
29. Harrison, W., et al. Applying software complexity metrics to program maintenance. Computer 15, 9 (Sept. 1982), 65-79.
30. Kirk, R.E. Experimental design, Wadsworth Publishing Company, Belmont, CA, 1968.
31. Lientz, B.P., and Swanson, E.B. Software maintenance management, Addison-Wesley, Reading, MA, 1980.
32. Lientz, B.P., and Swanson, E.B. Problems in application software maintenance. Commun. ACM 24, 11 (Nov. 1981), 763-769.
33. Martin, J., and McClure, C.L. Maintenance of computer software. Savant Institute Report, Carnforth, England, March 1982.
34. McCabe, T.J. A complexity measure. IEEE Trans. Softw. Eng. 2, 4 (Dec. 1976), 308-320.
35. McClure, C.L. Managing software development and maintenance. Van Nostrand Reinhold, New York, 1981.
36. Parikh, G. Tutorial on software maintenance. IEEE, New York, 1983.
37. Peercy, D.E. A software maintainability evaluation methodology. IEEE Trans. Softw. Eng. 7, 4 (July 1981), 343-351.
38. Pennington, N. Stimulus structures and mental representations in expert comprehension of computer programs. Cogn. Psych. 19, 3 (July 1987), 295-341.
39. Rittersbach, G. Technology. World (Peat Marwick), (Jan.-Feb. 1986), 5.
40. Ryge, S. Evaluating structured COBOL as a software engineering discipline. Data Base 12, 3 (Spring 1981), 3-6.
41. Sheppard, S.B., Milliman, P., and Love, T. Modern coding practices and programmer performance. Computer 12, 12 (Dec. 1979), 41-49.
42. Van Gelder, A. Structured programming in COBOL: An approach for applications programmers. Commun. ACM 20, 1 (Jan. 1977), 2-12.
43. Vessey, I., and Weber, R, Some factors affecting program repair maintenance: An empirical study. Commun. ACM 26, 2 (Feb. 1983), 128-134.
44. Vessey, I., and Weber, R. Research on structured programming: An empiricist't evaluation. IEEE Trans. Softw. Eng. 10, 4 (July 1984), 397-407.
45. Weiner-Ehrlich, W.K., Hamrick, J.R., and Rupolo, V.F. Modeling software behavior in terms of a formal life cycle curve: Implications for software maintenance. IEEE Trans. Softw. Eng. 10, 4 (July 1984), 376-383.
46. Weiser, M. Programmers use slices when debugging. Commun. ACM 25, 7 (July 1982), 446-452.
47. Weiss, D.M., and Basili, V.R. Evaluating software development by analysis of changes: Some data from the software engineering laboratory. IEEE Trans. Softw. Eng. 11, 2 (Feb. 1985), 157-168.
48. Winer, B.J. Statistical principles in experimental design, McGraw-Hill, New York, 1971.
49. Wolberg, J.R. Comparing the cost of software conversion to the cost of reprogramming. SIGPLAN Notices 16, 4 (Apr. 1981), pp. 104-110.
50. Woodward, M.R., Hennell, M.A., and Hedley, D. A measure of control flow complexity in program text. IEEE Trans. Softw. Eng. 5, 1 (Jan. 1979), 45-50.
51. Yau, S.S., and Collofello, J.S. Some stability measures for software maintenance. IEEE Trans. Softw. Eng. 6, 6 (Nov. 1980), 545-552.
52. Zolnowski, J.C., and Simmons, D.B. Taking the measure of program complexity. Proc. AFIPS, 1981, NCC, 329-336.