Published Papers - OHIRA Masao

Automatic Repair Method for Dockerfile Build Errors: Extracting Dependencies Between Build Error-Inducing Instructions based on Frequent Subtree Mining

Renya Sakamoto, Masao Ohira （Part： Last author,　Corresponding author )

IEICE TRANSACTIONS on Information and Systems (in print)     2026.03  [Refereed]

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

野口 優輝, 木村 祐太, 伊原 彰紀, 大平 雅雄 （Part： Last author,　Corresponding author )

コンピュータ ソフトウェア   42 ( 1 ) 54 - 68   2025.02  [Refereed]

DOI

Building an Issue Classification Model on Technical Debt

Yuta Kimura, Masao Ohira （Part： Last author,　Corresponding author )

IPSJ Journal   64 ( 1 ) 2 - 12   2023.01  [Refereed]

Automating License Rule Generation to Help Maintain Rule-based OSS License Identification Tools

Yunosuke Higashi, Masao Ohira, Yuki Manabe （Part： Corresponding author )

Journal of Information Processing ( Information Processing Society of Japan )  31   2 - 12   2023.01  [Refereed]

DOI

単語分散表現による類義語統一と単語N-gramによるフレーズ抽出に基づくセキュリティ要件分類手法

宮崎 智己, 東 裕之輔, 大平 雅雄 （Part： Last author,　Corresponding author )

情報処理学会論文誌   63 ( 1 ) 94 - 103   2022.03  [Refereed]

A Release-Aware Bug Triaging Method Considering Developers' Bug-Fixing Loads

Yutaro Kashiwa, Masao Ohira （Part： Last author,　Corresponding author )

IEICE TRANSACTIONS ON INFORMATION AND SYSTEMS   E103D ( 2 ) 348 - 362   2020.02  [Refereed]

DOI

Hierarchical Clustering of OSS License Statements toward Automatic Generation of License Rules.

Yunosuke Higashi, Masao Ohira, Yutaro Kashiwa, Yuki Manabe 0001 （Part： Corresponding author )

JIP   27 ( 1 ) 42 - 50   2019  [Refereed]

　View Summary

Reusing open source software (OSS) components for one's own software products has become common in the modern software development. Automated license identification tools have been proposed to help developers identify OSS licenses, since a large number of licenses sometimes must be checked before attempting to reuse. Of the existing tools, Ninka[1] can most correctly identify licenses of each source file by using regular expressions. In case Ninka does not have license identification rules for unknown licenses, Ninka reports these as "unknown licenses" which must be checked by developers manually. Since completely-new or derived OSS licenses appear nearly every year, a license identification tool should be appropriately maintained by adding regular expressions corresponding to the new licenses. The final goal of our study is to construct a method to automatically create candidate license rules to be added to a license identification tool such as Ninka. Toward achieving the goal, files identified as unknown licenses must be classified by license firstly. In this paper, we propose a hierarchical clustering which divides unknown licenses into clusters of files with a single license. We conduct a case study to confirm the usefulness of our clustering method when it is applied for classifying 2,801, 1,230 and 2,446 unknown license statement files for Linux Kernel v4.4.6, FreeBSD v10.3.0 and Debian v7.8.0 respectively. As a result, it is confirmed that our method can create clusters which are suitable as candidates for generating license rules automatically.------------------------------This is a preprint of an article intended for publication Journal ofInformation Processing(JIP). This preprint should not be cited. Thisarticle should be cited as: Journal of Information Processing Vol.27(2019) (online)DOI http://dx.doi.org/10.2197/ipsjjip.27.42------------------------------Reusing open source software (OSS) components for one's own software products has become common in the modern software development. Automated license identification tools have been proposed to help developers identify OSS licenses, since a large number of licenses sometimes must be checked before attempting to reuse. Of the existing tools, Ninka[1] can most correctly identify licenses of each source file by using regular expressions. In case Ninka does not have license identification rules for unknown licenses, Ninka reports these as "unknown licenses" which must be checked by developers manually. Since completely-new or derived OSS licenses appear nearly every year, a license identification tool should be appropriately maintained by adding regular expressions corresponding to the new licenses. The final goal of our study is to construct a method to automatically create candidate license rules to be added to a license identification tool such as Ninka. Toward achieving the goal, files identified as unknown licenses must be classified by license firstly. In this paper, we propose a hierarchical clustering which divides unknown licenses into clusters of files with a single license. We conduct a case study to confirm the usefulness of our clustering method when it is applied for classifying 2,801, 1,230 and 2,446 unknown license statement files for Linux Kernel v4.4.6, FreeBSD v10.3.0 and Debian v7.8.0 respectively. As a result, it is confirmed that our method can create clusters which are suitable as candidates for generating license rules automatically.------------------------------This is a preprint of an article intended for publication Journal ofInformation Processing(JIP). This preprint should not be cited. Thisarticle should be cited as: Journal of Information Processing Vol.27(2019) (online)DOI http://dx.doi.org/10.2197/ipsjjip.27.42------------------------------

DOI

An Politeness Analysis for Understanding Continuous Activities of Developers in OSS Communities

宮崎智己, 伊原彰紀, 大平雅雄, 東裕之輔, 山谷陽亮 （Part： Corresponding author )

情報処理学会論文誌ジャーナル(Web)   59 ( 1 ) 2‐11 (WEB ONLY)   2018.01  [Refereed]

Open Source Software Engineering.

伊原彰紀, 大平雅雄 （Part： Corresponding author )

コンピュータソフトウェア ( Japan Society for Software Science and Technology )  33 ( 1 ) 28‐40(J‐STAGE) - 1_27   2016  [Refereed]  [Invited]

DOI

A Bug Triaging Method for Reducing the Time to Fix Bugs in Large-scale Open Source Software Development

柏祐太郎, 大平雅雄, 阿萬裕久, 亀井靖高 （Part： Corresponding author )

情報処理学会論文誌ジャーナル(Web) ( Information Processing Society of Japan (IPSJ) )  56 ( 2 ) 669-681 (WEB ONLY) - 681   2015.02  [Refereed]

　View Summary

This paper proposes a bug triaging method to reduce the time to fix bugs in large-scale open source software development. Our method considers the upper limit of tasks which can be fixed by a developer in a certain period. In this paper, we conduct a case study of applying our method to Mozilla Firefox and Eclipse Platform projects and show the following findings: (1) using our method mitigates the situation where the majority of bug-fixing tasks are assigned to particular developers, (2) our method can reduce up to 50%-83% of time to fix bugs compared with the manual bug triaging method and up to 34%-38% compared with the existing method, and (3) the two factors, Preference (adequate for fixing a bug) and Limit (limits of developers' working hours), used in our method have an dispersion effect on the task assignment.

A Data Mining Method for Understanding Co-evolution of OSS Systems and Communities

山谷陽亮, 大平雅雄, PHANNACHITTA Passakorn, 伊原彰紀 （Part： Corresponding author )

情報処理学会論文誌ジャーナル(Web) ( Information Processing Society of Japan (IPSJ) )  56 ( 1 ) 59-71 (WEB ONLY) - 71   2015.01  [Refereed]

　View Summary

While using open source software (OSS) has been becoming common as a means for developing software systems, many companies still have a reluctance to utilize OSS products. This paper proposes a data mining method to analyze the co-evolution process of OSS systems and communities quantitatively. The method includes time-delayed correlation analysis to investigate whether changes in the amount of an explanatory variable have an impact on changes in the amount of an objective variable after a certain period of time. Through a case study of the Eclipse Platform project using 131 software metrics and our method, we found that our method extracted 31 correlations which cannot be extracted by the common correlation analysis. We also found that our method can support additional analyses to observe the co-evolution process in the Eclipse Platform project more precisely.

Studying re-opened bugs in open source software

Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid M. Ibrahim, Masao Ohira, Bram Adams, Ahmed E. Hassan, Ken-ichi Matsumoto

EMPIRICAL SOFTWARE ENGINEERING ( SPRINGER )  18 ( 5 ) 1005 - 1042   2013.10  [Refereed]

　View Summary

Bug fixing accounts for a large amount of the software maintenance resources. Generally, bugs are reported, fixed, verified and closed. However, in some cases bugs have to be re-opened. Re-opened bugs increase maintenance costs, degrade the overall user-perceived quality of the software and lead to unnecessary rework by busy practitioners. In this paper, we study and predict re-opened bugs through a case study on three large open source projects-namely Eclipse, Apache and OpenOffice. We structure our study along four dimensions: (1) the work habits dimension (e.g., the weekday on which the bug was initially closed), (2) the bug report dimension (e.g., the component in which the bug was found) (3) the bug fix dimension (e.g., the amount of time it took to perform the initial fix) and (4) the team dimension (e.g., the experience of the bug fixer). We build decision trees using the aforementioned factors that aim to predict re-opened bugs. We perform top node analysis to determine which factors are the most important indicators of whether or not a bug will be re-opened. Our study shows that the comment text and last status of the bug when it is initially closed are the most important factors related to whether or not a bug will be re-opened. Using a combination of these dimensions, we can build explainable prediction models that can achieve a precision between 52.1-78.6 % and a recall in the range of 70.5-94.1 % when predicting whether a bug will be re-opened. We find that the factors that best indicate which bugs might be re-opened vary based on the project. The comment text is the most important factor for the Eclipse and OpenOffice projects, while the last status is the most important one for Apache. These factors should be closely examined in order to reduce maintenance cost due to re-opened bugs.

DOI

An Algorithm for Gradual Patch Acceptance Detection in Open Source Software Repository Mining

Passakorn Phannachitta, Akinori Ihara, Pijak Jirapiwong, Masao Ohira, Ken-ichi Matsumoto （Part： Corresponding author )

IEICE TRANSACTIONS ON FUNDAMENTALS OF ELECTRONICS COMMUNICATIONS AND COMPUTER SCIENCES   E95A ( 9 ) 1478 - 1489   2012.09  [Refereed]

DOI

Good or Bad Committers? - A Case Study of Committer's Activities on the Eclipse's Bug Fixing Process

Anakorn Jongyindee, Masao Ohira, Akinori Ihara, Ken-ichi Matsumoto （Part： Corresponding author )

IEICE TRANSACTIONS ON INFORMATION AND SYSTEMS   E95D ( 9 ) 2202 - 2210   2012.09  [Refereed]

DOI

A Candidate Committer Prediction Based on Developer Activities in Open Source Software Projects

IHARA Akinori, KAMEI Yasutaka, OHIRA Masao, MATSUMOTO Ken-ichi, UBAYASHI Naoyasu （Part： Corresponding author )

The IEICE transactions on information and systems (Japanese edetion) ( The Institute of Electronics, Information and Communication Engineers )  95 ( 2 ) 237 - 249   2012.02  [Refereed]

　View Summary

本論文では,オープンソースソフトウェア(OSS)プロジェクトに参加する一般開発者の中からコミッターに推薦されるべき有能な開発者(コミッター候補者)を見つけ出すことを目的とする.近年,数百件もの不具合がプロジェクトに日々,報告されている現状から,コミッターへの過度な負担が原因となり不具合修正の長期化を招いている.コミッターの負担を軽減させるためにコミッターを増員するという手段があるが,プロジェクトに参加する一般開発者の中からコミッター候補者を見つけることは容易ではない.本論文では,コミッター候補者を見つけ出すために既存コミッターの過去の活動とその活動量を分析し,コミッター予測モデルを構築した.モデル構築には,コミッター候補者と一般開発者の活動(パッチの投稿,パッチの検証,開発に伴う議論)履歴とプロジェクトでの活動期間を用いた.分析の結果,継続的にパッチの投稿,パッチの検証を行う開発者がコミッターに昇格していることが分かった.また,構築したコミッター予測モデルは,ランダムに予測する場合に比べて予測精度が5〜7倍高いことが分かった.

The Impact of Bug Management Patterns on Bug Fixing: A Case Study of Eclipse Projects

Masao Ohira, Ahmed E. Hassan, Naoya Osawa, Ken-ichi Matsumoto （Part： Lead author,　Corresponding author )

2012 28TH IEEE INTERNATIONAL CONFERENCE ON SOFTWARE MAINTENANCE (ICSM)     264 - 273   2012  [Refereed]

DOI

ソフトウェア開発における知識コラボレーション

大平雅雄, YE Yunwen, 中小路久美代, 山本恭裕 （Part： Lead author )

人工知能学会誌 ( 人工知能学会 )  26 ( 1 ) 66 - 78   2011.01  [Refereed]  [Invited]

A Time-Lag Analysis for Improving Communication among OSS Developers

Masao Ohira, Kiwako Koyama, Akinori Ihara, Shinsuke Matsumoto, Yasutaka Kamei, Ken-ichi Matsumoto （Part： Lead author,　Corresponding author )

NEW FRONTIERS IN ARTIFICIAL INTELLIGENCE   6284   135 - 146   2010  [Refereed]

DOI

Predicting re-opened bugs: A case study on the Eclipse project

Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid M. Ibrahim, Masao Ohira, Bram Adams, Ahmed E. Hassan, Ken-Ichi Matsumoto

Proceedings - Working Conference on Reverse Engineering, WCRE ( IEEE Computer Society )    249 - 258   2010  [Refereed]

DOI

OSSコミュニティにおけるオープンコラボレーションの理解

松本 真佑, 亀井 靖高, 大平 雅雄, 松本 健一 （Part： Corresponding author )

情報社会学会学会誌   3 ( 2 ) 29 - 42   2009.03  [Refereed]