[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
research-article

Software Effort, Quality, and Cycle Time: A Study of CMM Level 5 Projects

Published: 01 March 2007 Publication History

Abstract

The Capability Maturity Model (CMM) has become a popular methodology for improving software development processes with the goal of developing high-quality software within budget and planned cycle time. Prior research literature, while not exclusively focusing on CMM level 5 projects, has identified a host of factors as determinants of software development effort, quality, and cycle time. In this study, we focus exclusively on CMM level 5 projects from multiple organizations to study the impacts of highly mature processes on effort, quality, and cycle time. Using a linear regression model based on data collected from 37 CMM level 5 projects of four organizations, we find that high levels of process maturity, as indicated by CMM level 5 rating, reduce the effects of most factors that were previously believed to impact software development effort, quality, and cycle time. The only factor found to be significant in determining effort, cycle time, and quality was software size. On the average, the developed models predicted effort and cycle time around 12 percent and defects to about 49 percent of the actuals, across organizations. Overall, the results in this paper indicate that some of the biggest rewards from high levels of process maturity come from the reduction in variance of software development outcomes that were caused by factors other than software size.

References

[1]
P. Jalote, CMM in Practice: Processes for Executing Software Projects at Infosys. Addison Wesley Longman, 2000.
[2]
M.C. Paulk, “How ISO 9001 Compares with the CMM,” IEEE Software, vol. 12, no. 1, pp. 74-83, Jan. 1995.
[3]
T. Pyzdek, The Six Sigma Handbook: The Complete Guide for Greenbelts, Blackbelts, and Managers at All Levels. McGraw-Hill, 2003.
[4]
D.E. Harter, M.S. Krishnan, and S.A. Slaughter, “Effects of Process Maturity on Quality, Cycle Time and Effort in Software Product Development,” Management Science, vol. 46, pp. 451-466, 2000.
[5]
H. Wohlwend and S. Rosenbaum, “Schlumberger's Software Improvement Program,” IEEE Trans. Software Eng., vol. 20, no. 11, pp.833-839, Nov. 1994.
[6]
M. Diaz and J. Sligo, “How Software Process Improvement Helped Motorola,” IEEE Software, vol. 14, no. 5, pp. 75-81, Sept.-Oct., 1997.
[7]
B.W. Boehm et al., Software Cost Estimation with COCOMO II. Prentice-Hall, 2000.
[8]
T. Mukhopadhyay, S.S. Vicinanza, and M.J. Prietula, “Examining the Feasibility of a Case-Based Reasoning Model for Software-Effort Estimation,” MIS Quarterly, vol. 16, pp. 155-171, 1992.
[9]
D.E. Harter and S.A. Slaughter, “Quality Improvement and Infrastructure Activity Costs in Software Development: A Longitudinal Analysis,” Management Science, vol. 49, pp. 784-800, 2003.
[10]
R.D. Banker, G.B. Davis, and S.A. Slaughter, “Software Development Practices, Software Complexity and Software Maintenance Performance: A Field Study,” Management Science, vol. 44, pp. 433-450, 1998.
[11]
G. Li and S. Rajagopalan, “Process Improvement, Quality and Learning Effects,” Management Science, vol. 44, pp. 1517-1532, 1998.
[12]
N. Ramasubbu et al., “Effect of Quality Management Practices in Distributed Offshore Software Development: An Empirical Analysis,” Proc. Academy of Management Meeting, 2004.
[13]
K. Chari and M. Agrawal, “Software Effort, Quality and Cycle Time: A Study,” Proc. INFORMS Conf. Information Systems and Technology, 2005.
[14]
A.J. Albrecht and J.E.J. Gaffney, “Software Function, Source Lines of Code and Development Effort Prediction: A Software Science Validation,” IEEE Trans. Software Eng., vol. 9, pp. 639-648, 1983.
[15]
C.F. Kemerer, “An Empirical Validation of Software Cost Estimation Models,” Comm. ACM, vol. 30, pp. 416-429, 1987.
[16]
J. Baik, “Disaggregating and Calibrating the Case Tool Variable in COCOMO II,” IEEE Trans. Software Eng., vol. 28, no. 6, pp. 1009-1022, Nov. 2002.
[17]
“List of Published SCAMPI Appraisal Results,” Software Eng. Inst., 2006.
[18]
J.E.J. Gaffney, “Estimating the Number of Faults in Code,” IEEE Trans. Software Eng., vol. 10, no. 4, pp. 459-464, July 1984.
[19]
R.D. Banker and C.F. Kemerer, “Scale Economies in New Software Development,” IEEE Trans. Software Eng., vol. 15, pp. 1199-1205, 1989.
[20]
B.T. Compton and C. Withrow, “Prediction and Control of Ada Software Defects,” J. Systems and Software, vol. 12, pp. 199-207, 1990.
[21]
J.E. Matson, B.E. Barrett, and J.M. Mellichamp, “Software Development Cost Estimation Using Function Points,” IEEE Trans. Software Eng., vol. 20, pp. 275-287, 1994.
[22]
M. Shepperd and C. Schofield, “Estimating Software Project Effort Using Analogies,” IEEE Trans. Software Eng., vol. 23, no. 11, pp.736-743, Nov. 1997.
[23]
M.S. Krishnan and M.I. Kellner, “Measuring Process Consistency: Implications Reducing Software Defects,” Management Science, vol. 25, pp. 800-815, 1999.
[24]
K. Maxwell, L.V. Wassenhove, and S. Dutta, “Performance Evaluation of General and Company Specific Models in Software Development Effort Estimation,” Management Science, vol. 45, pp.787-803, 1999.
[25]
B.K. Clark, “Quantifying the Effects of Process Improvement on Effort,” IEEE Software, vol. 17, pp. 65-70, 2000.
[26]
M.S. Krishnan et al., “An Empirical Analysis of Productivity and Quality in Software Products,” Management Science, vol. 46, pp.745-759, 2000.
[27]
N. Nan, D.E. Harter, and T. Thomas, “The Impact of Schedule Pressure on Software Development: A Behavioral Perspective,” Proc. Int'l Conf. Information Systems, 2003.
[28]
P.C. Pendharkar, G.H. Subramanian, and J.A. Rodger, “A Probabilistic Model for Predicting Software Development Effort,” IEEE Trans. Software Eng., vol. 31, pp. 615-624, 2005.
[29]
“True S and Price S: Software Development and Lifecycle Estimating Models,” PRICE Systems, 2006.
[30]
“CA-Estimacs,” Computer Assoc., 2006.
[31]
“SEER-SEM,” GA SEER Tech nologies, 2006.
[32]
B.W. Boehm, Software Engineering Economics. Prentice-Hall, 1981.
[33]
Function Point Counting Practices Manual. Int'l Function Point Users Group, 2006.
[34]
S.N. Mohanty, “Software Cost Estimation: Present and Future,” Software—Practice and Experience, vol. 11, pp. 103-121, 1981.
[35]
C.A. Behrens, “Measuring the Productivity of Computer Systems Development Activities with Function Points,” IEEE Trans. Software Eng., vol. 9, no. 6, pp. 648-652, Nov. 1983.
[36]
H.A. Rubin, “Macroestimation of Software Development Parameters: The Estimacs System,” Proc. SOFTFAIR Conf. Software Development Tools, Techniques, and Alternatives, 1983.
[37]
R.D. Banker and S.A. Slaughter, “The Moderating Effects of Structure on Volatility and Complexity in Software Enhancement,” Information Systems Research, vol. 11, pp. 219-240, 2000.
[38]
D.R. Goldenson and D.L. Gibson, “Demonstrating the Impact and Benefits of CMMI: An Update and Preliminary Results,” Technical Report CMU/SEI-2003-SR-009, Software Eng. Inst., 2003.
[39]
S.S. Vicinanza, T. Mukhopadhyay, and M.J. Prietula, “Software-Effort Estimation: An Exploratory Study of Expert Performance,” Information Systems Research, vol. 2, pp. 243-262, 1991.
[40]
T. Mukhopadhyay and S. Kekre, “Software Effort Models for Early Estimation of Process Control Applications,” IEEE Trans. Software Eng., vol. 18, no. 10, pp. 915-924, Oct. 1992.
[41]
C.K. Prahalad and M.S. Krishnan, “The New Meaning of Quality in the Information Age,” Harvard Business Rev., vol. 1999, pp. 109-118, 1999.
[42]
ISO/IEC 9126-1, 2001, Int'l Standards Organization, 1991.
[43]
C. Fox and W. Frakes, “The Quality Approach: Is It Delivering?” Comm. ACM, vol. 40, pp. 25-29, 1997.
[44]
D.E. Harter and S.A. Slaughter, “The Cascading Effect of Process Maturity on Software Quality,” Proc. Int'l Conf. Information Systems, 2000.
[45]
R.D. Austin, “The Effects of Time Pressure on Quality in Software Development: An Agency Model,” Information Systems Research, vol. 12, pp. 195-207, 2001.
[46]
V. Basili, “The Experience Factory and Its Relationship to Other Quality Approaches,” Advances in Computers, vol. 41, pp. 65-82, 1995.
[47]
W.S. Humphrey, “Characterizing the Software Process: A Maturity Framework,” IEEE Software, vol. 5, no. 3, pp. 73-79, Mar. 1988.
[48]
M.C. Paulk et al., “Capability Maturity Model, Version 1.1,” IEEE Software, vol. 10, no. 4, pp. 18-27, July 1993.
[49]
F.P.J. Brooks, The Mythical Man-Month, second ed. Addison-Wesley, 1995.
[50]
M. van Genuchten, “Why Is Software Late? An Empirical Study of Reasons for Delay in Software Development,” IEEE Trans. Software Eng., vol. 17, no. 6, pp. 582-590, June 1991.
[51]
D.E. Harter, S.A. Slaughter, and M.S. Krishnan, “Benefits of CMM-Based Process Improvements for Support Activities—An Empirical Study,” Proc. Am. Conf. Information Systems, 1998.
[52]
M.J. Benner and M. Tushman, “Process Management and Technological Innovation: A Longitudinal Study of the Photography and Paint Industries,” Administrative Science Quarterly, vol. 47, pp. 676-706, 2002.
[53]
L.H. Putnam, “A General Empirical Solution to the Macro Software Sizing and Estimating Problem,” IEEE Trans. Software Eng., vol. 4, no. 4, pp. 345-361, July 1978.
[54]
R.D. Banker, S.M. Datar, and C.F. Kemerer, “A Model to Evaluate Variables Impacting the Productivity of Software Maintenance Projects,” Management Science, vol. 37, pp. 1-18, 1991.
[55]
R. Nelson, “Educational Needs as Perceived by IS and End-User Personnel: A Survey of Knowledge and Skill Requirements,” MIS Quarterly, vol. 15, pp. 503-525, 1991.
[56]
IEEE Std. 830-1998, IEEE Recommended Practice for Software Requirements Specifications, IEEE, 25 June 1998.
[57]
E.B. Swanson and E. Dans, “System Life Expectancy and the Maintenance Effort: Exploring Their Equilibrium,” MIS Quarterly, vol. 24, pp. 277-297, 2000.

Cited By

View all
  • (2024)Cleaning Up Confounding: Accounting for Endogeneity Using Instrumental Variables and Two-Stage ModelsACM Transactions on Software Engineering and Methodology10.1145/367473033:8(1-31)Online publication date: 21-Nov-2024
  • (2023)Dynamic Prediction of Delays in Software Projects using Delay Patterns and Bayesian ModelingProceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering10.1145/3611643.3616328(1012-1023)Online publication date: 30-Nov-2023
  • (2021)Software Enhancement Effort Prediction Using Machine-Learning Techniques: A Systematic Mapping StudySN Computer Science10.1007/s42979-021-00872-62:6Online publication date: 22-Sep-2021
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering  Volume 33, Issue 3
March 2007
64 pages

Publisher

IEEE Press

Publication History

Published: 01 March 2007

Author Tags

  1. Cost estimation
  2. productivity.
  3. software quality
  4. time estimation

Qualifiers

  • Research-article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 23 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2024)Cleaning Up Confounding: Accounting for Endogeneity Using Instrumental Variables and Two-Stage ModelsACM Transactions on Software Engineering and Methodology10.1145/367473033:8(1-31)Online publication date: 21-Nov-2024
  • (2023)Dynamic Prediction of Delays in Software Projects using Delay Patterns and Bayesian ModelingProceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering10.1145/3611643.3616328(1012-1023)Online publication date: 30-Nov-2023
  • (2021)Software Enhancement Effort Prediction Using Machine-Learning Techniques: A Systematic Mapping StudySN Computer Science10.1007/s42979-021-00872-62:6Online publication date: 22-Sep-2021
  • (2021)The Moderating Effect of Management Review in Enhancing Software Reliability: A Partial Least Square ApproachInformation Systems Frontiers10.1007/s10796-021-10209-624:6(1845-1863)Online publication date: 3-Oct-2021
  • (2018)Omission of Quality Software Development PracticesACM Computing Surveys10.1145/317774651:2(1-27)Online publication date: 13-Feb-2018
  • (2018)Impact of incorrect and new requirements on waterfall software project outcomesEmpirical Software Engineering10.1007/s10664-017-9506-423:1(165-185)Online publication date: 1-Feb-2018
  • (2017)Research patterns and trends in software effort estimationInformation and Software Technology10.1016/j.infsof.2017.06.00291:C(1-21)Online publication date: 1-Nov-2017
  • (2017)Impact of customization over software quality in ERP projectsSoftware Quality Journal10.1007/s11219-016-9314-x25:2(581-598)Online publication date: 1-Jun-2017
  • (2017)The Contribution of Process, People and Perception to Information Systems Quality and SuccessThe Electronic Journal of Information Systems in Developing Countries10.1002/j.1681-4835.2012.tb00392.x55:1(1-22)Online publication date: 5-Dec-2017
  • (2016)Technical Debt and the Reliability of Enterprise Software SystemsManagement Science10.1287/mnsc.2015.219662:5(1487-1510)Online publication date: 1-May-2016
  • Show More Cited By

View Options

View options

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media