activity
20172021
most citedPredicting Defective Lines Using a Model-Agnostic Technique

138 citations · 475 across the 33 of their papers we have counts for

collaborators

35 papers

cs.SE2021★ 1 cited

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

Bodin Chinthanet, Raula Gaikovina Kula, Rodrigo Eliza Zapata +3

It has become common practice for software projects to adopt third-party dependencies. Developers are encouraged to update any outdated dependency to remain safe from potential thr…

cs.SE2021★ 4 cited

An Exploration of npm Package Co-Usage Examples from Stack Overflow: A Case Study

Syful Islam, Dong Wang, Raula Gaikovina Kula +2

Third-party package usage has become a common practice in contemporary software development. Developers often face different challenges, including choosing the right libraries, ins…

cs.SE2021★ 4 cited

What makes a good Node.js package? Investigating Users, Contributors, and Runnability

Bodin Chinthanet, Brittany Reid, Christoph Treude +4

The Node.js Package Manager (i.e., npm) archive repository serves as a critical part of the JavaScript community and helps support one of the largest developer ecosystems in the wo…

cs.SE2021

Automatic Patch Linkage Detection in Code Review Using TextualContent and File Location Features

Dong Wang, Raula Gaikovina Kula, Takashi Ishio +1

Context: Contemporary code review tools are a popular choice for software quality assurance. Using these tools, reviewers are able to post a linkage between two patches during a re…

cs.SE2021★ 19 cited

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

Toshiki Hirao, Shane McIntosh, Akinori Ihara +1

Code review is a broadly adopted software quality practice where developers critique each others' patches. In addition to providing constructive feedback, reviewers may provide a s…

cs.SE2021

Does the First Response Matter for Future Contributions? A Study of First Contributions

Noppadol Assavakamhaenghan, Supatsara Wattanakriengkrai, Naomichi Shimada +3

Open Source Software (OSS) projects rely on a continuous stream of new contributors for their livelihood. Recent studies reported that new contributors experience many barriers in…

cs.SE2021

FLOSS != GitHub: A Case Study of Linux/BSD Perceptions from Microsoft's Acquisition of GitHub

Raula Gaikovina Kula, Hideki Hata, Kenichi Matsumoto

In 2018, the software industry giants Microsoft made a move into the Open Source world by completing the acquisition of mega Open Source platform, GitHub. This acquisition was not…

cs.SE2021★ 23 cited

Characterizing and Mitigating Self-Admitted Technical Debt in Build Systems

Tao Xiao, Dong Wang, Shane McIntosh +4

Technical Debt is a metaphor used to describe the situation in which long-term software artifact quality is traded for short-term goals in software projects. In recent years, the c…

cs.SE2020

Automated Identification of On-hold Self-admitted Technical Debt

Rungroj Maipradit, Bin Lin, Csaba Nagy +4

Modern software is developed under considerable time pressure, which implies that developers more often than not have to resort to compromises when it comes to code that is well wr…

cs.SE2020★ 138 cited

Predicting Defective Lines Using a Model-Agnostic Technique

Supatsara Wattanakriengkrai, Patanamon Thongtanunam, Chakkrit Tantithamthavorn +2

Defect prediction models are proposed to help a team prioritize source code areas files that need Software QualityAssurance (SQA) based on the likelihood of having defects. However…

cs.SE2020★ 4 cited

Code-based Vulnerability Detection in Node.js Applications: How far are we?

Bodin Chinthanet, Serena Elisa Ponta, Henrik Plate +4

With one of the largest available collection of reusable packages, the JavaScript runtime environment Node.js is one of the most popular programming application. With recent work s…

cs.SE2020★ 3 cited

Newcomer Candidate: Characterizing Contributions of a Novice Developer to GitHub

Ifraz Rehman, Dong Wang, Raula Gaikovina Kula +2

Context: To attract, onboard, and retain any new-comer in Open Source Software (OSS) projects is vital to their livelihood. Recent studies conclude that OSS projects risk failure d…

cs.SE2020★ 3 cited

DevReplay: Automatic Repair with Editable Fix Pattern

Yuki Ueda, Takashi Ishio, Akinori Ihara +1

Static analysis tools, or linters, detect violation of source code conventions to maintain project readability. Those tools automatically fix specific violations while developers e…

cs.SE2020

A Simulation Study of Bandit Algorithms to Address External Validity of Software Fault Prediction

Teruki Hayakawa, Masateru Tsunoda, Koji Toda +2

Various software fault prediction models and techniques for building algorithms have been proposed. Many studies have compared and evaluated them to identify the most effective one…

cs.SE2019★ 2 cited

Can We Benchmark Code Review Studies? A Systematic Mapping Study of Methodology, Dataset, and Metric

Dong Wang, Yuki Ueda, Raula Gaikovina Kula +2

Code Review (CR) is the cornerstone for software quality assurance and a crucial practice for software development. As CR research matures, it can be difficult to keep track of the…

cs.SE2019★ 6 cited

From Academia to Software Development: Publication Citations in Source Code Comments

Akira Inokuchi, Yusuf Sulistyo Nugroho, Supatsara Wattanakriengkrai +5

Academic publications have been evaluated in terms of their impact on research communities based on many metrics, such as the number of citations. On the other hand, the impact of…

cs.SE2019★ 5 cited

Towards Generation of Visual Attention Map for Source Code

Takeshi D. Itoh, Takatomi Kubo, Kiyoka Ikeda +5

Program comprehension is a dominant process in software development and maintenance. Experts are considered to comprehend the source code efficiently by directing their gaze, or at…

cs.SE2019

Identifying Algorithm Names in Code Comments

Jakapong Klainongsuang, Yusuf Sulistyo Nugroho, Hideaki Hata +4

For recent machine-learning-based tasks like API sequence generation, comment generation, and document generation, large amount of data is needed. When software developers implemen…

cs.SE2019★ 60 cited

Lags in the Release, Adoption, and Propagation of npm Vulnerability Fixes

Bodin Chinthanet, Raula Gaikovina Kula, Shane McIntosh +3

Security vulnerability in third-party dependencies is a growing concern not only for developers of the affected software, but for the risks it poses to an entire software ecosystem…

cs.IR2019★ 3 cited

Sentiment Classification using N-gram IDF and Automated Machine Learning

Rungroj Maipradit, Hideaki Hata, Kenichi Matsumoto

We propose a sentiment classification method with a general machine learning framework. For feature representation, n-gram IDF is used to extract software-engineering-related, data…

cs.SE2019★ 34 cited

A Topological Analysis of Communication Channels for Knowledge Sharing in Contemporary GitHub Projects

Jirateep Tantisuwankul, Yusuf Sulistyo Nugroho, Raula Gaikovina Kula +4

With over 28 million developers, success of the GitHub collaborative platform is highlighted through an abundance of communication channels among contemporary software projects. Kn…

cs.SE2019★ 1 cited

Toward Imitating Visual Attention of Experts in Software Development Tasks

Yoshiharu Ikutani, Nishanth Koganti, Hideaki Hata +2

Expert programmers' eye-movements during source code reading are valuable sources that are considered to be associated with their domain expertise. We advocate a vision of new inte…

cs.SE2019★ 55 cited

How Different Are Different diff Algorithms in Git?

Yusuf Sulistyo Nugroho, Hideaki Hata, Kenichi Matsumoto

Automatic identification of the differences between two versions of a file is a common and basic task in several applications of mining code repositories. Git, a version control sy…

cs.SE2019★ 1 cited

Wait For It: Identifying "On-Hold" Self-Admitted Technical Debt

Rungroj Maipradit, Christoph Treude, Hideaki Hata +1

Self-admitted technical debt refers to situations where a software developer knows that their current implementation is not optimal and indicates this using a source code comment.…