Skip to main content

Criteria for Estimating Effort for Requirements Changes

  • Conference paper
Software Process Improvement (EuroSPI 2008)

Part of the book series: Communications in Computer and Information Science ((CCIS,volume 16))

Included in the following conference series:

Abstract

IT practitioners realize that poor scheduling can cause project failure. This is because schedule overruns may be caused by the effort involved in making requirement changes. A software process improvement challenge is to better estimate the cost and effort of requirements changes. Difficulties with such effort estimation is partially caused by lack of data for analysis supported with little information about the data types involved in the requirements changes. This research is an exploratory study, based on change request forms, in requirements change categorization. This categorization can be used to develop an empirical model for requirements change effort as input into a cost estimation model. An empirically based estimation model will provide IT practitioners with a basis for better estimation of effort needed for requirements changes.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 99.00
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 129.00
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Chua, B.B., Verner, J.M.: Estimation of rework effort based on requirements categorization. In: 5th Proceeding of Software Measurement European Forum (SMEF) (in press, 2008)

    Google Scholar 

  2. Chua, B.B., Verner, J.M.: A Framework for predicting Person Effort on Requirements Changes. In: Proceeding of 5th International Conference on Software Methodologies Tools and Techniques (2006)

    Google Scholar 

  3. Firesmith, D.: Common Requirements Problems, Their Negative Consequences, and the Industry Best Practices to Help Solve Them., Software Engineering Institute. Journal of Object Technology 6(1) (January-February 2007)

    Google Scholar 

  4. Gopal, A., Mukhopadhyay, T., Krishnan, M.S.: The Role of Software Processes and Communication in Offshore Software Development. Communications of the ACM 45(4) (2002)

    Google Scholar 

  5. Bianchi, A., Caivano, D., Lanubile, F., Rago, F., Visaggio, G.: An Empirical Study of distributed software maintenance. In: Proceeding of International Software Maintenance (IEEE) (2002)

    Google Scholar 

  6. Wiegers, K.E.: Lessons from Software Work Effort Metrics. Software Development (1994), http://www.processimpact.com/articles/metrics.pdf

  7. Boehm, B.W., Clark, B., Horowitz, C., Westland, R., Madachy, S., Selby, R.: Cost Models for Futre Software Life-Cycle Processes: COCOMO 2.0. Annals of Software Engineering Special Volume on Software Process and Product Measurement, Vol. 1, pp 45-60 (1995)

    Google Scholar 

  8. Shooman, M.L., Bolsky, M.: Types, Distribution, and Test and Correction Times For Programming Errors. In: Proceedings of the International conference on reliable software, Los Angeles, California, USA (1975)

    Google Scholar 

  9. Bell, T.E., Thayer, T.A.: Software Requirements: Are They Really a Problem? In: Proceedings of 2nd IEEE Iinternational confernce on software engineering, San Francisco, California,United States (1976)

    Google Scholar 

  10. Basili, V.R., Weiss, M.: Evaluation of a Software Requirements Document By Analysis of Change Data. In: Proceedings of the 5th International conference on Software Engineering, San Diego, Califonia, United States (1981)

    Google Scholar 

  11. Basili, V.R., Perricone, B.T.: Software Errors and Complexity: An Empirical Investigation. In: Proceedings of Communciations of the ACM, vol. 27(1), pp. 42–52 (1984)

    Google Scholar 

  12. Stark, G.E., Skillicorn, A., Oman, P.O., Ameele, R.: An examination of the Effects of Requirements Changes on Software Releases. Journal of Software Maintenance: ReseaRCsh and Practice 5(11), 293–309 (1999)

    Article  Google Scholar 

  13. Stark, G.E.: Measurements for Managing Software Maintenance. In: Proceedings of the International conference on Software Maintenance, Monterey, California, pp. 152–161 (1996)

    Google Scholar 

  14. Yashwant, K., Denton, M.J.: Requirements Volatility and Defect Density. In: Proceedings of the 10th International Symposium on Software Reliability Engineering, SA (1999)

    Google Scholar 

  15. Melonfire: Five common errors in requirements analysis (and how to avoid them)

    Google Scholar 

  16. Yardley, D.: Successful IT Project Delivery. Addison-Wesley, Reading (2002)

    Google Scholar 

  17. Standish Group : The Standish Group Report, Chaos (2006), http://www.cs.nmt.edu/~cs328/reading/Standish.pdf

  18. Sommerville, I., Sawyer, P.: Requirements Engineering: A Good Practice Guide. John Wiley and Sons. Inc., New York (1997)

    MATH  Google Scholar 

  19. Tran, X.: Improving the Recognition and Correction of Poor Requirements. In: Proceedings of the Systems Engineering, Test & Evaluation Conference, SETE 2005 – A Decade of Growth and Beyond, Brisbane, Queensland (2005)

    Google Scholar 

  20. Kasser, J.E.: A Prototype Tool for Improving the Wording of Requirements. In: Proceedings of the 12th International Symposium of INCOSE, Las Vegas, NV (2002)

    Google Scholar 

  21. Chulani, S.D.: Incorporating Bayesian Analysis to Improve the Accuracy of COCOMO II and Its Quality Model Extension, P.h.D. Qualifying Exam Report, University of Southern California, USA (1998)

    Google Scholar 

  22. Boehm, B.W.: Software Engineering Economics. Prentice Hall, Englewood Cliffs (1981)

    MATH  Google Scholar 

  23. Albrecht, A.: Measuring Application Development Productivity. In: Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, pp. 83–92 (1979)

    Google Scholar 

  24. Putman, L.H.: A general empirical solution to the maCRsosoftware sizing and estimating problem. Proceeding of IEEE Transactions on Software Engineering 4, 345–361 (1978)

    Article  Google Scholar 

  25. Fenton, N., Plfleeger, S.L.: Software Metrics: A Rigorous and Practical Approach. PWS Publishing Company (1975)

    Google Scholar 

  26. Verner, J.M., Cerpa, N.: Software Project Failure. Accepted by CACM, Communication of ACM (in press, 2008)

    Google Scholar 

  27. Chua, B.B., Verner, J.M.: IT Practitioner’s Perspective on Australian Risk Management Practices and Tools For Software Development Projects: A Pilot Study. In: The 4th International Conference proceeding on Software Methodologies, Tools, and Techniques (SoMET) (2004)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Rory V. O’Connor Nathan Baddoo Kari Smolander Richard Messnarz

Rights and permissions

Reprints and permissions

Copyright information

© 2008 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Chua, B.B., Bernardo, D.V., Verner, J. (2008). Criteria for Estimating Effort for Requirements Changes. In: O’Connor, R.V., Baddoo, N., Smolander, K., Messnarz, R. (eds) Software Process Improvement. EuroSPI 2008. Communications in Computer and Information Science, vol 16. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-85936-9_4

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-85936-9_4

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-85934-5

  • Online ISBN: 978-3-540-85936-9

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics