Experiences on Managing Technical Debt with Code Smells and AntiPatterns

Show simple item record

dc.contributor.author Ramirez Lahti, Jacinto
dc.contributor.author Tuovinen, Antti-Pekka
dc.contributor.author Mikkonen, Tommi
dc.date.accessioned 2021-09-16T09:05:01Z
dc.date.available 2021-09-16T09:05:01Z
dc.date.issued 2021-06-25
dc.identifier.citation 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
dc.identifier.citation conference
dc.identifier.other PURE: 168479106
dc.identifier.other PURE UUID: 04747faf-4673-4741-9881-751a416c00d8
dc.identifier.other ORCID: /0000-0002-1092-4157/work/100083725
dc.identifier.other ORCID: /0000-0002-8540-9918/work/100085045
dc.identifier.other WOS: 000695315600005
dc.identifier.uri http://hdl.handle.net/10138/334412
dc.description.abstract 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. en
dc.format.extent 9
dc.language.iso eng
dc.publisher IEEE
dc.relation.ispartof 2021 IEEE/ACM International Conference on Technical Debt (TechDebt)
dc.relation.isversionof 978-1-6654-1405-0
dc.rights unspecified
dc.rights.uri info:eu-repo/semantics/closedAccess
dc.subject 113 Computer and information sciences
dc.subject Technical debt, code smells, AntiPatterns, case study, software maintenance, code refactoring
dc.subject Technical debt
dc.subject code smells
dc.subject AntiPatterns
dc.subject case study
dc.subject software maintenance
dc.subject code refactoring
dc.title Experiences on Managing Technical Debt with Code Smells and AntiPatterns en
dc.type Conference contribution
dc.contributor.organization Department of Computer Science
dc.contributor.organization Empirical Software Engineering research group
dc.description.reviewstatus Peer reviewed
dc.relation.doi https://doi.org/10.1109/TechDebt52882.2021.00013
dc.rights.accesslevel closedAccess
dc.type.version submittedVersion
dc.identifier.url https://arxiv.org/abs/2103.11486

Files in this item

Total number of downloads: Loading...

Files Size Format View
2103.11486.pdf 1.336Mb PDF View/Open

This item appears in the following Collection(s)

Show simple item record