Code Smell Detection Tool for Java Script Programs

Almashfi, Nabil; Lu, Lunjin

doi:10.1109/icccs49078.2020.9118465

Cited by 6 publications

(14 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It was also observed the emergence of bad smells being adapted to Javascript as the year of publication progressed, such as Middle Man and Feature Envy, found only in the work of Almashfi, published in 2020 [1], and which may indicate new areas of interest in the language such as the structures of previously mentioned OO paradigm, promoting a greater incidence of smells not seen at the time of construction of this work.…”

Section: Interest In the Bad Smells Topic In Js Over The Yearsmentioning

confidence: 77%

“…Executing the search string defined in Section 2 in the search engine of the Scopus (Elsevier) database, a total of 16 items were returned. After applying the inclusion and exclusion criteria, 8 works were considered for analysis [1,7,14,16,19,20,22,24]. The other 8 items returned have been discarded; 7 of them because they are not works, but documents with the index of the annals of congresses where the works were published.…”

Section: Discussionmentioning

confidence: 99%

“…Middle Man When a class exists as an intermediator to call a feature that is already in another class [22] Negative Array index When the code tries to get a negative unit of the array [1] Primitive Property Assignment Use of primitive types to assign a variable [1]…”

Section: List Of Javascript Bad Smellsmentioning

confidence: 99%

“…According to data from a survey conducted by the Stack Overflow website, the language is the most used among all developers for 5 years in a row. 1 With the popularization of JS and its growing adoption in the development of web systems, it becomes increasingly important that systems developed with JS technologies are long-lived, i.e., able to evolve to remain useful over the years [18]. But as the system evolves, changes to its source code may deteriorate its evolution ability [4].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Bad Smells in Javascript - A Mapping Study

Barros¹,

Adachi²

2021

Anais Do IX Workshop De Visualização, Evolução E Manutenção De Software (VEM 2021)

View full text Add to dashboard Cite

Javascript is one of the most famous mainstream programming languages nowadays. It has gained considerable practical relevance over the last years, with applications in several areas, such as games, 3D rendering, and, mainly, web development. Like any other software system, systems developed in Javascript need to keep their ability to evolve to remain useful and relevant over time. Empirical evidence has shown that bad smells are possible indicators of problems hindering software evolvability. In this context, this paper presents a mapping study investigating if and to what extent bad smells have been defined for the Javascript language and how the interest in this topic has evolved. Our study identified 26 different types of bad smells investigated in the context of Javascript in 8 different works published between 2013 and 2020. This result suggests that although Javascript has gained practical relevance in recent years, there is still room for further empirical studies defining and evaluating the impact of bad smells on Javascript-based software systems.

show abstract

Section: Interest In the Bad Smells Topic In Js Over The Yearsmentioning

confidence: 77%

Section: Discussionmentioning

confidence: 99%

Section: List Of Javascript Bad Smellsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Bad Smells in Javascript - A Mapping Study

Barros¹,

Adachi²

2021

Anais Do IX Workshop De Visualização, Evolução E Manutenção De Software (VEM 2021)

View full text Add to dashboard Cite

show abstract

“…One way to detect possible code smells automatically is to use static source code analysis tools [11], [12], [13]. Static source code analysis tools analyze the source code without the need to compile and run it and there are different tools discerning different things in the code [14], [15], [16].…”

Section: A Code Smellsmentioning

confidence: 99%

Experiences on Managing Technical Debt with Code Smells and AntiPatterns

Lahti¹,

Tuovinen²,

Mikkonen³

2021

Preprint

View full text Add to dashboard Cite

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.

show abstract