ACM Home Page
Please provide us with feedback. Feedback
Managing application program maintenance expenditures
Full text PdfPdf (821 KB)
Source
Communications of the ACM archive
Volume 26 ,  Issue 10  (October 1983) table of contents
Pages: 739 - 746  
Year of Publication: 1983
ISSN:0001-0782
Author
Tor Guimaraes  Case Western Univ., Cleveland, OH
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 32,   Citation Count: 16
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/358413.358421
What is a DOI?

ABSTRACT

Program maintenance represents a major portion of the total expenditures on application programs. Despite the attention this subject has received in the MIS literature, new guidelines to action in this area remain of great interest to practitioners. A large number of variables thought to be determinants of application program maintenance expenditure have been studied through the inspection of application portfolios and personal interviews with top computer executives and systems development personnel. Based on the results, recommendations are made on how to reduce application program maintenance expenditures.


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
AC, Program maintenance: User's view. Data Process., Sept.-Oct. 1973.
 
2
Berg, J., Ed. Database directions: The next steps. NBS Special Publication 451, Sept. 1976.
 
3
Braddock, F. How to stretch your software lifecycle. ICP Interface, Spring 1980.
 
4
Boehm, B. W. Software and its impact: A quantitative assessment. Datamation (May 1973).
 
5
Boehm, B. W. Software engineering. IEEE Trans. Comput. (Dec. 1976).
 
6
Brantley, C. L. and Osajima, Y. R. Continuing development of centrally developed and maintained software systems, IEEE Computer Society Conference Proceedings (Spring, 1975).
 
7
 
8
Canning, R. G. That maintenance "iceberg" EDP Anal. (Oct. 1972).
 
9
Codasyl. Selection and acquisition of DBMS: A report of the CODASYL systems committee. (March 1976)
 
10
Daly, E. B. Management of software development. IEEE Trans. Softw. Eng. Forthcoming.
 
11
Ditri, A. E., Shaw, J. C., and Atkins, W. Managing the EDP function, McGraw-Hill, New York, 1971.
 
12
Elshoff, J. L. An analysis of some commercial PL/1 programs, IEEE Trans. Softw. Eng. SE-2, 2 (June 1976).
 
13
Fewer, A. R. and Fowlkes, E. B. Relating computer program maintainability to software measures. Proceedings of the 1979 National Computer Conference, lune 1979.
 
14
Guimaraes, N. Survey and classification of implementation studies. Management Information Systems Research Center, University of Minnesota, unpublished paper, 1978.
 
15
Guimaraes, N. An analysis of application program life patterns, Ph.D. Thesis, University of Minnesota, 1981.
 
16
Gunderman, R. E. A glimpse into program maintenance. Dotamation (June 1973).
 
17
J. Hoskyns and Co. Implications of'using modular programming, Guide No. 1, Hoskyns System Research, London, 1973.
 
18
Khan, Z. How to tackle the systems maintenance dilemma. Canadian Data System, March 1975.
19
20
 
21
McLaughlin, R. A. 1975 DP Budgets. Datamation (March 1975).
 
22
McGreggor, Bob. Program maintenance. Data Process. (May-June 1973).
 
23
Mooney, J. W. Organized program maintenance. Datomation Feb. 1975.
 
24
Olson, M. H. An investigation of organizational contingencies associated with structure of the information systems function. Ph.D. Thesis, University of Minnesota, 1978.
 
25
Punter, M. Programming for maintenance, Data Process. (Sept.-Oct. 1975).
 
26
Riggs, R. Computer system maintenance, Datamation (November 1969).
 
27
Snyders, J. Taking the drudgery out of documentation, Comput. Decis. (July 1979).
28

CITED BY  16