Experiences on Managing Technical Debt with Code Smells and AntiPatterns

Näytä kaikki kuvailutiedot



Pysyväisosoite

http://hdl.handle.net/10138/334412

Lähdeviite

Ramirez Lahti , J , Tuovinen , A-P & Mikkonen , T 2021 , Experiences on Managing Technical Debt with Code Smells and AntiPatterns . in 2021 IEEE/ACM International Conference on Technical Debt (TechDebt) . IEEE , pp. 36-44 , IEEE/ACM International Conference on Technical Debt , Madrid , Spain , 19/05/2021 . https://doi.org/10.1109/TechDebt52882.2021.00013

Julkaisun nimi: Experiences on Managing Technical Debt with Code Smells and AntiPatterns
Tekijä: Ramirez Lahti, Jacinto; Tuovinen, Antti-Pekka; Mikkonen, Tommi
Tekijän organisaatio: Department of Computer Science
Empirical Software Engineering research group
Julkaisija: IEEE
Päiväys: 2021-06-25
Kieli: eng
Sivumäärä: 9
Kuuluu julkaisusarjaan: 2021 IEEE/ACM International Conference on Technical Debt (TechDebt)
ISBN: 978-1-6654-1405-0
DOI-tunniste: https://doi.org/10.1109/TechDebt52882.2021.00013
URI: http://hdl.handle.net/10138/334412
Tiivistelmä: Technical debt has become a common metaphor for the accumulation of software design and implementation choices that seek fast initial gains but that are under par and counterproductive in the long run. However, as a metaphor, technical debt does not offer actionable advice on how to get rid of it. To get to a practical level in solving problems, more focused mechanisms are needed. Commonly used approaches for this include identifying code smells as quick indications of possible problems in the codebase and detecting the presence of AntiPatterns that refer to overt, recurring problems in design. There are known remedies for both code smells and AntiPatterns. In paper, our goal is to show how to effectively use common tools and the existing body of knowledge on code smells and AntiPatterns to detect technical debt and pay it back. We present two main results: (i) How a combination of static code analysis and manual inspection was used to detect code smells in a codebase leading to the discovery of AntiPatterns; and (ii) How AntiPatterns were used to identify, characterize, and fix problems in the software. The experiences stem from a private company and its long-lasting software product development effort.
Avainsanat: 113 Computer and information sciences
Technical debt, code smells, AntiPatterns, case study, software maintenance, code refactoring
Technical debt
code smells
AntiPatterns
case study
software maintenance
code refactoring
Vertaisarvioitu: Kyllä
Tekijänoikeustiedot: unspecified
Pääsyrajoitteet: closedAccess
Rinnakkaistallennettu versio: submittedVersion


Tiedostot

Latausmäärä yhteensä: Ladataan...

Tiedosto(t) Koko Formaatti Näytä
2103.11486.pdf 1.336MB PDF Avaa tiedosto

Viite kuuluu kokoelmiin:

Näytä kaikki kuvailutiedot