Which documentation for software maintenance?

Souza, Sergio Cozzetti B. de; Anquetil, Nicolas; Oliveira, Káthia Marçal de

doi:10.1007/bf03194494

“…In many empirical studies selected in this study, the source code was used to identify the TD. However, the code comments also help developers to understand the code source [11,12]. That reason leads some researchers to use code comments to identify Self-Admitted Technical Debt (SATD) [8,9,10].…”

Section: Introductionmentioning

confidence: 99%

Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study

BenIdris

¹

2020

SSRN Journal

0

View full text Add to dashboard Cite

Context: Technical Debt (TD) is a metaphor that refers to short-term solutions in software development that may affect the cost to the software development life cycle. Objective: To explore and understand TDrelated to the software industry as well as an overview on the current state of TD research. Forty-three TD empirical studies were collected for classification and analyzation. Goals: Classify TD types, find the indicators used to detect TD, find the estimators used to quantify the TD, evaluate how researchers investigate TD. Method: By performing a systematic mapping study to identify and analyze the TD empirical studies which published between 2014 and 2017. Results: We present the most common indicators and evaluators to identify and evaluate the TD, and we gathered thirteen types of TD. We showed some ways to investigate the TD, and used tools in the selected studies. Conclusion: The outcome of our systematic mapping study can help researchers to identify interestand future in TD.

show abstract

“…In many empirical studies selected in this study, the source code was used to identify the TD. However, the code comments also help developers to understand the code source [11,12]. That reason leads some researchers to use code comments to identify Self-Admitted Technical Debt (SATD) [8,9,10].…”

Section: Introductionmentioning

confidence: 99%

Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study

BenIdris¹,

Ammar²,

Dzielski³

2018

IJSEA

View full text Add to dashboard Cite

Context: Technical Debt (TD) is a metaphor that refers to short-term solutions in software development that may affect the cost to the software development life cycle. Objective: To explore and understand TDrelated to the software industry as well as an overview on the current state of TD research. Forty-three TD empirical studies were collected for classification and analyzation. Goals: Classify TD types, find the indicators used to detect TD, find the estimators used to quantify the TD, evaluate how researchers investigate TD. Method: By performing a systematic mapping study to identify and analyze the TD empirical studies which published between 2014 and 2017. Results: We present the most common indicators and evaluators to identify and evaluate the TD, and we gathered thirteen types of TD. We showed some ways to investigate the TD, and used tools in the selected studies. Conclusion: The outcome of our systematic mapping study can help researchers to identify interestand future in TD.

show abstract

Software Redocumentation Using Distributed Data Processing Technique to Support Program Understanding for Legacy System: A Proposed Approach

Nallusamy¹,

Hao²,

Zulkifle³

2021

Advances in Visual Informatics

0

View full text Add to dashboard Cite

Which documentation for software maintenance?

Cited by 16 publications

References 17 publications

Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study

Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study

Investigate, Identify and Estimate the Technical Debt: A Systematic Mapping Study

Software Redocumentation Using Distributed Data Processing Technique to Support Program Understanding for Legacy System: A Proposed Approach

Contact Info

Product

Resources

About