default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDAkinori Ihara
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2024
[j14]Akinori Ihara:
Foreword. IEICE Trans. Inf. Syst. 107(3): 244 (2024)- 2022
- [j13]Bodin Chinthanet, Raula Gaikovina Kula
, Rodrigo Eliza Zapata, Takashi Ishio, Kenichi Matsumoto, Akinori Ihara:
SōjiTantei: Function-Call Reachability Detection of Vulnerable Code for npm Packages. IEICE Trans. Inf. Syst. 105-D(1): 19-20 (2022) - [j12]Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto:
Code Reviews With Divergent Review Scores: An Empirical Study of the OpenStack and Qt Communities. IEEE Trans. Software Eng. 48(2): 69-81 (2022) - 2021
- [j11]Bodin Chinthanet, Raula Gaikovina Kula, Shane McIntosh, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto:
Lags in the release, adoption, and propagation of npm vulnerability fixes. Empir. Softw. Eng. 26(3): 47 (2021) - [c39]Kazuya Saiki, Akinori Ihara:
Linkage of Similar Code Snippets Assessed in the Micro Benchmark Service jsPerf. SCAM 2021: 247-251 - [c38]Tomoki Koguchi, Akinori Ihara:
Early Identification of Active Developers Based on their Past Contributions in OSS Projects. SNPD 2021: 230-235 - [i8]Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto:
Code Reviews with Divergent Review Scores: An Empirical Study of the OpenStack and Qt Communities. CoRR abs/2104.01537 (2021) - [i7]Bodin Chinthanet, Raula Gaikovina Kula, Rodrigo Eliza Zapata, Takashi Ishio, Kenichi Matsumoto, Akinori Ihara:
SōjiTantei: Function-Call Reachability Detection of Vulnerable Code for npm Packages. CoRR abs/2109.08931 (2021) - 2020
- [i6]Yuki Ueda, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto:
DevReplay: Automatic Repair with Editable Fix Pattern. CoRR abs/2005.11040 (2020)
2010 – 2019
- 2019
- [j10]Shade Ruangwan, Patanamon Thongtanunam, Akinori Ihara, Kenichi Matsumoto:
The impact of human factors on the participation decision of reviewers in modern code review. Empir. Softw. Eng. 24(2): 973-1016 (2019) - [j9]Shohei Ikeda, Akinori Ihara, Raula Gaikovina Kula, Kenichi Matsumoto:
An Empirical Study of README contents for JavaScript Packages. IEICE Trans. Inf. Syst. 102-D(2): 280-288 (2019) - [j8]Toshiki Hirao, Raula Gaikovina Kula, Akinori Ihara, Kenichi Matsumoto:
Understanding Developer Commenting in Code Reviews. IEICE Trans. Inf. Syst. 102-D(12): 2423-2432 (2019) - [j7]Md. Rejaul Karim, Akinori Ihara, Eunjong Choi, Hajimu Iida:
Identifying and predicting key features to support bug reporting. J. Softw. Evol. Process. 31(12) (2019) - [c37]Yuki Ueda, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto:
Mining Source Code Improvement Patterns from Similar Code Review Works. IWSC 2019: 13-19 - [c36]Yutaro Kashiwa, Akinori Ihara, Masao Ohira:
What Are the Perception Gaps Between FLOSS Developers and SE Researchers? - A Case of Bug Finding Research. OSS 2019: 44-57 - [c35]Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto:
The review linkage graph for code review analytics: a recovery approach and empirical study. ESEC/SIGSOFT FSE 2019: 578-589 - [i5]Bodin Chinthanet, Raula Gaikovina Kula, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto:
On The Lag of Library Vulnerability Updates: An Investigation into the Repackage and Delivery of Security Fixes Within The npm JavaScript Ecosystem. CoRR abs/1907.03407 (2019) - 2018
- [j6]Kanyakorn Jewmaidang, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto, Pattara Leelaprute:
Extraction of Library Update History Using Source Code Reuse Detection. IEICE Trans. Inf. Syst. 101-D(3): 799-802 (2018) - [j5]Yuki Ueda, Akinori Ihara, Takashi Ishio, Toshiki Hirao, Kenichi Matsumoto:
How are IF-Conditional Statements Fixed Through Peer CodeReview? IEICE Trans. Inf. Syst. 101-D(11): 2720-2729 (2018) - [j4]Chakkrit Tantithamthavorn, Surafel Lemma Abebe, Ahmed E. Hassan, Akinori Ihara, Kenichi Matsumoto:
The impact of IR-based classifier configuration on the performance and the effort of method-level bug localization. Inf. Softw. Technol. 102: 160-174 (2018) - [c34]Takuto Norikane, Akinori Ihara, Kenichi Matsumoto:
Do Review Feedbacks Influence to a Contributor's Time Spent on OSS Projects? BCD 2018: 109-113 - [c33]Farida Elzanaty, Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto:
An empirical study of design discussions in code review. ESEM 2018: 11:1-11:10 - [c32]Daiki Katsuragawa, Akinori Ihara, Raula Gaikovina Kula, Kenichi Matsumoto:
Maintaining third-party libraries through domain-specific category recommendations. SoHeal@ICSE 2018: 2-9 - [c31]Rodrigo Elizalde Zapata, Raula Gaikovina Kula, Bodin Chinthanet, Takashi Ishio, Kenichi Matsumoto, Akinori Ihara:
Towards Smoother Library Migrations: A Look at Vulnerable Dependency Migrations at Function Level for npm JavaScript Packages. ICSME 2018: 559-563 - [c30]Yuki Ueda, Akinori Ihara, Takashi Ishio, Ken-ichi Matsumoto:
Impact of Coding Style Checker on Code Review - A Case Study on the OpenStack Projects. IWESEP 2018: 31-36 - [i4]Shohei Ikeda, Akinori Ihara, Raula Gaikovina Kula, Kenichi Matsumoto:
An Empirical Study on README contents for JavaScript Packages. CoRR abs/1802.08391 (2018) - [i3]Chakkrit Tantithamthavorn, Surafel Lemma Abebe, Ahmed E. Hassan, Akinori Ihara, Kenichi Matsumoto:
The Impact of IR-based Classifier Configuration on the Performance and the Effort of Method-Level Bug Localization. CoRR abs/1806.07727 (2018) - [i2]Shade Ruangwan, Patanamon Thongtanunam, Akinori Ihara, Kenichi Matsumoto:
The Impact of Human Factors on the Participation Decision of Reviewers in Modern Code Review. CoRR abs/1806.10277 (2018) - 2017
- [c29]Hirohiko Suwa, Akinori Ihara, Raula Gaikovina Kula, Daiki Fujibayashi, Kenichi Matsumoto:
An Analysis of Library Rollbacks: A Case Study of Java Libraries. APSEC Workshops 2017: 63-70 - [c28]Yuki Ueda, Akinori Ihara, Toshiki Hirao, Takashi Ishio, Kenichi Matsumoto:
How is IF Statement Fixed Through Code Review? A Case Study of Qt Project. ISSRE Workshops 2017: 207-213 - [c27]Md. Rejaul Karim, Akinori Ihara, Xin Yang, Hajimu Iida, Kenichi Matsumoto:
Understanding Key Features of High-Impact Bug Reports. IWESEP 2017: 53-58 - [c26]Akinori Ihara, Daiki Fujibayashi, Hirohiko Suwa, Raula Gaikovina Kula, Kenichi Matsumoto:
Understanding When to Adopt a Library: A Case Study on ASF Projects. OSS 2017: 128-138 - [c25]Daiki Fujibayashi, Akinori Ihara, Hirohiko Suwa, Raula Gaikovina Kula, Ken-ichi Matsumoto:
Does the release cycle of a library project influence when it is adopted by a client project? SANER 2017: 569-570 - [c24]Takuto Norikane, Akinori Ihara, Kenichi Matsumoto:
Which review feedback did long-term contributors get on OSS projects? SANER 2017: 571-572 - [i1]Emad Shihab, Akinori Ihara:
Mining Software Repositories:Accomplishments, Challenges andFuture Trends (NII Shonan Meeting 2017-2). NII Shonan Meet. Rep. 2017 (2017) - 2016
- [c23]Jirayus Jiarpakdee, Akinori Ihara, Ken-ichi Matsumoto:
Understanding question quality through affective aspect in Q&A site. SEmotion@ICSE 2016: 12-17 - [c22]Norihito Kitagawa, Hideaki Hata, Akinori Ihara, Kiminao Kogiso, Ken-ichi Matsumoto:
Code review participation: game theoretical modeling of reviewers in gerrit datasets. CHASE@ICSE 2016: 64-67 - [c21]Yutaka Arakawa, Keiichi Yasumoto, Kenichi Matsumoto, Hideaki Hata, Hirohiko Suwa, Akinori Ihara, Manato Fujimoto:
Project IS^3: Incentive-Based Intelligent Intervention for Smart and Sustainable Society. IIAI-AAI 2016: 215-218 - [c20]Jirayus Jiarpakdee, Chakkrit Tantithamthavorn, Akinori Ihara, Kenichi Matsumoto:
A Study of Redundant Metrics in Defect Prediction Datasets. ISSRE Workshops 2016: 51-52 - [c19]Toshiki Hirao, Akinori Ihara, Yuki Ueda, Passakorn Phannachitta, Ken-ichi Matsumoto:
The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process. OSS 2016: 97-110 - 2015
- [c18]Toshiki Hirao, Akinori Ihara, Ken-ichi Matsumoto:
Pilot study of collective decision-making in the code review process. CASCON 2015: 248-251 - [c17]Chakkrit Tantithamthavorn, Shane McIntosh, Ahmed E. Hassan, Akinori Ihara, Ken-ichi Matsumoto:
The Impact of Mislabelling on the Performance and Interpretation of Defect Prediction Models. ICSE (1) 2015: 812-823 - [c16]Masao Ohira, Yutaro Kashiwa, Yosuke Yamatani, Hayato Yoshiyuki, Yoshiya Maeda, Nachai Limsettho, Keisuke Fujino, Hideaki Hata, Akinori Ihara, Ken-ichi Matsumoto:
A Dataset of High Impact Bugs: Manually-Classified Issue Reports. MSR 2015: 518-521 - 2014
- [c15]Chakkrit Tantithamthavorn, Akinori Ihara, Hideaki Hata, Kenichi Matsumoto:
Impact Analysis of Granularity Levels on Feature Location Technique. APRES 2014: 135-149 - [c14]Akinori Ihara, Akito Monden, Ken-ichi Matsumoto:
Industry Questions about Open Source Software in Business: Research Directions and Potential Answers. IWESEP 2014: 55-59 - [c13]Ryohei Takasawa, Kazunori Sakamoto, Akinori Ihara, Hironori Washizaki, Yoshiaki Fukazawa:
Do Open Source Software Projects Conduct Tests Enough? PROFES 2014: 322-325 - 2013
- [j3]Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid M. Ibrahim, Masao Ohira, Bram Adams, Ahmed E. Hassan, Ken-ichi Matsumoto:
Studying re-opened bugs in open source software. Empir. Softw. Eng. 18(5): 1005-1042 (2013) - [c12]John Boaz Lee, Akinori Ihara, Akito Monden, Ken-ichi Matsumoto:
Patch Reviewer Recommendation in OSS Projects. APSEC (2) 2013: 1-6 - [c11]Chakkrit Tantithamthavorn, Rattamont Teekavanich, Akinori Ihara, Ken-ichi Matsumoto:
Mining A change history to quickly identify bug locations : A case study of the Eclipse project. ISSRE (Supplemental Proceedings) 2013: 108-113 - [c10]Hironori Hayashi, Akinori Ihara, Akito Monden, Ken-ichi Matsumoto:
Why is collaboration needed in OSS projects? a case study of eclipse project. SSE@ESEC/FSE 2013: 17-20 - [c9]Akinori Ihara, Yuji Tsuda, Ken-ichi Matsumoto:
What type of thread can get feedback in OSS user mailing list? SSE@ESEC/FSE 2013: 25-28 - [c8]Chakkrit Tantithamthavorn, Akinori Ihara, Ken-ichi Matsumoto:
Using Co-change Histories to Improve Bug Localization Performance. SNPD 2013: 543-548 - 2012
- [j2]Passakorn Phannachitta, Akinori Ihara, Pijak Jirapiwong, Masao Ohira, Ken-ichi Matsumoto:
An Algorithm for Gradual Patch Acceptance Detection in Open Source Software Repository Mining. IEICE Trans. Fundam. Electron. Commun. Comput. Sci. 95-A(9): 1478-1489 (2012) - [j1]Anakorn Jongyindee, Masao Ohira, Akinori Ihara, Ken-ichi Matsumoto:
Good or Bad Committers? - A Case Study of Committer's Activities on the Eclipse's Bug Fixing Process. IEICE Trans. Inf. Syst. 95-D(9): 2202-2210 (2012) - [c7]Akinori Ihara, Yasutaka Kamei, Akito Monden, Masao Ohira, Jacky Wai Keung, Naoyasu Ubayashi, Ken-ichi Matsumoto:
An Investigation on Software Bug-Fix Prediction for Open Source Software Projects - A Case Study on the Eclipse Project. APSEC Workshops 2012: 112-119 - [c6]Phiradet Bangcharoensap, Akinori Ihara, Yasutaka Kamei, Ken-ichi Matsumoto:
Locating Source Code to Be Fixed Based on Initial Bug Reports - A Case Study on the Eclipse Project. IWESEP 2012: 10-15 - 2011
- [c5]Passakorn Phannachitta, Pijak Jirapiwong, Akinori Ihara, Masao Ohira, Ken-ichi Matsumoto:
An Analysis of Gradual Patch Application: A Better Explanation of Patch Acceptance. IWSM/Mensura 2011: 106-115 - [c4]Anakorn Jongyindee, Masao Ohira, Akinori Ihara, Ken-ichi Matsumoto:
Good or Bad Committers? A Case Study of Committers' Cautiousness and the Consequences on the Bug Fixing Process in the Eclipse Project. IWSM/Mensura 2011: 116-125 - 2010
- [c3]Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid M. Ibrahim, Masao Ohira, Bram Adams, Ahmed E. Hassan, Ken-ichi Matsumoto:
Predicting Re-opened Bugs: A Case Study on the Eclipse Project. WCRE 2010: 249-258
2000 – 2009
- 2009
- [c2]Akinori Ihara, Masao Ohira, Ken-ichi Matsumoto:
An analysis method for improving a bug modification process in open source software development. EVOL/IWPSE 2009: 135-144 - [c1]Masao Ohira, Kiwako Koyama, Akinori Ihara, Shinsuke Matsumoto, Yasutaka Kamei, Ken-ichi Matsumoto:
A Time-Lag Analysis for Improving Communication among OSS Developers. JSAI-isAI Workshops 2009: 135-146
Coauthor Index
aka: Kenichi Matsumoto
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from 
to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the 
of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from 
, 
, and 
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from 
.
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-12-26 01:51 CET by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by:
