The "Technical Debt" metaphor is gaining recognition in the software development community, not only to communicate the debt to the non-technical stakeholders but also to maintain the long term health of the software project. The idea is that software practitioners accept compromises in the project in some magnitude to meet demand in other dimensions. The compromises in the system incur a "debt" which has to be repaid at some point for the long term health of the project. If the debt remains unpaid, it could incur more additional costs, in terms of software that is harder to change and more error prone. This pain is most evident to the software practitioners, as they are the ones' who have to deal with these problems at the code level.
We have conducted an interview study of software practitioners to analyze and understand how they face this debt and how they manage it. The result of this study identifies the characteristics, causes, and approaches for management of technical debt. As a result of analysis of the data for this study we also present several models of the cause and effect of different types of technical debt. These models also provide an understanding upon which approaches to track, measure, quantify and monitor technical debt can be developed.
|Commitee:||Hurst, Amy, Sampath, Sreedevi|
|School:||University of Maryland, Baltimore County|
|School Location:||United States -- Maryland|
|Source:||MAI 50/04M, Masters Abstracts International|
|Subjects:||Information science, Computer science|
|Keywords:||Interview study, Qualitative research, Software maintenance, Software project management, Software quality, Technical debt|
Copyright in each Dissertation and Thesis is retained by the author. All Rights Reserved
The supplemental file or files you are about to download were provided to ProQuest by the author as part of a
dissertation or thesis. The supplemental files are provided "AS IS" without warranty. ProQuest is not responsible for the
content, format or impact on the supplemental file(s) on our system. in some cases, the file type may be unknown or
may be a .exe file. We recommend caution as you open such files.
Copyright of the original materials contained in the supplemental file is retained by the author and your access to the
supplemental files is subject to the ProQuest Terms and Conditions of use.
Depending on the size of the file(s) you are downloading, the system may take some time to download them. Please be