Measuring and Monitoring Technical Debt

Advances in Computers

Volumn 82, Issue , 2011, Pages 25-46

  Seaman, Carolyn ^a   Guo, Yuepu ^a  

^a Baltimore County   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 79952799302     PISSN: 00652458     EISSN: None     Source Type: Book Series    
DOI: 10.1016/B978-0-12-385512-1.00002-5     Document Type: Book

References (33)

1. Dekleva S.M. Software maintenance: 1990 status. Software Maintenance Res. Pract. 1992, 4:15.
2. Sousa M.J.C., Moreira H.M. A survey on the software maintenance process 1998, 265-274.
3. Lientz B.P., Swanson E.B., Tompkins G.E. Characteristics of application software maintenance. Commun. ACM 1978, 21:6.
4. Fowler M. Technical Debt. Available:. http://www.martinfowler.com/bliki/TechnicalDebt.html.
5. Program Evolution: Processes of Software Change 1985, Academic Press Professional, Inc, San Diego, CA, USA. M.M. Lehman, L.A. Belady (Eds.).
6. Parnas D.L. Software aging 1994.
7. Cunningham W. The WyCash Portfolio management system 1992, 29-30.
8. McConnell S. 10x Software Development. Available:. http://forums.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx.
9. Rothman J. An Incremental Technique to Pay off Testing Technical Debt. Available:. http://www.stickyminds.com/sitewide.asp?Function=edetail&ObjectType=COL&ObjectId=11011&tth=DYN&tt=siteemail&iDyn=2.
10. Shore J. Quality with a Name. Available:. http://jamesshore.com/Articles/Quality-With-a-Name.html.
11. Carr M.J., Konda S., Monarch I., Walker C.F., Ulrich F.C. Taxonomy-Based Risk Identification 1993, Software Engineering Institute, Pittsburgh, CMU/SEI-93-TR-6.
12. Fairley R. Risk management for software projects. IEEE Software 1994, 11:57-67.
13. Chapman C., Ward S. Project Risk Management: Processes, Techniques and Insights 1996, John Wiley & Sons, West Sussex, UK. first ed.
14. Airmic, A risk management standard, available at http://www.theirm.org/publications/documents/Risk_Management_Standard_030820.pdf, 2002.
15. Hillson D., Hulett D. Assessing risk probability: alternative approaches 2004.
16. P.E. Engert, Z.F. Lansdowne, Risk Matrix User's Guide, The Mitre Corporation, Bedford, MA, USA, 1999. Available at http://www.mitre.org/work/sepo/toolkits/risk/ToolsTechniques/files/UserGuide220.pdf.
17. Ansell J., Wharton F. Risk: Analysis, Assessment and Management 1992, John Wiley & Sons, Chichester.
18. Sommerville I. Software Engineering 2007, Addison-Wesley, Harlow, UK. eighth ed.
19. McConnell S. Software Project Survival Guide 1998, Microsoft Press, Redmond, WA, USA.
20. Kitchenham B., Pfleeger L. Software quality: the elusive target. IEEE Software 1996, 13:12-21.
21. Tian J., Zelkowitz M. Complexity measure evaluation and selection. IEEE Trans. Software Eng. 1995, 21:641-650.
22. El Emam K., et al. The confounding effect of class size on the validity of object-oriented metrics. IEEE Trans. Software Eng. 2001, 27:630-650.
23. Koru G., Jeff T. Comparing high-change modules and modules with the highest measurement values in two large-scale open-source products. IEEE Trans. Software Eng. 2005, 31:625-642.
24. Fowler M., et al. Refactoring. Improving the Design of Existing Code 1999, Addison Wesley, Boston, MA, USA.
25. Lanza M., et al. Object-Oriented Metrics in Practice 2006, Springer, Berlin.
26. Guo Y., et al. Domain-specific tailoring of code smells: an empirical study 2010, Vancouver, Canada, pp. 167-170.
27. van Emden E., Moonen L. Java quality assurance by detecting code smells 2002.
28. Boehm B.W. Software Engineering Economics 1981, Prentice-Hall, Englewood Cliffs, NJ.
29. I.I. Standard, ISO-20926 Software Engineering-Unadjusted Functional Size Measurement Method-Counting Practices Manual, 2003.
30. A. Stellman, J. Greene, Applied software project management, 2005.
31. Jørgensen M. Estimation of software development work effort: evidence on expert judgment and formal models. Int. J. Forecasting 2007, 23:449-462.
32. Jørgensen M. A review of studies on expert estimation of software development effort. J. Systems and Software 2004, 70:37-60.
33. Lutters W.G., Seaman C.B. The value of war stories in debunking the myths of documentation in software maintenance. Inform. Software Technol. 2007, 49:12.