Answers are grounded in this paper and cite their sources.
Documentation technical debt typically is related to non-existent, inconsistent, outdated, unnecessary, or incomplete documentation. Such problems may lead to negative consequences to the software product development and maintenance endeavors, for instance, difficulties identifying and removing defects and increased cost and effort to deploy new versions. We followed Design Science Research principles to create DOTED, a method for managing Documentation Technical Debt on software products. We present a case study to evaluate DOTED viability in supporting the management of this type of technical debt. The study participants highlighted its benefits and reported the intention of future use. We also found that DOTED may be more effective in fostering technical debt repayment if used early and continuously on the product’s development lifecycle.
No takes yet. Share an insight, caveat, or question.
Mendes et al. (2024) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: