On the portability of quantitative software estimation models

Abstract Evidence in the literature indicates that the portability of currently available quantitative software estimation models is poor. A primary reason is that most models fail to account for managerial characteristics of the software development environment; a set of factors that tend to vary significantly from one organization to another. A major stumbling block has been the inability to quantify the impact of managerial-type factors on cost. In this study, we take a first step towards rectifying this situation. An extensive simulation model of the software development process is developed and used to identify managerial factors that impact the cost of software development, and to quantify the degree of that impact. Because the areas identified are variables that the project manager can objectively evaluate at the beginning of a software project, it should be feasible to incorporate them in future cost estimation models. This, we feel, would improve both their accuracy and portability.

[1]  M WeissDavid Evaluating software development by error analysis , 1984 .

[2]  Sam M. Pederson,et al.  The Software Development Project: Planning and Management , 1982 .

[3]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[4]  Lawrence H. Putnam,et al.  A General Empirical Solution to the Macro Software Sizing and Estimating Problem , 1978, IEEE Transactions on Software Engineering.

[5]  W. E. Vandervelde,et al.  The dynamics of software development project management: An integrative systems dynamic perspective , 1984 .

[6]  Tarek K. Abdel-Hamid,et al.  The Dynamics of Software Project Staffing: A System Dynamics Based Simulation Approach , 1989, IEEE Trans. Software Eng..

[7]  Siba N. Mohanty,et al.  Software cost estimation: Present and future , 1981, Softw. Pract. Exp..

[8]  A. Nico Habermann,et al.  The Engineering Institute: Bridging Practice and Potential , 1985, IEEE Software.

[9]  M. E. Conway HOW DO COMMITTEES INVENT , 1967 .

[10]  Tom DeMarco,et al.  Controlling Software Projects , 1982 .

[11]  Robert Thibodeau,et al.  Life cycle phase interrelationships , 1980, J. Syst. Softw..

[12]  David M. Weiss,et al.  Evaluating software development by error analysis: The data from the Architecture Research Facility , 1984, J. Syst. Softw..

[13]  Kathryn M. Bartol,et al.  Managing Information Systems Personnel: A Reveiw of the Literature and Managerial Implications , 1982, MIS Q..

[14]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[15]  Izak Benbasat,et al.  Programmer and Analyst Time/Cost Estimation , 1980, MIS Q..

[16]  Robert L. Glass,et al.  Modern Programming Practices: A Report from Industry , 1981 .

[17]  Marvin V. Zelkowitz,et al.  Software Engineering Practices in the US and Japan , 1984, Computer.

[18]  K. Weick The social psychology of organizing , 1969 .

[19]  James D. McKeen Successful Development Strategies for Business Application Systems , 1983, MIS Q..

[20]  Barry W. Boehm,et al.  Software cost modeling: Some lessons learned , 1980, J. Syst. Softw..

[21]  John H Lehman,et al.  Software Engineering Project Management: A Survey Concerning U. S. Aerospace Industry Management of Software Development Projects. , 1977 .

[22]  Glenford J. Myers,et al.  A controlled experiment in program testing and code walkthroughs/inspections , 1978, CACM.