Software complexity and maintenance costs
Communications of the ACMPublished 1 November 1993
Rajiv D. Banker, Srikant M. Datar, Chris F. Kemerer, Dani Zweig
Citations330
SJR quartileQ1
SJR score1.15
SNIP3.34
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
Before empirical evidence linking software complexity to software maintenance costs is relatively weak, several researchers have noted that such results must be applied cautiously to the large-scale commercial application systems that account for most software maintenance expenditures.
Abstract
article Free AccessSoftware complexity and maintenance costs Authors: Rajiv D. Banker Univ. of Minnesota, Minneapolis Univ. of Minnesota, MinneapolisView Profile , Srikant M. Datar Stanford Univ., Stanford, CA Stanford Univ., Stanford, CAView Profile , Chris F. Kemerer Massachusetts Institute of Technology, Cambridge Massachusetts Institute of Technology, CambridgeView Profile , Dani Zweig Naval Postgraduate School, Monterey, CA Naval Postgraduate School, Monterey, CAView Profile Authors Info & Claims Communications of the ACMVolume 36Issue 11Nov. 1993 pp 81–94https://doi.org/10.1145/163359.163375Published:01 November 1993Publication History 199citation4,823DownloadsMetricsTotal Citations199Total Downloads4,823Last 12 Months84Last 6 weeks7 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF
Keywords
Computer Science
IEEE Transactions on Software EngineeringA Methodology for Collecting Valid Software Engineering Data
1,120 Citations1984Victor R. Basili, David M. Weiss
An effective data collection method for evaluating software development methodologies and for studying the software development process is described and results show that data validation is a necessary part of change data collection.
Communications of the ACMSoftware errors and complexity: an empirical investigation0
634 Citations1984Victor R. Basili, Barry T. Perricone
An analysis of the distributions and relationships derived from the change data collected during development of a medium-scale software project produces some surprising insights into the factors influencing software development.
IEEE Transactions on Software EngineeringMeasuring the Psychological Complexity of Software Maintenance Tasks with the Halstead and McCabe Metrics
287 Citations1979Bruce Curtis, Sylvia B. Sheppard +3 more
Three software complexity measures (Halstead's E, McCabe's u(G), and the length as measured by number of statements) were compared to programmer performance on two software maintenance tasks and correlated with both the accuracy of the modification and the time to completion.
Management ScienceA Model to Evaluate Variables Impacting the Productivity of Software Maintenance Projects
249 Citations1991Rajiv D. Banker, Srikant M. Datar +1 more
An estimable production frontier model of software maintenance is developed, using a new methodology that allows the simultaneous estimation of both the production frontier and the effects of several productivity factors.
IEEE Transactions on Software EngineeringCyclomatic complexity density and software maintenance productivity
229 Citations1991Geoffrey K. Gill, Chris F. Kemerer
A simple transformation of the metric is investigated whereby the cyclomatic complexity is divided by the size of the system in source statements, thereby determining a complexity density ratio, which is demonstrated to be a useful predictor of software maintenance productivity on a small pilot sample of maintenance projects.
IEEE Transactions on Software EngineeringThe State of Software Maintenance
217 Citations1987Norman F. Schneidewind
A state of software maintenance survey is presented, indicating the incongruity of the simultaneous existence of importance and neglect in this field.
IEEE Transactions on Software EngineeringScale Economies in New Software Development
208 Citations1989Rajiv D. Banker, Chris F. Kemerer
This paper reconcile two opposing views regarding the presence of economies or diseconomies of scale In new software development by hypothesizing a production function model of software development and showing how to identify the mmt productive scale size that may vary across organizations.
Communications of the ACMSoftware complexity measurement
194 Citations1986Joseph P. Kearney, Robert L. Sedlmeyer +3 more
Inappropriate use of software complexity measures can have large, damaging effects by rewarding poor programming practices and demoralizing good programmers.
Communications of the ACMSystem structure and software maintenance performance
140 Citations1989Virginia R. Gibson, James A. Senn
Results indicate that system improvements lead to decreased total maintenance time and decreased frequency of ripple effect errors, which suggests that improving old systems may be worthwhile and may yield benefits over the remaining life of the system.
IEEE Transactions on Software EngineeringAn Empirical Study of a Syntactic Complexity Family
134 Citations1983Victor R. Basili, David H. Hutchens
The study suggests that individual differences have a large effect on the significance of results where many individuals are used and when an individual is isolated, better results are obtainable.
International Conference on Software EngineeringThird time charm: Stronger prediction of programmer performance by software complexity metrics
116 Citations1979Bill Curtis, Sylvia B. Sheppard +1 more
Improved experimental procedures were improved and much stronger results were obtained than in earlier studies, and Halstead's E proved to be the best predictor of performance, followed by McCabe's v (G) and the number of lines of code.
IEEE Transactions on Software EngineeringAn experimental investigation of software metrics and their relationship to software development effort
102 Citations1989Regina Lind, K. Vairavan
The results are reported of an experimental study of software metrics for a fairly large software system used in a real-time application, including the mutual relationship between various software metrics and, more importantly, the relationship between metrics and the development effort.
The dimensionality of program complexity
82 Citations1989John C. Munson, Taghi M. Khoshgoftaar
The objective of this paper is to examine some recent investigations in the area of software complexity using factor analysis to begin an exploration of the actual dimensionality of the complexity metrics.
Communications of the ACMSome factors affecting program repair maintenance
74 Citations1983Iris Vessey, Ron Weber
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.
Communications of the ACMDeterminants of program repair maintenance requirements
62 Citations1984Lee L. Gremillion
Repairs 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.
Software complexity and maintainability
50 Citations1989Rajiv D. Banker, Srikant M. Datar +1 more
These models are proposed for estimating the economic impacts of software complexity and for identifying the factors which affect a system’s complexity and have shown to be implementable.
International Conference on Software EngineeringCriteria for software modularization
44 Citations1985David N. Card, Gerald Page +1 more
The results indicated that module strength is a good criterion with respect to fault rate, whereas arbitrary module size limitations inhibit programmer productivity.
Journal of Systems and SoftwareManaging programming productivity
31 Citations1985D. Ross Jeffery, Michael Lawrence
The results of the later study were in many respects almost identical to those obtained earlier, thus validating the previous study, and revealed a very strong relationship between a programmer's attitude to his supervisor and programming productivity.
Journal of Systems and SoftwareModule size: A standard or heuristic?
16 Citations1984John B. Bowen
It is claimed that commonly specified limits such as 200 executable source statements have little practical value for programmers, and that the limits have not been validated.
International Conference on Software EngineeringProgramming cost estimate: Is it reasonable?
7 Citations1984Robert E. Boydston
This paper contributes to the software cost estimation by identifying those variables of the product which were found to be governing: The importance of distinguishing higher level language Programming Language Systems (PLS) from low level Basic Assembler Language (BAL), the importance of recognizing the major increase of effort if code is modified rather than new code created.