Published Papers - IHARA Akinori

自動生成されたパッチがコーディング規約に与える影響の分析

野口優輝, 木村祐太, 伊原彰紀, 大平雅雄

情報処理学会論文誌     2025.01  [Refereed]

Detecting Software Library Version with Backward Compatibility Loss based on Test Code Changes

Akinori Ihara, Daiki Maekawa, Kazuki Matsuda （Part： Lead author,　Corresponding author )

情報処理学会論文誌     2025  [Refereed]

相関関係の効率的な解釈を支援するための遅延相関分析手法の拡張：プロジェクト管理への活用に向けた適用実験

市井誠, 堀口日向, 柏祐太郎, 川上真澄, 伊原彰紀, 大平雅雄

情報処理学会論文誌   64 ( 7 )   2023.07  [Refereed]

Predicting Proficiency Level for Scratch Users Based on Computational Thinking

Ryota Ando, Akinori Ihara （Part： Corresponding author )

情報処理学会論文誌   63 ( 4 ) 928 - 937   2022.04  [Refereed]

Code Reviews With Divergent Review Scores: An Empirical Study of the OpenStack and Qt Communities

Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto （Part： Corresponding author )

IEEE Transactions on Software Engineering ( Institute of Electrical and Electronics Engineers ({IEEE}) )  48 ( 1 ) 69 - 81   2022.01  [Refereed]

DOI

SōjiTantei: Function-Call Reachability Detection of Vulnerable Code for npm Packages.

Bodin Chinthanet, Raula Gaikovina Kula, Rodrigo Eliza Zapata, Takashi Ishio, Kenichi Matsumoto, Akinori Ihara

IEICE Transactions on Information and Systems   105 ( 1 ) 19 - 20   2022.01  [Refereed]

DOI

Linkage of Similar Code Snippets Assessed in the Micro Benchmark Service jsPerf.

Kazuya Saiki, Akinori Ihara （Part： Corresponding author )

Proceedings of the International Working Conference on Source Code Analysis and Manipulation (SCAM)     247 - 251   2021.09  [Refereed]

DOI

Early Identification of Active Developers Based on their Past Contributions in OSS Projects.

Tomoki Koguchi, Akinori Ihara （Part： Corresponding author )

22nd IEEE/ACIS International Fall Virtual Conference on SoftwareEngineering, Artificial Intelligence, Networking and Parallel/Distributed Computing (SNPD)     230 - 235   2021.09  [Refereed]

DOI

Lags in the release, adoption, and propagation of npm vulnerability fixes.

Bodin Chinthanet, Raula Gaikovina Kula, Shane McIntosh, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto （Part： Corresponding author )

Journal of Empirical Software Engineering   26 ( 3 ) 47 - 47   2021.03  [Refereed]

DOI

ソフトウェアオープン化時代に向けたソースコード自動検証技術の開発

伊原彰紀 （Part： Lead author )

テレコム先端技術研究支援センター 技術情報誌TELECOM FRONTIER     1 - 4   2020.08  [Invited]

Analysis of Prevalent Code Improvements through Code Review

上田裕己, 石尾隆, 伊原彰紀, 松本健一 （Part： Corresponding author )

コンピュータソフトウェア   37 ( 2 )   2020.05  [Refereed]

Understanding Developer Commenting in Code Reviews

Toshiki Hirao, Raula Gaikovina Kula, Akinori Ihara, Kenichi Matsumoto （Part： Corresponding author )

IEICE Transactions on Information and Systems   E102-D ( 12 ) 2423 - 2432   2019.12  [Refereed]

DOI

The Review Linkage Graph for Code Review Analytics

Hirao Toshiki, McIntosh Shane, Ihara Akinori, Matsumoto Kenichi （Part： Corresponding author )

Proceedings of the 27th ACM Joint Meeting On European Software Engineering Conference And Symposium on the Foundations of Software Engineering     578 - 589   2019.08  [Refereed]

DOI

Identifying and predicting key features to support bug reporting.

Md. Rejaul Karim, Akinori Ihara, Eunjong Choi, Hajimu Iida （Part： Corresponding author )

Journal of Software Evolution and Process   31 ( 12 ) 1 - 24   2019.05  [Refereed]

DOI

Impact of coding style checker on code review - A case study on the openstack projects

Yuki Ueda, Akinori Ihara, Takashi Ishio, Kennichi Matsumoto （Part： Corresponding author )

Proceedings - 2018 9th International Workshop on Empirical Software Engineering in Practice, IWESEP 2018 ( Institute of Electrical and Electronics Engineers Inc. )    31 - 36   2019.03  [Refereed]

　View Summary

Code review is key to ensuring the absence of potential issues in source code. Code review is changing from a costly manual check by reviewer to a cost-efficient automatic check by coding style checkers. So that patch authors can verify the changed code before submitting their patches. Although cost-efficiency, the checkers do not detect all potential issues, requiring reviewers to verify the submitted patches based on their knowledge. It would be most efficient if patch authors will learn potential issues and remove the same type of issues from patches prior to code review. This study investigates potential issues that patch authors have repeatedly introduced in their patch submissions despite receiving feedback. To understand the impact of adopting checkers to patch authors' coding style improvement, this study compares two types of potential issues: Automatically Detected Issues by checkers (ADIs) and Manually Detected Issues by reviewers (MDIs). In a case study using an OpenStack code review dataset, we found that the patch authors have repeatedly introduced the same type of MDIs, while they do not repeat ADIs. This result suggests that the introduction of code style checkers might promote the patch authors' effective potential issues learning.

DOI

On The Lag of Library Vulnerability Updates: An Investigation into the Repackage and Delivery of Security Fixes Within The npm JavaScript Ecosystem.

Bodin Chinthanet, Raula Gaikovina Kula, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto

CoRR   abs/1907.03407   2019  [Refereed]

Mining Source Code Improvement Patterns from Similar Code Review Works

Ueda Yuki, Ishio Takashi, Ihara Akinori, Matsumoto Kenichi （Part： Corresponding author )

2019 IEEE 13TH INTERNATIONAL WORKSHOP ON SOFTWARE CLONES (IWSC '19)     13 - 19   2019  [Refereed]

The Impact of Human Factors on the Participation Decision of Reviewers in Modern Code Review.

Shade Ruangwan, Patanamon Thongtanunam, Akinori Ihara, Kenichi Matsumoto （Part： Corresponding author )

Journal of Empirical Software Engineering   24 ( 2 ) 973 - 1016   2019  [Refereed]

What Are the Perception Gaps Between FLOSS Developers and SE Researchers? A Case of Bug Finding Research

Yutaro Kashiwa, Akinori Ihara, Masao Ohira （Part： Corresponding author )

Proceedings of the International Conference on Open Source Systems (OSS) 2019 ( SPRINGER INTERNATIONAL PUBLISHING AG )  556   44 - 57   2019  [Refereed]

　View Summary

In recent years, many researchers in the SE community have been devoting considerable efforts to provide FLOSS developers with a means to quickly find and fix various kinds of bugs in FLOSS products such as security and performance bugs. However, it is not exactly sure how FLOSS developers think about bugs to be removed preferentially. Without a full understanding of FLOSS developers' perceptions of bug finding and fixing, researchers' efforts might remain far away from FLOSS developers' needs. In this study, we interview 322 notable GitHub developers about high impact bugs to understand FLOSS developers' needs for bug finding and fixing, and we manually inspect and classify developers' answers (bugs) by symptoms and root causes of bugs. As a result, we show that security and breakage bugs are highly crucial for FLOSS developers. We also identify what kinds of high impact bugs should be studied newly by the SE community to help FLOSS developers.

DOI

An Empirical Study of README contents for JavaScript Packages.

Shohei Ikeda, Akinori Ihara, Raula Gaikovina Kula, Kenichi Matsumoto （Part： Corresponding author )

IEICE Transactions on Information and Systems   102-D ( 2 ) 280 - 288   2019  [Refereed]

DOI