The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. ex. Some numerals are expressed as "XNUMX".
Copyrights notice
The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. Copyrights notice
코드 냄새는 소스 코드의 설계 결함이나 문제를 나타내는 지표입니다. 코드 냄새를 탐지하기 위한 다양한 도구와 기술이 제안되었습니다. 이러한 도구는 일반적으로 많은 수의 코드 냄새를 감지하므로 코드 냄새의 우선 순위를 지정하고 필터링하기 위한 접근 방식도 개발되었습니다. 그러나 개발자가 코드 냄새를 필터링하고 우선순위를 지정하는 방법을 자세히 설명하는 경험적 데이터가 부족하면 이러한 접근 방식을 개선하는 데 방해가 됩니다. 본 연구에서는 전문 개발자 69명을 대상으로 50가지 작업 목록을 완료하는 조건으로 오픈소스 프로젝트에서 코드 냄새를 필터링하고 우선순위를 지정하는 데 사용하는 요소를 결정했습니다. 전문 개발자 XNUMX명으로부터 코드 냄새 필터링에 대한 응답은 총 XNUMX건, 코드 냄새 우선순위에 대한 응답은 XNUMX건이었습니다. 우리는 그것을 발견했습니다 작업 관련성 and 냄새 심각도 코드 냄새 필터링 중에 가장 일반적으로 고려되는 반면 모듈의 중요성 and 작업 관련성 코드 냄새 우선 순위 지정에 가장 자주 사용되었습니다. 이러한 결과는 코드 냄새 감지, 우선 순위 지정 및 필터링에 대한 추가 연구를 촉진하여 개발자의 실제 요구 사항에 더 집중할 수 있습니다.
Natthawute SAE-LIM
Tokyo Institute of Technology
Shinpei HAYASHI
Tokyo Institute of Technology
Motoshi SAEKI
Tokyo Institute of Technology
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
부
Natthawute SAE-LIM, Shinpei HAYASHI, Motoshi SAEKI, "An Investigative Study on How Developers Filter and Prioritize Code Smells" in IEICE TRANSACTIONS on Information,
vol. E101-D, no. 7, pp. 1733-1742, July 2018, doi: 10.1587/transinf.2017KBP0006.
Abstract: Code smells are indicators of design flaws or problems in the source code. Various tools and techniques have been proposed for detecting code smells. These tools generally detect a large number of code smells, so approaches have also been developed for prioritizing and filtering code smells. However, lack of empirical data detailing how developers filter and prioritize code smells hinders improvements to these approaches. In this study, we investigated ten professional developers to determine the factors they use for filtering and prioritizing code smells in an open source project under the condition that they complete a list of five tasks. In total, we obtained 69 responses for code smell filtration and 50 responses for code smell prioritization from the ten professional developers. We found that Task relevance and Smell severity were most commonly considered during code smell filtration, while Module importance and Task relevance were employed most often for code smell prioritization. These results may facilitate further research into code smell detection, prioritization, and filtration to better focus on the actual needs of developers.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.2017KBP0006/_p
부
@ARTICLE{e101-d_7_1733,
author={Natthawute SAE-LIM, Shinpei HAYASHI, Motoshi SAEKI, },
journal={IEICE TRANSACTIONS on Information},
title={An Investigative Study on How Developers Filter and Prioritize Code Smells},
year={2018},
volume={E101-D},
number={7},
pages={1733-1742},
abstract={Code smells are indicators of design flaws or problems in the source code. Various tools and techniques have been proposed for detecting code smells. These tools generally detect a large number of code smells, so approaches have also been developed for prioritizing and filtering code smells. However, lack of empirical data detailing how developers filter and prioritize code smells hinders improvements to these approaches. In this study, we investigated ten professional developers to determine the factors they use for filtering and prioritizing code smells in an open source project under the condition that they complete a list of five tasks. In total, we obtained 69 responses for code smell filtration and 50 responses for code smell prioritization from the ten professional developers. We found that Task relevance and Smell severity were most commonly considered during code smell filtration, while Module importance and Task relevance were employed most often for code smell prioritization. These results may facilitate further research into code smell detection, prioritization, and filtration to better focus on the actual needs of developers.},
keywords={},
doi={10.1587/transinf.2017KBP0006},
ISSN={1745-1361},
month={July},}
부
TY - JOUR
TI - An Investigative Study on How Developers Filter and Prioritize Code Smells
T2 - IEICE TRANSACTIONS on Information
SP - 1733
EP - 1742
AU - Natthawute SAE-LIM
AU - Shinpei HAYASHI
AU - Motoshi SAEKI
PY - 2018
DO - 10.1587/transinf.2017KBP0006
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E101-D
IS - 7
JA - IEICE TRANSACTIONS on Information
Y1 - July 2018
AB - Code smells are indicators of design flaws or problems in the source code. Various tools and techniques have been proposed for detecting code smells. These tools generally detect a large number of code smells, so approaches have also been developed for prioritizing and filtering code smells. However, lack of empirical data detailing how developers filter and prioritize code smells hinders improvements to these approaches. In this study, we investigated ten professional developers to determine the factors they use for filtering and prioritizing code smells in an open source project under the condition that they complete a list of five tasks. In total, we obtained 69 responses for code smell filtration and 50 responses for code smell prioritization from the ten professional developers. We found that Task relevance and Smell severity were most commonly considered during code smell filtration, while Module importance and Task relevance were employed most often for code smell prioritization. These results may facilitate further research into code smell detection, prioritization, and filtration to better focus on the actual needs of developers.
ER -