Proceedings of the 2017 5th International Conference on Machinery, Materials and Computing Technology (ICMMCT 2017) 2017
DOI: 10.2991/icmmct-17.2017.120
|View full text |Cite
|
Sign up to set email alerts
|

The detection of code smell on software development: a mapping study

Abstract: Abstract.Context: Although Code Smell can't cause problems with execution of project code, Code Smell can cause some potential problems of maintainability and understandability on the software projects. Meanwhile, as for the research of code smell, current research results pay attention to only several specific Code Smells, and then don't have a comprehensive detection on Code Smell. Objective: To investigate what the objective of Code Smell study is, and to find what kinds of code smells could the detection t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(7 citation statements)
references
References 18 publications
0
4
0
Order By: Relevance
“…There are many tools and techniques available for detecting code smells like JDeodrant, 28 InCode, [29][30][31] JCodeOdor, 32 DLFinder, 33 Arcan, 34 FindSmells, 35 JSpIRIT, 13 Risk-based code smells detector, 36 iPlasma, Checkstyle, PMD, inFusion, and StenchBlossm. 37 These tools extract structural information, architectural blueprints, or change history information from the source code for detecting code smells. [38][39][40][41][42][43] The code smells detected by the different tools mentioned above are given in Table 2.…”
Section: Alternative Classes With Different Interfacesmentioning
confidence: 99%
“…There are many tools and techniques available for detecting code smells like JDeodrant, 28 InCode, [29][30][31] JCodeOdor, 32 DLFinder, 33 Arcan, 34 FindSmells, 35 JSpIRIT, 13 Risk-based code smells detector, 36 iPlasma, Checkstyle, PMD, inFusion, and StenchBlossm. 37 These tools extract structural information, architectural blueprints, or change history information from the source code for detecting code smells. [38][39][40][41][42][43] The code smells detected by the different tools mentioned above are given in Table 2.…”
Section: Alternative Classes With Different Interfacesmentioning
confidence: 99%
“…They aimed to provide a concise summary of these tools, highlighting their main features and effectiveness in detecting bad smells. Liu and Zhang [18] conducted a mapping study to scrutinize the purpose of code smell research and the scope of detection tools. They delved into the empirical software engineering context to determine if the available detection tools could identify all types of code smells.…”
Section: Related Workmentioning
confidence: 99%
“…Major instances of technical debt include code smells and ineffective design decisions made by developers, which can have a negative impact on the maintainability, scalability, and quality of a software system [4]. Over the past few decades, research has heavily focused on the following areas [5]:…”
Section: Introductionmentioning
confidence: 99%
“…In the software engineering industry, extensive research has been conducted to identify code smells within codebases during software development and investigate their impact and various dimensions. Rulebased or static code analysis tools are increasingly popular [5]. By using intelligent code smell analysis and detection systems, the system would be able to adapt and update rules and sequences based on new changes, enabling it to predict or identify code smells in advance [6].…”
mentioning
confidence: 99%