Software Development Practices, Software Complexity, and Software Maintenance Performance: A Field Study
Management SciencePublished 1 April 1998
Rajiv D. Banker, Gordon B. Davis, Sandra A. Slaughter
Citations266
SJR quartileQ1
SJR score5.72
SNIP2.88
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
A two-stage model in which software complexity is a key intermediate variable that links design and development decisions to their downstream effects on software maintenance is developed, suggesting an important link between software development practices and maintenance performance.
Abstract
Software maintenance claims a large proportion of organizational resources. It is thought that many maintenance problems derive from inadequate software design and development practices. Poor design choices can result in complex software that is costly to support and difficult to change. However, it is difficult to assess the actual maintenance performance effects of software development practices because their impact is realized over the software life cycle. To estimate the impact of development activities in a more practical time frame, this research develops a two-stage model in which software complexity is a key intermediate variable that links design and development decisions to their downstream effects on software maintenance. The research analyzes data collected from a national mass merchandising retailer on 29 software enhancement projects and 23 software applications in a large IBM COBOL environment. Results indicate that the use of a code generator in development is associated with increased software complexity and software enhancement project effort. The use of packaged software is associated with decreased software complexity and software enhancement effort. These results suggest an important link between software development practices and maintenance performance.
Keywords
Computer Science
EconometricaA Heteroskedasticity-Consistent Covariance Matrix Estimator and a Direct Test for Heteroskedasticity
26,139 Citations1980Halbert White
Academy of Management ReviewBuilding Theories from Case Study Research
23,160 Citations1989Kathleen M. Eisenhardt
BiometrikaAn analysis of variance test for normality (complete samples)
19,344 Citations1965Samuel S. Shapiro, M. B. Wilk
Academy of Management ReviewBuilding Theories from Case Study Research
16,240 Citations1989Kathleen M. Eisenhardt
Journal of the Royal Statistical Society Series B (Statistical Methodology)An Analysis of Transformations
15,066 Citations1964George E. P. Box, David R. Cox
BiometricsApplied Multivariate Statistical Analysis.
11,424 Citations1988Andrea Johnson, Dean W. Wichern
TechnometricsApplied Linear Statistical Models
7,271 Citations1997Michael Kutner, Nachtsheim, Christopher J. +2 more
Journal of the Operational Research SocietyRegression Diagnostics -- Identifying Influential Data and Sources of Collinearity
6,517 Citations1981Chris Beaumont, D. A. Belsley +2 more
Academy of Management ReviewA Theory of Goal Setting and Task PerformanceA Theory of Goal Setting and Task Performance, by LockeEdwin A. and LathamGary P.. Englewood Cliffs, NJ: Prentice-Hall, 1990.
4,182 Citations1991Henry L. Tosi
ComputerNo Silver Bullet Essence and Accidents of Software Engineering
3,144 Citations1987Brooks
This article shall try to show why there is no single development, in either technology or management technique, that by itself promises even one order-of-magnitude improvement in productivity, in reliability, in simplicity.
IEEE Transactions on Software EngineeringSoftware Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation
1,550 Citations1983Alan J. Albrecht, John E. Gaffney
This paper demonstrates the equivalence between Albrecht's external input/output data flow representative of a program (the "function points" metric) and Halstead's "software science" or "software linguistics" model of a programs as well as the "soft content" variation of Halstead’s model suggested by Gaffney.
Organizational Behavior and Human Decision ProcessesTask complexity: Definition of the construct
1,373 Citations1986Robert E. Wood
Academy of Management ReviewTask Complexity: A Review and Analysis
1,252 Citations1988Donald J. Campbell
IEEE Transactions on Software EngineeringEvaluating software complexity measures
841 Citations1988Elaine J. Weyuker
A set of properties of syntactic software complexity measures is proposed to serve as a basis for the evaluation of such measures, and several are found to fail to possess particularly fundamental properties; this failure calls into question their usefulness in measuring synthetic complexity.
Software Psychology: Human Factors in Computer and Information Systems
618 Citations1980Ben Shneiderman
Journal of Applied PsychologyTask complexity as a moderator of goal effects: A meta-analysis.
588 Citations1987Robert E. Wood, Anthony J. Mento +1 more
Cognitive PsychologyStimulus structures and mental representations in expert comprehension of computer programs
516 Citations1987Nancy Pennington
Investigating the role of programming knowledge in program comprehension and the nature of mental representations of programs suggests that procedural rather than functional units form the basis of expert programmers' mental representations, supporting work in other areas of text comprehension and showing the importance of text structure knowledge in understanding.
TechnometricsThe Use of the Rank Transform in Regression
461 Citations1979Ronald L. Iman, W. J. Conover
Communications of the ACMSoftware complexity and maintenance costs
330 Citations1993Rajiv D. Banker, Srikant M. Datar +2 more
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.
Information & ManagementInformation systems design methodologies - A comparative review
317 Citations1983
When you read more every page of this information systems design methodologies a comparative review, what you will obtain is something great.
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.
IEEE SoftwareScience and substance: a challenge to software engineers
269 Citations1994Norman Fenton, Shari Lawrence Pfleeger +1 more
This work suggests several ways to address the problem of software development and maintenance with new practices whose effectiveness is rarely, if ever, backed up by hard evidence.
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.
DSpace@MIT (Massachusetts Institute of Technology)Reliability of function points measurement : a field experiment
222 Citations2009Chris F. Kemerer
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 EngineeringIdentifying Error-Prone Software—An Empirical Study
209 Citations1985V. Y. Shen, Tze-Jie Yu +2 more
Through a detailed analysis of three software products and their error discovery histories, simple metrics related to the amount of data and the structural complexity of programs are found to be of value for identifying error-prone software.
Economics As a Science
184 Citations1970Kenneth E. Boulding
Journal of Systems and SoftwareMental models and software maintenance
179 Citations1987David Littman, Jeannine Pinto +2 more
Vidoetaped protocols of experienced programmers as they enhanced a personnel data base program are analyzed and it is suggested that there are two strategies for program understanding, the systematic strategy and the as-needed strategy.
Journal of Software Maintenance Research and PracticeSoftware maintenance management: Changes in the last decade
154 Citations1990John T. Nosek, Prashant Palvia
One of the important, but somewhat disturbing, conclusions is that maintenance problems are pretty much the same as during the 1970s (except for minor changes), despite advances made in structured methodologies and techniques.
IEEE Transactions on Software EngineeringAn Empirical Study of Software Metrics
149 Citations1987H.F. Li, William K. Cheung
Communications of the ACMReliability of function points measurement
145 Citations1993Chris F. Kemerer
S oftware engineering management encompasses two major functions, planning and control, both of which require the capability to accurately and reliably measure the software being delivered.
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.
Annals of Software EngineeringSoftware complexity and software maintenance: A survey of empirical research
134 Citations1995Chris F. Kemerer
A survey of the empirical literature in this area shows two broad areas of study: complexity metrics and comprehension, and a series of recommendations for future research.
Medical Entomology and ZoologyMaintaining Information Systems in Organizations
123 Citations1989E. Burton Swanson, Cynthia Mathis Beath
This volume focuses on comparative environments for IS maintenance, and on alternative strategies for management of the maintenance process, including alternative approaches to task definition, work technique and more.
Singapore Management University Institutional Knowledge (InK) (Singapore Management University)Strategic information technology management: Perspectives on organizational growth and competitive advantage
119 Citations1993Rajiv D. Banker, Robert J. Kauffman +1 more
The impact of IT investment on quality management and the diversity of IT applications when IT creates a threat and an opportunity and much more!.
Proceedings of the IEEESubstantiating programmer variability
98 Citations1981Bruce Curtis
An alternate data set is presented which substantiates the enormous variability in programmer performance and the opportunity for productivity gains and improved experimental methods in research through reducing the range of this variability remains fertile.
Information Systems ResearchPerformance Evaluation Metrics for Information Systems Development: A Principal-Agent Model
89 Citations1992Rajiv D. Banker, Chris F. Kemerer
This paper develops a principal-agent model for IS development, where information systems development is typically assigned by the user to a systems developer (agent), and the use of multiple measures is necessary given the multi-dimensional nature of successful systems development.
Communications of the ACMManaging application program maintenance expenditures
87 Citations1983Tor Guimãrães
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.
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.
Management ScienceAn Economics Approach to Modeling the Productivity of Computer Systems
78 Citations1980Charles H. Kriebei, Artur Raviv
The approach to modeling the productivity of computer systems is based on conventional economic theory and empirical analysis, to view the organization as a marketplace for computing and information services which contains elements of supply and demand.
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.
International Journal of Man-Machine StudiesToward a theory of computer program bugs: an empirical test
52 Citations1989Iris Vessey
The results are interpreted in light of the need to formulate a mental model of correct program functioning and to determine the location of the program bug in terms of the functioning of that model.
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.
AIS Electronic Library (AISeL) (Association for Information Systems)FACTORS AFFECTING SOFTWARE MAINTENANCE PRODUCTIVITY: AN EXPLORATORY STUDYl
46 Citations1987Rajiv D. Banker, Chris F. Kemerer
Preliminary results have suggested a number of new research directions and have prompted the data-site to begin a full scale data collection effort in order to validate a model of software maintenance productivity.
Communications of the ACMPractical results from measuring software quality
45 Citations1993Robert B. Grady
This article gives a defect categorization model that highlights areas for potential improvement for an organization and looks at examples of proven software best practices that help to avoid defects or detect them sooner.
International Journal of Man-Machine StudiesThe role of program structure in software maintenance
44 Citations1992Deborah A. Boehm‐Davis, Robert W. Holt +1 more
Students and professional programmers were asked to make either simple or complex modifications to programs that had been generated using each of three different program structures, suggesting that problem structure, problem content, complexity of modification, and programmer experience all play a crucial role in determining performance and the representation formed.
Journal of Systems and SoftwareEffects of programming experience in debugging semantic errors
28 Citations1989Paul Oman, Curtis +2 more
Results demonstrate skill-level differences, show the importance of error and message interaction, and support previous research claiming that programmers can almost always correct an error once it is located.
DSpace@MIT (Massachusetts Institute of Technology)Software complexity and software maintenance costs
27 Citations2011Rajiv D. Banker
PubMedBuying software off the rack. Packages can be the solution to the software shortage.
22 Citations1983James R. Martin, Carma McClure
The article describes the features a company should look for in packaged software and the optimal provisions of a software contract.
Software maintenance: a profile of past empirical research
20 Citations1988David P. Hale, Dwight A. Haworth
The authors examine empirical software maintenance research reported from 1978 through 1987 and categorize the research according to placement, origin, and nature of research to determine what has been done in the past.
Office Technology and PeopleOFFICE PRODUCTIVITY: A MICROECONOMIC FRAMEWORK FOR EMPIRICAL RESEARCH
14 Citations1982Charles B. Stabell
A framework for empirical research on the productivity effects of office technology is outlined, based on micro‐economic production theory, and the unit of analysis is the firm.
OmegaA human information processing perspective on software maintenance
12 Citations1994Sampath Ramanujan, RB Cooper
The human information processing model is shown to provide explanatory as well as descriptive power, providing a basis for managerial action and recommendations aimed at decreasing maintenance effort which can decrease maintenance cost and increase the responsiveness of maintenance to changing organizational needs.
INFORMS Journal on Applied AnalyticsSoftware Productivity as a Strategic Variable
12 Citations1985Gus W. Grammas, June R. Klein
In recent years the major incentive for adopting computer technology—increased productivity through automation of labor intensive tasks—is eroding as the field of data processing itself becomes labor intensive.
ACM SIGSOFT Software Engineering NotesSoftware maintenance news
8 Citations1985Girish Parikh
My goal is to make maintenance programming a highly respected discipline, and I would even dare to call it "Softwar e Maintenance Engineering".
Assessing user experience with CASE tools: an exploratory analysis
3 Citations1992Gordon C. Everest, Macedonio Alanis
Most organizations had strong management support and a high ranking executive to champion the adoption and use of CASE, and more organizations had made a commitment to use construction tools than design, and to use design tools than planning tools.