Code Smell DataSet

Citation Author(s):
Ali
Nizam
Fatih Sultan Mehmet Vakıf Üniversitesi
Ömer Kerem
Adalı
Fatih Sultan Mehmet Vakıf Üniversitesi
Ertuğrul
İslamoğlu
Fatih Sultan Mehmet Vakıf Üniversitesi
Submitted by:
Ali Nizam
Last updated:
Wed, 12/25/2024 - 13:39
DOI:
10.21227/j0rn-ht76
Data Format:
License:
0
0 ratings - Please login to submit your rating.

Abstract 

This dataset contains information about code smell, which is a very important issue in software engineering. 

It is built by collecting the method having code smell from GitHub using the SonarCloud tool.

There are 5 code smells and 1 normal class with 500 examples each.

the metadata: method (function),smellkey, smellid

Smell Type

ID

Description

Reference

java:S100

0

Method names should comply with a naming convention to allow teams to collaborate efficiently.

https://rules.sonarsource.com/java/RSPEC-100/

java:S1161

1

"@Override" should be used on overriding and implementing methods to improve readability

https://rules.sonarsource.com/java/RSPEC-1161/

java:S1452

2

Generic wildcard types should not be used in return types to prevent  returning a more general type than the method’s return type

https://rules.sonarsource.com/java/RSPEC-1452/

 

java:S119

3

Type parameter names should comply with a naming convention to increase team collaboration.

https://rules.sonarsource.com/java/RSPEC-119/

java:S1172

4

Unused method parameters should be removed to prevent confusion

https://rules.sonarsource.com/java/RSPEC-1172/

Without smell

5

Does not contain any smell

 -

 

 

 

 

 

Instructions: 

the metadata: method (function),smellkey, smellid

 

Funding Agency: 
TÜBİTAK
Grant Number: 
123E020