The week's pick
Reseach Article
A Systematic Method to Evaluate the Software Engineering Practices for Minimizing Technical Debt
| International Journal of Computer Applications |
| Foundation of Computer Science (FCS), NY, USA |
| Volume 131 - Number 4 |
| Year of Publication: 2015 |
| Authors: Vinay Krishna, Anirban Basu |
10.5120/ijca2015907295
|
Vinay Krishna, Anirban Basu . A Systematic Method to Evaluate the Software Engineering Practices for Minimizing Technical Debt. International Journal of Computer Applications. 131, 4 ( December 2015), 21-25. DOI=10.5120/ijca2015907295
Abstract
Often we find it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance. Primary reason for this is inflexibility in design and code which makes it difficult for changes to be incorporated. This inflexibility substantially increases the cost of making changes and this metaphor has been termed as Technical Debt [1]. While Technical Debt cannot be eliminated completely, its burden needs to be reduced. Many practitioners, especially from agile community, have suggested some practices to avoid or eliminate Technical Debt. This paper discusses on a systematic method to evaluate the six software engineering practices that a developer can follow to minimize Technical Debt. These practices have been used and found to be effective when implemented in projects as discussed here.
References
- W. Cunningham, The WyCash Portfolio Management System, OOPSLA, 1992;http://c2.com/doc/oopsla92.html
- S. McConnell, Technical Debt, 2007; http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx
- V. Krishna and A. Basu, “Minimizing Technical Debt: Developer’s Viewpoint”, in Proc ICSEMA 2012, Chennai, Dec 2012
- J. Higgs, The Four Grades of Technical Debt, 2011; http://madebymany.com/blog/the-four-grades-of-technical-debt
- M. Fowler, Technical Debt Quadrant, 2009; http://www.martinfowler.com/bliki/TechnicalDebtQuadrant.html
- T. Theodoropoulos, Technical Debt Part1-4, 2012; http://blog.acrowire.com/technical-debt/technical-debt-part-1-definition
- V. Krishna, My Experiments with TDD, ScrumAlliance, 2010; http://www.scrumalliance.org/articles/357-my-experiments-with-tdd
- D. Laribee, Using Agile Techniques to Pay Back Technical Debt, MSDN Magazine, December 2009; http://msdn.microsoft.com/en-us/magazine/ee819135.aspx
- J. Letouzey, The SQALE Method, January 2012; http://www.sqale.org/wp-content/uploads/2010/08/SQALE-Method-EN-V1-0.pdf
- R. C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship, Aug 2008, Prentice Hill, page 4
Index Terms
Keywords