Updated on 2024/04/16

写真a

 
IHARA Akinori
 
Name of department
Faculty of Systems Engineering, Socio-Informatics
Job title
Associate Professor
Concurrent post
School of Socio-Informatics（Associate Professor）、Informatics Division（Associate Professor）
Mail Address
E-mail address
Homepage
External link

Education

  • 2009
    -
    2012

    Nara Institute of Science and Technology   Information Science   Ph.D course  

  • 2007
    -
    2009

    Nara Institute of Science and Technology   Information Science   Master course  

Degree

  • 博士（工学）

Academic & Professional Experience

  • 2023.04
    -
    Now

    Wakayama University   Faculty of Systems Engineering   Associate Professor

  • 2023.04
    -
    Now

    Wakayama University   社会インフォマティクス学環

  • 2018.04
    -
    2023.03

    Wakayama University   Faculty of System Engineering   Lecturer

  • 2012.04
    -
    2018.03

    Nara Institute of Science and Technology   Information Science   Assistant Professor

Association Memberships

  • JAPAN SOCIETY FOR SOFTWARE SCIENCE AND TECHNOLOGY

  • IEEE

  • THE INSTITUTE OF ELECTRONICS, INFORMATION AND COMMUNICATION ENGINEERS

  • INFORMATION PROCESSING SOCIETY OF JAPAN

Research Areas

  • Informatics / Software

Classes (including Experimental Classes, Seminars, Graduation Thesis Guidance, Graduation Research, and Topical Research)

  • 2022   Graduation Research   Specialized Subjects

  • 2022   Exercises in Information Systems Development II   Specialized Subjects

  • 2022   Exercises in Information Systems Development I   Specialized Subjects

  • 2022   Socio-informatics Seminar Ⅱ   Specialized Subjects

  • 2022   Socio-informatics Seminar Ⅰ   Specialized Subjects

  • 2022   Exercises in Fundamental Programming   Specialized Subjects

  • 2022   Programming Languages 2   Specialized Subjects

  • 2022   Programming Languages 1   Specialized Subjects

  • 2022   Data Mining II   Specialized Subjects

  • 2022   Data Mining I   Specialized Subjects

  • 2022   Introduction to Data Science 2   Specialized Subjects

  • 2022   Introduction to Data Science 1   Specialized Subjects

  • 2022   Software Engineering   Specialized Subjects

  • 2022   Exercises in Software Engineering A   Specialized Subjects

  • 2022   Introductory Seminar in Systems Engineering   Specialized Subjects

  • 2022   Operating System   Specialized Subjects

  • 2021   Graduation Research   Specialized Subjects

  • 2021   Exercises in Information Systems Development II   Specialized Subjects

  • 2021   Socio-informatics Seminar Ⅱ   Specialized Subjects

  • 2021   Introduction to Data Science 2   Specialized Subjects

  • 2021   Exercises in Information Systems Development I   Specialized Subjects

  • 2021   Introduction to Data Science 1   Specialized Subjects

  • 2021   Exercises in Software Engineering A   Specialized Subjects

  • 2021   Operating System   Specialized Subjects

  • 2021   Data Mining II   Specialized Subjects

  • 2021   Software Engineering   Specialized Subjects

  • 2021   Graduation Research   Specialized Subjects

  • 2021   Graduation Research   Specialized Subjects

  • 2021   Socio-informatics Seminar Ⅰ   Specialized Subjects

  • 2021   Introduction to Current Systems Engineering B   Specialized Subjects

  • 2021   Exercises in Fundamental Programming   Specialized Subjects

  • 2021   Data Mining I   Specialized Subjects

  • 2020   Graduation Research   Specialized Subjects

  • 2020   Graduation Research   Specialized Subjects

  • 2020   Graduation Research   Specialized Subjects

  • 2020   Graduation Research   Specialized Subjects

  • 2020   Graduation Research   Specialized Subjects

  • 2020   Introduction to Current Systems Engineering B   Specialized Subjects

  • 2020   Exercises in Fundamental Programming   Specialized Subjects

  • 2020   Exercises in Information Systems Development II   Specialized Subjects

  • 2020   Exercises in Information Systems Development I   Specialized Subjects

  • 2020   Introduction to Data Science 2   Specialized Subjects

  • 2020   Introduction to Data Science 1   Specialized Subjects

  • 2020   Exercises in Software Engineering A   Specialized Subjects

  • 2020   Data Mining II   Specialized Subjects

  • 2020   Data Mining I   Specialized Subjects

  • 2020   Socio-informatics Seminar Ⅱ   Specialized Subjects

  • 2020   Socio-informatics Seminar Ⅰ   Specialized Subjects

  • 2019   Introduction to Current Systems EngineeringⅡ   Specialized Subjects

  • 2019   Exercises in Software Engineering   Specialized Subjects

  • 2019   Socio-informatics Seminar Ⅱ   Specialized Subjects

  • 2019   Exercises in Information Systems Development   Specialized Subjects

  • 2019   Introductory Seminar in Systems Engineering   Specialized Subjects

  • 2019   Invitation to Data Science   Liberal Arts and Sciences Subjects

  • 2019   Socio-informatics Seminar Ⅰ   Specialized Subjects

  • 2019   Exercises in Information Systems Development   Specialized Subjects

  • 2019   Introduction to Data Science   Specialized Subjects

  • 2019   Data Mining   Specialized Subjects

  • 2018   Introduction to Data Science   Specialized Subjects

  • 2018   Exercises in Software Engineering   Specialized Subjects

  • 2018   Socio-informatics Seminar Ⅱ   Specialized Subjects

  • 2018   Exercises in Information Systems Development   Specialized Subjects

  • 2018   NA   Specialized Subjects

  • 2018   Data Mining   Specialized Subjects

▼display all

Classes

  • 2022   Systems Engineering Global Seminar Ⅱ   Doctoral Course

  • 2022   Systems Engineering Global Seminar Ⅰ   Doctoral Course

  • 2022   Systems Engineering Advanced Research   Doctoral Course

  • 2022   Systems Engineering Advanced Seminar Ⅱ   Doctoral Course

  • 2022   Systems Engineering Advanced Seminar Ⅰ   Doctoral Course

  • 2022   Systems Engineering Project SeminarⅡB   Master's Course

  • 2022   Systems Engineering Project SeminarⅡA   Master's Course

  • 2022   Systems Engineering Project SeminarⅠB   Master's Course

  • 2022   Systems Engineering Project SeminarⅠA   Master's Course

  • 2022   Advanced Software Engineering   Master's Course

  • 2022   Systems Engineering SeminarⅡB   Master's Course

  • 2022   Systems Engineering SeminarⅡA   Master's Course

  • 2022   Systems Engineering SeminarⅠB   Master's Course

  • 2022   Systems Engineering SeminarⅠA   Master's Course

  • 2021   Systems Engineering Global Seminar Ⅱ   Doctoral Course

  • 2021   Systems Engineering Global Seminar Ⅰ   Doctoral Course

  • 2021   Systems Engineering Advanced Research   Doctoral Course

  • 2021   Systems Engineering Advanced Seminar Ⅱ   Doctoral Course

  • 2021   Systems Engineering Advanced Seminar Ⅰ   Doctoral Course

  • 2021   Systems Engineering Project SeminarⅡB   Master's Course

  • 2021   Systems Engineering Project SeminarⅡA   Master's Course

  • 2021   Systems Engineering Project SeminarⅠB   Master's Course

  • 2021   Systems Engineering Project SeminarⅠA   Master's Course

  • 2021   Systems Engineering SeminarⅡB   Master's Course

  • 2021   Systems Engineering SeminarⅡA   Master's Course

  • 2021   Systems Engineering SeminarⅠB   Master's Course

  • 2021   Systems Engineering SeminarⅠA   Master's Course

  • 2021   Advanced Software Engineering   Master's Course

  • 2020   Systems Engineering Global Seminar Ⅱ   Doctoral Course

  • 2020   Systems Engineering Global Seminar Ⅰ   Doctoral Course

  • 2020   Systems Engineering Advanced Research   Doctoral Course

  • 2020   Systems Engineering Advanced Seminar Ⅱ   Doctoral Course

  • 2020   Systems Engineering Advanced Seminar Ⅰ   Doctoral Course

  • 2020   Systems Engineering Project SeminarⅡB   Master's Course

  • 2020   Systems Engineering Project SeminarⅡA   Master's Course

  • 2020   Systems Engineering Project SeminarⅠB   Master's Course

  • 2020   Systems Engineering Project SeminarⅠA   Master's Course

  • 2020   Advanced Software Engineering   Master's Course

  • 2020   Systems Engineering SeminarⅡB   Master's Course

  • 2020   Systems Engineering SeminarⅡA   Master's Course

  • 2020   Systems Engineering SeminarⅠB   Master's Course

  • 2020   Systems Engineering SeminarⅠA   Master's Course

  • 2019   Systems Engineering Advanced Seminar Ⅱ   Doctoral Course

  • 2019   Systems Engineering Advanced Seminar Ⅱ   Doctoral Course

  • 2019   Systems Engineering Advanced Seminar Ⅰ   Doctoral Course

  • 2019   Systems Engineering Advanced Seminar Ⅰ   Doctoral Course

  • 2019   Systems Engineering Advanced Research   Doctoral Course

  • 2019   Systems Engineering Advanced Research   Doctoral Course

  • 2019   Systems Engineering SeminarⅡB   Master's Course

  • 2019   Systems Engineering SeminarⅡA   Master's Course

  • 2019   Systems Engineering SeminarⅠB   Master's Course

  • 2019   Systems Engineering SeminarⅠA   Master's Course

  • 2019   Systems Engineering Global Seminar Ⅱ   Doctoral Course

  • 2019   Systems Engineering Project SeminarⅡB   Master's Course

  • 2019   Systems Engineering Project SeminarⅡA   Master's Course

  • 2019   Systems Engineering Project SeminarⅠB   Master's Course

  • 2019   Systems Engineering Project SeminarⅠA   Master's Course

  • 2019   Advanced Software Engineering   Master's Course

  • 2018   Systems Engineering Advanced Research   Doctoral Course

  • 2018   Systems Engineering Advanced Research   Doctoral Course

  • 2018   Systems Engineering Advanced Seminar Ⅱ   Doctoral Course

  • 2018   Systems Engineering Advanced Seminar Ⅱ   Doctoral Course

  • 2018   Systems Engineering Advanced Seminar Ⅰ   Doctoral Course

  • 2018   Systems Engineering Advanced Seminar Ⅰ   Doctoral Course

  • 2018   Systems Engineering Project SeminarⅡB   Master's Course

  • 2018   Systems Engineering Project SeminarⅡA   Master's Course

  • 2018   Systems Engineering Project SeminarⅠB   Master's Course

  • 2018   Systems Engineering Project SeminarⅠA   Master's Course

  • 2018   Systems Engineering SeminarⅡB   Master's Course

  • 2018   Systems Engineering SeminarⅡA   Master's Course

  • 2018   Systems Engineering SeminarⅠB   Master's Course

  • 2018   Systems Engineering SeminarⅠA   Master's Course

▼display all

Research Interests

  • Software Engineering

  • プログラム理解

  • ソフトウェアリポジトリマイニング

  • 協調作業

  • プログラミング教育

  • ソフトウェア保守

  • 自動プログラム修正

▼display all

Published Papers

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

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

    情報処理学会論文誌   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]

  • 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 Trans. Inf. Syst.   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

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

    DOI

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

    伊原彰紀 （Part： Lead author )

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

  • Analysis of Prevalent Code Improvements through Code Review

    上田裕己, 石尾隆, 伊原彰紀, 松本健一

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

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

    Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto

    Transactions on Software Engineering     2020.02  [Refereed]

  • Understanding Developer Commenting in Code Reviews

    Toshiki Hirao, Raula Gaikovina Kula, Akinori Ihara, Kenichi Matsumoto

    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

    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

    Journal of Software Evolution and Process   31 ( 12 )   2019.05

    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

    2019 IEEE 13TH INTERNATIONAL WORKSHOP ON SOFTWARE CLONES (IWSC '19)     13 - 19   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

    Proceedings of the 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

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

    DOI

  • How are IF-Conditional Statements Fixed Through Peer CodeReview?

    Yuki Ueda, Akinori Ihara, Takashi Ishio, Toshiki Hirao, Kenichi Matsumoto

    IEICE Transactions on Information and Systems   101-D ( 11 ) 2720 - 2729   2018.11  [Refereed]

    DOI

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

    Shade Ruangwan, Patanamon Thongtanunam, Akinori Ihara, Kenichi Matsumoto

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

  • Erratum: Extraction of library update history using source code reuse detection (IEICE Transactions on Information and Systems (2018) E101.D:3 (799-802) DOI: 10.1587/transinf.2017EDL8205)

    Kanyakorn Jewmaidang, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto, Pattara Leelaprute

    IEICE Transactions on Information and Systems ( Institute of Electronics, Information and Communication, Engineers, IEICE )  E101D ( 3 ) 799 - 802   2018.06  [Refereed]

    　View Summary

    This paper proposes a method to extract and visualize a library update history in a project. The method identifies reused library versions by comparing source code in a product with existing versions of the library so that developers can understand when their own copy of a library has been copied, modified, and updated.

    DOI

  • Extraction of Library Update History Using Source Code Reuse Detection(vol 101, pg 799, 2018)

    Jewmaidang Kanyakorn, Ishio Takashi, Ihara Akinori, Matsumoto Kenichi

    IEICE Transactions on Information and Systems   E101D ( 6 ) 1722   2018.06  [Refereed]

    DOI

  • Maintaining third-party libraries through domain-specific category recommendations.

    Daiki Katsuragawa, Akinori Ihara, Raula Gaikovina Kula, Kenichi Matsumoto

    Proceedings of the 1st International Workshop on Software Health (SoHeal) 2018 ( ACM )    2 - 9   2018  [Refereed]

  • A Predicting Method of Issue-fixing Time Using Development Metrics in OSS Projects

    伊原彰紀, 若元亮樹, 松本健一

    情報処理学会論文誌ジャーナル(Web)   59 ( 3 ) 834 - 844   2018  [Refereed]

  • Towards Smoother Library Migrations: A Look at Vulnerable Dependency Migrations at Function Level for npm JavaScript Packages.

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

    Proceedings of the IEEE International Conference on Software Maintenance and Evolution (ICSME) 2018 ( IEEE Computer Society )    559 - 563   2018  [Refereed]

    DOI

  • An Empirical Study on README contents for JavaScript Packages.

    Shohei Ikeda, Akinori Ihara, Raula Gaikovina Kula, Kenichi Matsumoto

    IEICE Transactions on Information and Systems   abs/1802.08391   2018  [Refereed]

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

    宮崎智己, 伊原彰紀, 大平雅雄, 東裕之輔, 山谷陽亮

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

  • The impact of IR-based classifier configuration on the performance and the effort of method-level bug localization

    Chakkrit Tantithamthavorn, Surafel Lemma Abebe, Ahmed E. Hassan, Akinori Ihara, Kenichi Matsumoto

    Information and Software Technology ( Elsevier B.V. )  102   160 - 174   2018  [Refereed]

    　View Summary

    Context: IR-based bug localization is a classifier that assists developers in locating buggy source code entities (e.g., files and methods) based on the content of a bug report. Such IR-based classifiers have various parameters that can be configured differently (e.g., the choice of entity representation). Objective: In this paper, we investigate the impact of the choice of the IR-based classifier configuration on the top-k performance and the required effort to examine source code entities before locating a bug at the method level. Method: We execute a large space of classifier configuration, 3172 in total, on 5266 bug reports of two software systems, i.e., Eclipse and Mozilla. Results: We find that (1) the choice of classifier configuration impacts the top-k performance from 0.44% to 36% and the required effort from 4395 to 50,000 LOC
    (2) classifier configurations with similar top-k performance might require different efforts
    (3) VSM achieves both the best top-k performance and the least required effort for method-level bug localization
    (4) the likelihood of randomly picking a configuration that performs within 20% of the best top-k classifier configuration is on average 5.4% and that of the least effort is on average 1%
    (5) configurations related to the entity representation of the analyzed data have the most impact on both the top-k performance and the required effort
    and (6) the most efficient classifier configuration obtained at the method-level can also be used at the file-level (and vice versa). Conclusion: Our results lead us to conclude that configuration has a large impact on both the top-k performance and the required effort for method-level bug localization, suggesting that the IR-based configuration settings should be carefully selected and the required effort metric should be included in future bug localization studies.

    DOI

  • An Analysis of Library Rollbacks: A Case Study of Java Libraries

    Hirohiko Suwa, Akinori Ihara, Raula Gaikovina Kula, Daiki Fujibayashi, Kenichi Matsumoto

    1st International Workshop on Software-driven Big Data Analytics     2017.12  [Refereed]

    DOI

  • How is if statement fixed through code review? A case study of QT project

    Yuki Ueda, Akinori Ihara, Toshiki Hirao, Takashi Ishio, Kenichi Matsumoto

    Proceedings - 2017 IEEE 28th International Symposium on Software Reliability Engineering Workshops, ISSREW 2017 ( Institute of Electrical and Electronics Engineers Inc. )    207 - 213   2017.11  [Refereed]

    　View Summary

    Peer code review is key to ensuring the absence of software defects. To improve the review process, many code review tools provide OSS(Open Source Software) project CI(Continuous Integration) tests that automatically verify code quality issues such as a code convention issues. However, these tests do not cover project policy issues and a code readability issues. In this study, our main goal is to understand how a code owner fixes conditional statement issues based on reviewers feedback. We conduct an empirical study to understand if statement changes after review. Using 69,325 review requests in the Qt project, we analyze changes of the if conditional statements that (1) are requested to be reviewed, and (2) that are implemented after review. As a result, we find the most common symbolic changes are '(' and ')' (35%), '!' operator (20%) and '-&gt
    ' operator (12%). Also, '!' operator is frequently replaced with '(' and ')'.

    DOI

  • Understanding key features of high-impact bug reports

    Md. Rejaul Karim, Akinori Ihara, Xin Yang, Hajimu Iida, Kenichi Matsumoto

    Proceedings - 8th IEEE International Workshop on Empirical Software Engineering in Practice, IWESEP 2017 ( Institute of Electrical and Electronics Engineers Inc. )    53 - 58   2017.05  [Refereed]

    　View Summary

    Nowadays, software projects are receiving bug reports on a daily basis. Developers cannot treat all the bugs in the same priority since some bugs can significantly affect software development process and the quality of products. Previous studies defined these bugs as High Impact Bug (HIB) and they found that HIB should be fixed quicker than other bugs in software development. However, fixing a HIB sometimes become complicated because the low-quality bug reports can be delay the bug fixing. In this study, we investigate what information is essential when reporting a HIB report. As a case study, we manually examine the HIB reports and perform both qualitative and quantitative analysis in Apache Camel project. Our main findings include: (1) we find four types of features are the most requested information from developers when they fix HIB, (2) the requested additional information significantly influences bug fixing time.

    DOI

  • Does the release cycle of a library project influence when it is adopted by a client project?

    Daiki Fujibayashi, Akinori Ihara, Hirohiko Suwa, Raula Gaikovina Kula, Kenichi Matsumoto

    SANER 2017 - 24th IEEE International Conference on Software Analysis, Evolution, and Reengineering ( Institute of Electrical and Electronics Engineers Inc. )    569 - 570   2017.03  [Refereed]

    　View Summary

    A key goal of this research is to understand the relationship between adoption of software library versions and its release cycle. In detail, we conducted an empirical study of the release cycle of 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our preliminary findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle.

    DOI

  • Which review feedback did long-term contributors get on OSS projects?

    Takuto Norikane, Akinori Ihara, Kenichi Matsumoto

    SANER 2017 - 24th IEEE International Conference on Software Analysis, Evolution, and Reengineering ( Institute of Electrical and Electronics Engineers Inc. )    571 - 572   2017.03  [Refereed]

    　View Summary

    Open Source Software (OSS) cannot exist without contributions from the community. In particular, long-term contributors (LTCs) (e.g., committer), defined as contributors who spend at least one year on OSS projects, play crucial role in a project success because they would have permission to add (commit) code changes to a project's version control system, and to become a mentor for a beginner in OSS projects. However, contributors often leave a project before becoming a LTC because most contributors are volunteers. If contributors are motivated in their work in OSS projects, they might not leave the projects. In this study, we examine the phenomena involved in becoming a LTC in terms of motivation to continue in OSS projects. In particular, our target motivation is to understand what is involved in long-term contribution with other expert contributors. We study classifier to identify a LTC who will contribute patch submissions for more than one year based on collaboration in terms of the code review process. In detail, we analyze what review feedbacks encourage a contributor to continue with OSS project. Using a Qt project dataset, we understand review feedback which affected contribution period of the developer.

    DOI

  • Toward Identifying a Re-opened Bug Based on Reviewers Disagreement―Case Study of OpenStack Project

    林 宏徳, 伊原 彰紀, 松本 健一

    情報処理学会論文誌 ( 情報処理学会 )    2017.03  [Refereed]

  • Toward Identifying a Re-opened Bug Based on Reviewers Disagreement-Case Study of OpenStack Project

    林宏徳, 伊原彰紀, 松本健一

    情報処理学会論文誌ジャーナル(Web)   58 ( 3 ) 721 - 725   2017  [Refereed]

  • Understanding when to adopt a library: A case study on ASF projects

    Akinori Ihara, Daiki Fujibayashi, Hirohiko Suwa, Raula Gaikovina Kula, Kenichi Matsumoto

    IFIP Advances in Information and Communication Technology ( Springer New York LLC )  496   128 - 138   2017  [Refereed]

    　View Summary

    Software libraries are widely used by both industrial and open source client projects. Ideally, a client user of a library should adopt the latest version that the library project releases. However, sometimes the latest version is not better than a previous version. This is because the latest version may include additional developer effort to test and integrate all changed features. In this study, our main goal is to better understand the relationship between adoption of library versions and its release cycle. Specifically, we conducted an empirical study of release cycles for 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. Moreover, results suggest that software projects are more likely to adopt the latest version of a rapid-release library compared to libraries with a longer release cycles.

    DOI

  • Project IŜ3: Incentive-based intelligent intervention for smart and sustainable society

    Yutaka Arakawa, Keiichi Yasumoto, Kenichi Matsumoto, Hideaki Hata, Hirohiko Suwa, Akinori Ihara, Manato Fujimoto

    Proceedings - 2016 5th IIAI International Congress on Advanced Applied Informatics, IIAI-AAI 2016     215 - 218   2016.08  [Refereed]

    　View Summary

    © 2016 IEEE. Project IS^3 is the leading-edge project in Nara Institute of Science and Technology, a national graduate school in Japan, started from February 2016. This project aims to utilize a human's behavior change for solving the social problems and maintaining our society sustainably. In order to cause the behavior change intentionally, various information technologies are required. In this paper, we explain the concept and goal of our project and figure out what we will do in this project.

    DOI

  • Toward selecting a reliable version of OSS library based on bug-fixing curve

    Keisuke Fujino, Akinori Ihara, Kiyoshi Honda, Hironori Washizaki, Kenichi Matsumoto

    23rd IEEE International Conference on Software Analysis, Evolution, and Reengineering (SANER 2016)     2016.03  [Refereed]

  • Treemap Forest : An Exploratory Data Visualization Approach for Software Development Project Datasets

    中川 尊雄, 伊原 彰紀, 松本 健一

    SEC journal ( 情報処理推進機構技術本部ソフトウェア・エンジニアリング・センター )  12 ( 1 ) 8 - 15   2016

  • 欠陥とソースコードの変更回数の関係分析

    本田 澄, 坂口 英司, 伊原 彰紀, 鷲崎 弘宜, 深澤 良彰

    情報処理学会/ソフトウェア工学研究会ウィンターワークショップ2016・イン・逗子     2016  [Refereed]

  • Open Source Software Engineering.

    伊原彰紀, 大平雅雄

    コンピュータソフトウェア ( 日本ソフトウェア科学会 )  33 ( 1 ) 1_28 - 1_40   2016  [Refereed]

  • A Study of Redundant Metrics in Defect Prediction Datasets

    Jirayus Jiarpakdee, Chakkrit Tantithamthavorn, Akinori Ihara, Kenichi Matsumoto

    2016 IEEE 27TH INTERNATIONAL SYMPOSIUM ON SOFTWARE RELIABILITY ENGINEERING WORKSHOPS (ISSREW) ( IEEE )    51 - 52   2016  [Refereed]

    　View Summary

    Defect prediction models can help Software Quality Assurance (SQA) teams understand their past pitfalls that lead to defective modules. However, the conclusions that are derived from defect prediction models without mitigating redundant metrics issues may be misleading. In this paper, we set out to investigate if redundant metrics issues are affecting defect prediction studies, and its degree and causes of redundancy. Through a case study of 101 publicly-available defect datasets of systems that span both proprietary and open source domains, we observe that (1) 10%-67% of metrics of the studied defect datasets are redundant, and (2) the redundancy of metrics has to do with the aggregation functions of metrics. These findings suggest that researchers should be aware of redundant metrics prior to constructing a defect prediction model in order to maximize internal validity of their studies.

    DOI

  • Code Review Participation: Game Theoretical Modeling of Reviewers in Gerrit Datasets

    Norihito Kitagawa, Hideaki Hata, Akinori Ihara, Kiminao Kogiso, Kenichi Matsumoto

    9TH IEEE/ACM INTERNATIONAL WORKSHOP ON COOPERATIVE AND HUMAN ASPECTS OF SOFTWARE ENGINEERING (CHASE 2016) ( IEEE )    64 - 67   2016  [Refereed]

    　View Summary

    Code review is a common practice for improving the quality of source code changes and expediting knowledge transfer in a development community. In modern code review, source code changes or patches are considered to be assessed and approved for integration by multiple reviews. However, from our empirical study, we found that some patches are reviewed by only one reviewer, and some reviewers did not continue the review discussion, which can have negative effects on software quality. To understand these reviewers' behaviors, we model the code review situation based on the snowdrift game, which is used to analyze social dilemmas. With this game-theoretical modeling, we found that it can explain reviewers' behaviors well.

    DOI

  • Understanding Question Quality through Affective Aspect in Q&A Site

    Jirayus Jiarpakdee, Akinori Ihara, Ken-ichi Matsumoto

    2016 IEEE/ACM 1ST INTERNATIONAL WORKSHOP ON EMOTION AWARENESS IN SOFTWARE ENGINEERING (SEMOTION) ( IEEE )    12 - 17   2016  [Refereed]

    　View Summary

    Ever since the Internet has become widely available, question and answer sites have been used as a knowledge sharing service. Users ask the community about how to solve problems, hoping that there will be someone to provide a solution. However, not every question is answered. Eric Raymond claimed that how an user asks a question is important. Existing studies have presented ways to study the question quality by textual, community-based or affective features. In this paper, we investigated how affective features are related to the question quality, and we found that using affective features improves the prediction of question quality. Moreover, Favorite Vote Count feature has the highest influence on our prediction models.

    DOI

  • The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process

    Toshiki Hirao, Akinori Ihara, Yuki Ueda, Passakorn Phannachitta, Ken-ichi Matsumoto

    OPEN SOURCE SYSTEMS: INTEGRATING COMMUNITIES, OSS 2016 ( SPRINGER-VERLAG BERLIN )  472   97 - 110   2016  [Refereed]

    　View Summary

    Software code review systems are commonly used in software development. In these systems, many patches are submitted to improve the quality. To verify the quality, voting is commonly used by contributors; however, there still exists a major problem, namely, that reviewers do not always simply reach a broad agreement. In our previous study, we found that consensus is not usually reached, implying that an individual reviewer's final decision usually differs from that of the majority of the other reviewers. In this study, we further investigate the reasons why such situations often occur, and provide suggestions for better handling of these problems. Our analysis of the Qt and OpenStack project datasets allow us to suggest that a patch owner should select more appropriate reviewers who often agree with others' decisions.

    DOI

  • オープンソースソフトウェアに関するソースコードの変更回数とバグ修正の関係分析に向けて

    本田 澄, 伊原 彰紀, 鷲崎 弘宜, 深澤 良彰

    第22回 ソフトウェア工学の基礎ワークショップ (FOSE 2015)     2015.11  [Refereed]

  • The Impact of Mislabelling on the Performance and Interpretation of Defect Prediction Models

    Chakkrit Tantithamthavorn, Shane McIntosh, Ahmed E. Hassan, Akinori Ihara, Kenichi Matsumoto

    2015 IEEE/ACM 37TH IEEE INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, VOL 1 ( IEEE )    812 - 823   2015  [Refereed]

    　View Summary

    The reliability of a prediction model depends on the quality of the data from which it was trained. Therefore, defect prediction models may be unreliable if they are trained using noisy data. Recent research suggests that randomly-injected noise that changes the classification (label) of software modules from defective to clean (and vice versa) can impact the performance of defect models. Yet, in reality, incorrectly labelled (i.e., mislabelled) issue reports are likely non-random. In this paper, we study whether mislabelling is random, and the impact that realistic mislabelling has on the performance and interpretation of defect models. Through a case study of 3,931 manually-curated issue reports from the Apache Jackrabbit and Lucene systems, we find that: (1) issue report mislabelling is not random; (2) precision is rarely impacted by mislabelled issue reports, suggesting that practitioners can rely on the accuracy of modules labelled as defective by models that are trained using noisy data; (3) however, models trained on noisy data typically achieve 56%-68% of the recall of models trained on clean data; and (4) only the metrics in top influence rank of our defect models are robust to the noise introduced by mislabelling, suggesting that the less influential metrics of models that are trained on noisy data should not be interpreted or used to make decisions.

    DOI

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

    山谷陽亮, 大平雅雄, PHANNACHITTA Passakorn, 伊原彰紀

    情報処理学会論文誌ジャーナル(Web) ( 一般社団法人情報処理学会 )  56 ( 1 ) 59 - 71   2015  [Refereed]

  • A Dataset of High Impact Bugs: Manually-Classified Issue Reports

    Masao Ohira, Yutaro Kashiwa, Yosuke Yamatani, Hayato Yoshiyuki, Yoshiya Maeda, Nachai Limsettho, Keisuke Fujino, Hideaki Hata, Akinori Ihara, Kenichi Matsumoto

    12TH WORKING CONFERENCE ON MINING SOFTWARE REPOSITORIES (MSR 2015) ( IEEE )  2015-August   518 - 521   2015  [Refereed]

    　View Summary

    The importance of supporting test and maintenance activities in software development has been increasing, since recent software systems have become large and complex. Although in the field of Mining Software Repositories (MSR) there are many promising approaches to predicting, localizing, and triaging bugs, most of them do not consider impacts of each bug on users and developers but rather treat all bugs with equal weighting, excepting a few studies on high impact bugs including security, performance, blocking, and so forth. To make MSR techniques more actionable and effective in practice, we need deeper understandings of high impact bugs. In this paper we introduced our dataset of high impact bugs which was created by manually reviewing four thousand issue reports in four open source projects (Ambari, Camel, Derby and Wicket).

    DOI

  • OSSの不具合修正曲線に基づく残存未修正不具合数の予測の試み

    藤野啓輔, 伊原彰紀, 本田澄, 鷲崎弘宜, 松本健一

    日本ソフトウェア科学会 第21回 ソフトウェア工学の基礎ワークショップ FOSE 2014 in 霧島     2014.12  [Refereed]

  • Adaptive Search Framework: Better Search Result for Community

    Papon Yongpisanpop, Masao Ohira, Akinori Ihara, Kenichi Matsumoto

    情報社会学会誌   8 ( 2 ) 29 - 43   2014.03  [Refereed]

  • Impact Analysis of Granularity Levels on Feature Location Technique

    Chakkrit Tantithamthavorn, Akinori Ihara, Hideaki Hata, Kenichi Matsumoto

    Communications in Computer and Information Science ( Springer )  432 CCIS   135 - 149   2014  [Refereed]

    　View Summary

    Due to the increasing of software requirements and software features, modern software systems continue to grow in size and complexity. Locating source code entities that required to implement a feature in millions lines of code is labor and cost intensive for developers. To this end, several studies have proposed the use of Information Retrieval (IR) to rank source code entities based on their textual similarity to an issue report. The ranked source code entities could be at a class or function granularity level. Source code entities at the class-level are usually large in size and might contain a lot of functions that are not implemented for the feature. Hence, we conjecture that the class-level feature location technique requires more effort than function-level feature location technique. In this paper, we investigate the impact of granularity levels on a feature location technique. We also presented a new evaluation method using effort-based evaluation. The results indicated that function-level feature location technique outperforms class-level feature location technique. Moreover, function-level feature location technique also required 7 times less effort than class-level feature location technique to localize the first relevant source code entity. Therefore, we conclude that feature location technique at the function-level of program elements is effective in practice. © Springer-Verlag Berlin Heidelberg 2014.

    DOI

  • Early Identification of Future Committers in Open Source Software Projects

    Akinori Ihara, Yasutaka Kamei, Masao Ohira, Ahmed E. Hassan, Naoyasu Ubayashi, Ken-ichi Matsumoto

    2014 14TH INTERNATIONAL CONFERENCE ON QUALITY SOFTWARE (QSIC 2014) ( IEEE COMPUTER SOC )    47 - 56   2014  [Refereed]

    　View Summary

    There exists two types of developers in Open Source Software (OSS) projects: 1) Committers who have permission to commit edited source code to the Version Control System (VCS), 2) Developers who contribute source code but cannot commit to the VCS directly. In order to develop and evolve high quality OSS, projects are always in search of new committers. OSS projects often promote strong developers to become committers. When existing committers find strong developers, they propose their promotion to a committer role. Delaying the committer-promotion might lead to strong developers departing from an OSS project and the project losing them. However early committer-promotion comes with its own slew of risks as well (e.g., the promotion of inexperienced developers). Hence, committer-promotion decisions are critical for the quality and successful evolution of OSS projects. In this paper, we examine the committer-promotion phenomena for two OSS projects (Eclipse and Firefox). We find that the amount of activities by future committers was higher than the amount of activities by developers who did not become committers). We also find that some developers are promoted to a committer role very rapidly (within a few month) while some of developers take over one year to become a committer. Finally, we develop a committer-identification model to assist OSS projects identifying future committers.

    DOI

  • Industry Questions About Open Source Software in Business: Research Directions and Potential Answers

    Akinori Ihara, Akito Monden, Ken-ichi Matsumoto

    2014 6TH INTERNATIONAL WORKSHOP ON EMPIRICAL SOFTWARE ENGINEERING IN PRACTICE (IWESEP 2014) ( IEEE )    55 - 59   2014  [Refereed]

    　View Summary

    As open source software (OSS) has become an integral part of today's software businesses, many software companies rely on OSS to develop their customer solutions and products. On the other hand, they face various concerns in using OSS, such as technical support, quality, security and licensing issues. This paper focuses on OSS-related FAQ in industry, and tries to answer them or to provide research directions based on lessons learned from recent mining OSS repository researches.

    DOI

  • Exploratory Data Analysis in Independent Assessment of Software Quality: A Case Study of OSS Project Data

    大平 雅雄, 伊原 彰紀, 中野 大輔, 松本 健一

    SEC Journal ( 情報処理推進機構 )  10 ( 1 )   2014  [Refereed]

  • 「ソフトウェア工学の実証的アプローチ」シリーズ第5回 ソフトウェアリポジトリマイニング

    門田 暁人, 伊原 彰紀, 松本 健一

    コンピュウータソフトウェア   30 ( 2 ) 52 - 65   2013.05  [Refereed]

  • Predicting the Bug Fixing Time Based on the Bug Assignment Patterns in OSS Development

    正木 仁, 大平 雅雄, 伊原 彰紀, 松本 健一

    情報処理学会論文誌 ( 情報処理学会 )  54 ( 2 ) 933 - 944   2013.02  [Refereed]

    　View Summary

    大規模OSSプロジェクトには日々大量の不具合が報告されており，不具合修正時間（OSSプロジェクトに報告された不具合が解決するまでに要する時間）をより正確に見積もることが重要になってきている．OSSプロジェクト管理者は，次期バージョンのリリースまでにどの不具合を修正すべきかを判断しなければならないためである．しかしながら，不具合の修正範囲の大きさや問題の複雑さの違い，ボランティアを主体とする開発者のスキルセットの違いなどの要因によって，個々の不具合の修正時間を見積もることは容易ではない．そのため近年，OSS開発における不具合修正時間の予測に関する研究がさかんに行われている．本論文では，不具合割当てパターンを用いて不具合修正時間の予測モデルを構築する．不具合割当てパターンとは，不具合修正タスク割当て時の不具合報告者・管理者・修正担当者の3者の社会的関係を分類したものである．不具合割当てパターンの違いにより，修正作業にとりかかるまでの時間および修正作業自体に要する時間はそれぞれ大きく異なることが知られている．従来研究の多くは不具合情報（重要度や優先度など）に基づいて予測モデルを構築しているが，不具合管理パターンを考慮することでさらなる予測精度の向上を期待できる．本論文では，Eclipse PlatformおよびJDTを対象として構築した予測モデルの評価を行った．実験の結果，不具合割当てパターンが不具合修正時間の予測精度向上に寄与するとともに，指定期間内（1週間以内など）に不具合修正が完了するか否かの判断を支援できることが分かった．さらに，本予測モデルを利用することで，Platformで約16%，JDTで約10%多くの不具合を修正可能と判断できることが分かった．The number of reported bugs has been increasing especially in large-scale open source software (OSS) projects. Project managers in the projects have to decide which bugs should be resolved until they release the next version of their products. However it is not easy to estimate the time to resolve each bug due to the differences of the size of required modifications, the difficulty of each modification, skill set of each developer, and so forth. To address this issue, many studies have tried to predict the bug fixing time in OSS development. In this paper we constructs a prediction model for the bug fixing time, using the bug assignment patterns which have an impact on developer's performance of fixing bugs. The bug assignment patterns categorize the social relationships among bug reporters, managers, and developers in assigning bug fixing tasks. While most studies in the past only used the information extracted from bug reports itself, taking the bug assignment patterns into account would lead to prediction results with higher accuracy. Using data from the Eclipse Platform and JDT projects, we evaluates the prediction model. As a result, we found that the bug assignment patterns improved the prediction accuracy and help OSS managers make sure if a target bug will be resolved in a specified period (e.g., one week). We also found that our prediction model can contribute to resolve more bugs until the specified release (about 16% in Platform and about 10% in JDT).

  • Using Co-Change Histories to Improve Bug Localization Performance

    Chakkrit Tantithamthavorn, Akinori Ihara, Ken-ichi Matsumoto

    2013 14TH ACIS INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, ARTIFICIAL INTELLIGENCE, NETWORKING AND PARALLEL/DISTRIBUTED COMPUTING (SNPD 2013) ( IEEE )    543 - 548   2013  [Refereed]

    　View Summary

    A large open source software (OSS) project receives many bug reports on a daily basis. Bug localization techniques automatically pinpoint source code fragments that are relevant to a bug report, thus enabling faster correction. Even though many bug localization methods have been introduced, their performance is still not efficient. In this research, we improved on existing bug localization methods by taking into account co-change histories. We conducted experiments on two OSS datasets, the Eclipse SWT 3.1 project and the Android ZXing project. We validated our approach by evaluating effectiveness compared to the state-of-the-art approach BugLocator. In the Eclipse SWT 3.1 project, our approach reliably identified source code that should be fixed for a bug in 72.46% of the total bugs, while BugLocator identified only 51.02%. In the Android ZXing project, our approach identified 85.71%, while BugLocator identified 60%.

    DOI

  • Mining Software Repositories

    門田暁人, 伊原彰紀, 松本健一

    コンピュータソフトウェア ( 日本ソフトウェア科学会 )  30 ( 2 ) 52 - 65   2013  [Refereed]

    DOI

  • What type of thread can get feedback in oss user mailing list?

    Akinori Ihara, Yuji Tsuda, Ken-Ichi Matsumoto

    2013 5th International Workshop on Social Software Engineering, SSE 2013 - Proceedings     25 - 28   2013  [Refereed]

    　View Summary

    High quality Open Source Software (OSS) has been used in many commercial software developments. In order to provide technical support to end users, OSS projects manage a user mailing list. It is for discussion about bugs and new functions of OSS with end users. However, according to a survey of Japanese companies that use OSS to build their commercial software, the biggest problem is the lack of adequate technical support. In this study, we investigate what type of thread can get feedback in user mailing list. As a result of a case study using Apache and Python project data, a thread is posted by a deep experienced user would be received a useful answer. In addition, we found threads written about internal system information of the OSS is more likely to be replied. Copyright 2013 ACM.

    DOI

  • Mining A Change History to Quickly Identify Bug Locations : A Case Study of the Eclipse Project

    Chakkrit Tantithamthavorn, Rattamont Teekavanich, Akinori Ihara, Ken-ichi Matsumoto

    2013 IEEE INTERNATIONAL SYMPOSIUM ON SOFTWARE RELIABILITY ENGINEERING WORKSHOPS (ISSREW) ( IEEE )    108 - 113   2013  [Refereed]

    　View Summary

    In this study, we proposed an approach to mine a change history to improve the bug localization performance. The key idea is that a recently fixed file may be fixed in the near future. We used a combination of textual feature and mining the change history to recommend source code files that are likely to be fixed for a given bug report. First, we adopted the Vector Space Model (VSM) to find relevant source code files that are textually similar to the bug report. Second, we analyzed the change history to identify previously fixed files. We then estimated the fault proneness of these files. Finally, we combined the two scores, from textual similarity and fault proneness, for every source code file. We then recommend developers examine source code files with higher scores. We evaluated our approach based on 1,212 bug reports from the Eclipse Platform and Eclipse JDT. The experimental results show that our proposed approach can improve the bug localization performance and effectively identify buggy files.

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

    Passakorn Phannachitta, Akinori Ihara, Pijak Jirapiwong, Masao Ohira, Kenichi Matsumoto

    IEICE Transactions on Information and Systems   E95-A ( 9 ) 1478 - 1489   2012.09  [Refereed]

  • Studying Re-Opened Bugs in Open Source Software

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

    Empirical Software Engineering     2012.09  [Refereed]

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

    Anakorn jongyindee, Masao Ohira, Akinori Ihara, Kenichi Matsumoto

    IEICE Transactions on Information and Systems   E95-D ( 9 ) 2202 - 2210   2012.09  [Refereed]

  • Locating source code to be fixed based on initial bug reports - A case study on the eclipse project

    Phiradet Bangcharoensap, Akinori Ihara, Yasutaka Kamei, Ken-Ichi Matsumoto

    Proceedings - 2012 4th International Workshop on Empirical Software Engineering in Practice, IWESEP 2012     10 - 15   2012  [Refereed]

    　View Summary

    In most software development, a Bug Tracking System is used to improve software quality. Based on bug reports managed by the bug tracking system, triagers who assign a bug to fixers and fixers need to pinpoint buggy files that should be fixed. However if triagers do not know the details of the buggy file, it is difficult to select an appropriate fixer. If fixers can identify the buggy files, they can fix the bug in a short time. In this paper, we propose a method to quickly locate the buggy file in a source code repository using 3 approaches, text mining, code mining, and change history mining to rank files that may be causing bugs. (1) The text mining approach ranks files based on the textual similarity between a bug report and source code. (2) The code mining approach ranks files based on prediction of the fault-prone module using source code product metrics. (3) The change history mining approach ranks files based on prediction of the fault-prone module using change process metrics. Using Eclipse platform project data, our proposed model gains around 20% in TOP1 prediction. This result means that the buggy files are ranked first in 20% of bug reports. Furthermore, bug reports that consist of a short description and many specific words easily identify and locate the buggy file. © 2012 IEEE.

    DOI

  • OSS開発における不具合修正プロセスの現状と課題:不具合修正時間の短縮化へ向けた分析

    伊原彰紀, 大平雅雄, 松本健一

    情報社会学会誌   6 ( 2 ) 1 - 12   2012  [Refereed]

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

    IHARA Akinori, KAMEI Yasutaka, OHIRA Masao, MATSUMOTO Ken-ichi, UBAYASHI Naoyasu

    電子情報通信学会論文誌 ( 一般社団法人電子情報通信学会 )  J95-D ( 2 ) 237 - 249   2012  [Refereed]

  • グローバル環境下におけるOSS開発者の情報交換に対する時差の影響

    亀井靖高, 大平雅雄, 伊原彰紀, 小山貴和子, 松本真佑, 松本健一, 鵜林尚靖

    情報社会学会誌   6 ( 2 ) 17 - 32   2012

  • グローバル環境下におけるOSS開発者の情報交換に対する時差の影響

    亀井 靖高, 大平 雅雄, 伊原 彰紀, 小山 貴和子, 本 真佑, 松本 健一, 鵜林 尚靖

    情報社会学会学会誌   6 ( 2 ) 13 - 30   2011.11  [Refereed]

  • An analysis of gradual patch application: A better explanation of patch acceptance

    Passakorn Phannachitta, Pijak Jirapiwongy, Akinori Ihara, Masao Ohira, Ken-Ichi Matsumoto

    Proceedings - Joint Conference of the 21st International Workshop on Software Measurement, IWSM 2011 and the 6th International Conference on Software Process and Product Measurement, MENSURA 2011 ( IEEE Computer Society )    106 - 115   2011  [Refereed]

    　View Summary

    Patch submission has been known as one of the most important activities to sustain the open source software (OSS). The patch archive can be analyzed to procure many benefit cognizance for supporting the OSS project works. The recent models and methods that analyze the patches acceptance are quite rack of comprehensive
    hence, complex activities such as a committer portioning the submitted patch out and accept are still excluded from the analysis. Therefore, the results derived from those methods would be inadequate to conclude the actual patch acceptance. In this research, we introduce an algorithm for analyzing patch acceptance including the partial and gradually accepted conditions. Validating our algorithm, we present our methods for indicating the partial and gradual application of the submitted patch between either mailing list and SVN or Bugzilla and CVS which are the commonly deployed patchactivities related system. We studied on two well known OSS projects
    Apache HTTP and Eclipse Platform. We obtained a fascinating conclusion that larger patches have more confident to be accepted than the smaller contradicted to other analysis that came from the recent methods. © 2011 IEEE.

    DOI

  • Good or bad committers? A case study of committers' cautiousness and the consequences on the bug fixing process in the eclipse project

    Anakorn Jongyindee, Masao Ohira, Akinori Ihara, Ken-Ichi Matsumoto

    Proceedings - Joint Conference of the 21st International Workshop on Software Measurement, IWSM 2011 and the 6th International Conference on Software Process and Product Measurement, MENSURA 2011 ( IEEE Computer Society )    116 - 125   2011  [Refereed]

    　View Summary

    There are many roles to play in the bug fixing process in open source software development. A developer called "Committer", who has a permission to submit a patch into software repository, plays a major role in this process and hold a key to the successfulness of the project. In this work, we have observed each committer activities from the Eclipse-Platform bug tracking system and version archives. Despite the importance of committer's activities, we suspected that sometimes committers can make mistakes, which have negative consequences to the bug fixing process. Our research focus on studying the consequences of each committer's activities to this process. We collected each committer's historical data and evaluated each of them by comparing the more cautiousness to less cautiousness committers. Then we looked deeper into each committer's characteristics to see the reasons why some committers tend to make mistakes more than the others. From our results, we would like to make a humbly suggestion to the OSS's committers to be aware of their importance to the projects and be cautious before doing their jobs. © 2011 IEEE.

    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]

    　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 the Eclipse project. We structure our study along 4 dimensions: 1) the work habits dimension (e.g., the weekday on which the bug was initially closed on), 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). Our case study on the Eclipse Platform 3.0 project shows that the comment and description text, the time it took to fix the bug, and the component the bug was found in are the most important factors in determining whether a bug will be re-opened. Based on these dimensions we create decision trees that predict whether a bug will be re-opened after its closure. Using a combination of our dimensions, we can build explainable prediction models that can achieve 62.9% precision and 84.5% recall when predicting whether a bug will be re-opened. © 2010 IEEE.

    DOI

  • A Time-Lag Analysis Toward Improving the Efficiency of Communications among OSS Developers

    Masao Ohira, Kiwako Koyama, Akinori Ihara, Shinsuke Matsumoto, Yasutaka Kamei, Ken-ichi Matsumoto

    In Proceedings of The 3rd International Workshop on Knowledge Collaboration in Software Development (KCSD2009)     49 - 62   2009.11  [Refereed]

  • An Analysis Method for Improving a Bug Modification Process in Open Source Software Development

    Akinori Ihara, Masao Ohira, Ken-ichi Matsumoto

    IWPSE-EVOL 09: ERCIM WORKSHOP ON SOFTWARE EVOLUTION (EVOL) AND INTERNATIONAL WORKSHOP ON PRINCIPLES OF SOFTWARE EVOLUTION (IWPSE) ( ASSOC COMPUTING MACHINERY )    135 - 143   2009  [Refereed]

    　View Summary

    As open source software products have evolved over time to satisfy a variety of demands from increasing users, they have become large and complex in general. Open source developers often face with challenges in fixing a considerable amount of bugs which are reported into a bug tracking system on a daily basis. As a result, he mean time to resolve bugs has been protracted in these days. In order to reduce the mean time to resolve bugs, managers/leaders of open source projects need to identify and understand the bottleneck of a bug modification process in their own projects. In this paper, we propose an analysis method which represents a bug modification process using a bug tracking system as a state transition diagram and then calculates the amount of time required to transit between states. We have conducted a case study using Firefox and Apache project data to confirm the usefulness of the analysis method. From the results of the case study, we have found that the method helped to reveal that both of the projects took a lot of time to verify results of bug modifications by developers.

    DOI

  • A Time-Lag Analysis for Improving Communication among OSS Developers.

    Masao Ohira, Kiwako Koyama, Akinori Ihara, Shinsuke Matsumoto, Yasutaka Kamei, Ken-ichi Matsumoto

    New Frontiers in Artificial Intelligence, JSAI-isAI 2009 Workshops, LENLS, JURISIN, KCSD, LLLL, Tokyo, Japan, November 19-20, 2009, Revised Selected Papers ( Springer )    135 - 146   2009  [Refereed]

    DOI

  • OSS開発における情報交換の効率改善へ向けたタイムラグ分析手法の提案

    小山 貴和子, 伊原 彰紀, 本 真佑, 亀井 靖高, 大平 雅雄, 松本 健一

    情報処理学会シンポジウム グループウェアとネットワークサービスワークショップ2009 論文集   2009 ( 8 ) 81 - 86   2009  [Refereed]

  • OSSの開発状況理解支援のための可視化手法の提案

    伊原 彰紀, 大平 雅雄, 本 真佑, 松本 健一

    情報処理学会シンポジウム グループウェアとネットワークサービス・ワークショップ 2009 論文集   2009 ( 8 ) 63 - 64   2009

  • オープンメディアを活用した知識コミュニティのデザインに関する一考察

    大平 雅雄, 本 真佑, 伊原 彰紀, 松本 健一

    情報社会学会 知識共有コミュニティワークショップ -インターネット上の知識検索サービス研究-     1 - 10   2008.11  [Refereed]

  • OSSプロジェクトにおける障害に関する情報共有の分析

    伊原 彰紀, 亀井 靖高, 大平 雅雄, 本 真佑, 松本 健一

    平成20年度 情報処理学会関西支部支部大会 講演論文集   2008   69 - 72   2008

  • Analysis of Network in an OSS Community with Multiple Sub Communities

    伊原彰紀, 大平雅雄, 松本真佑, 亀井靖高, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2008 ( 1 ) 297 - 303   2008  [Refereed]

  • Analysis of Coordinators in an OSS Community with Multiple Sub Communities

    伊原彰紀, 前島弘敬, まつ本真佑, 亀井靖高, 大平雅雄, 松本健一

    情報処理学会シンポジウム論文集   2007 ( 11 ) 13 - 18   2007

▼display all

Books etc

  • ソフトウェア品質知識体系ガイド : SQuBOK guide v3

    SQuBOK策定部会, 飯泉, 紀子, 鷲崎, 弘宜, 誉田, 直美( Part： Contributor,  Work： 第５章１節「オープンソースソフトウェア開発における品質」)

    オーム社  2020.11  ISBN: 9784274226311

Misc

  • 発生頻度の少ないコーディング規約違反データ統合による検出精度向上への試み

    亀岡 令, 伊原 彰紀, 南 雄太, 大森 楓己

    第85回全国大会講演論文集     2023.04

  • README修正内容に関連するソースコード変更コミット追跡への試み

    白崎 優奈, 伊原 彰紀, 石岡 直樹 （Part： Corresponding author )

    第85回全国大会講演論文集     2023.04

  • 直感的なScratch作品検索のためのユーザ入力タイミング特定の試み

    岡本 圭悟, 伊原 彰紀, 三倉 舞子, 橋谷 直樹 （Part： Corresponding author )

    第85回全国大会講演論文集     2023.04

  • マイクロベンチマークデータセットを用いたプログラム実行速度改善の試み

    大森 楓己, 伊原彰紀, 才木 一也, 柏 祐太郎 （Part： Corresponding author )

    信学技報   122 ( 432 ) 55 - 60   2023.03

  • 後方互換性の損失に伴うテストコード変更内容の分類

    前川 大樹, 伊原 彰紀, 大森 楓己, 才木 一也 （Part： Corresponding author )

    第85回全国大会講演論文集     2023.03

  • バージョンに導入される変更提案の特徴分析

    上中 瑞稀, 伊原 彰紀, 柏 祐太郎 （Part： Corresponding author )

    信学技報   122 ( 432 ) 79 - 84   2023.03

  • Scratch作品の再利用による学習効果の分析

    橋谷 直樹, 伊原 彰紀 （Part： Corresponding author )

    研究報告ソフトウェア工学（SE）   2022-SE-212 ( 5 ) 1 - 8   2022.12

  • READMEにおける項目と説明文の一貫性の分析

    石岡 直樹, 伊原 彰紀 （Part： Corresponding author )

    第28回ソフトウェア工学の基礎ワークショップ     2022.11  [Refereed]

  • Scratchにおける類似動作を含む作品間のプログラム類似性の分析

    三倉 舞子, 伊原 彰紀, 橋谷 直樹 （Part： Corresponding author )

    情報処理学会関西支部支部大会講演論文集(CD-ROM) 2022     1 - 4   2022.09

  • ソフトウェアリリースに向けて優先的に検証する変更提案の分析

    上中瑞稀, 伊原彰紀, 牧之瀬丈裕, 南雄太 （Part： Corresponding author )

        1 - 2   2022.03

  • プロジェクト固有の特徴に基づくコーディング規約違反の修正判定基準の分析

    南雄太, 伊原彰紀, 福元春輝 （Part： Corresponding author )

    情報処理学会 第84回全国大会講演論文集     1 - 2   2022.03

  • 機能導入判定に向けた GitHub における要求依頼文章の分析

    久保優斗, 伊原彰紀, 石岡直樹, 松田和輝, 才木一也 （Part： Corresponding author )

    情報処理学会 第84回全国大会講演論文集     1 - 2   2022.03

  • 障害内容に応じたソースコード修正方法の分析

    大森楓己, 伊原彰紀, 松田和輝, 才木一也 （Part： Corresponding author )

    情報処理学会 第84回全国大会講演論文集     1 - 2   2022.03

  • ライブラリのテストケース変更に基づく後方互換性の実証的分析

    松田和輝, 伊原彰紀, 才木一也 （Part： Corresponding author )

    ソフトウェア工学の基礎ワークショップ論文集     139 - 144   2021.11  [Refereed]

    DOI

  • オブジェクト動作経路の時系列解析に基づくビジュアルプログラム作品検索の試み

    福地ユキ, 伊原彰紀, 山本豪志朗, 橋谷直樹 （Part： Corresponding author )

    第28回ソフトウェア工学の基礎ワークショップ ポスター     2021.11

  • コーディング規約違反の優先順位付けに向けた修正時間見積もり手法の提案

    南雄太, 伊原彰紀, 福元春輝 （Part： Corresponding author )

    第28回ソフトウェア工学の基礎ワークショップ ポスター     2021.11  [Refereed]

  • コードレビューにおけるソースコード修正の共変更パターンの抽出

    福元春輝, 伊原彰紀

    ソフトウェアエンジニアリングシンポジウム2021 ポスター     2021.09  [Refereed]

  • 共変更されるソースコード修正パターンの抽出

    福元春輝, 伊原彰紀

    情報処理学会関西支部支部大会講演論文集(CD-ROM)   2021   2021.09

  • 組込みソフトウェア製品開発のプロジェクト管理に対する遅延相関分析の適用に向けて

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

    ソフトウェアエンジニアリングシンポジウム2021論文集   2021   200 - 208   2021.09  [Refereed]

  • ビジュアルプログラミング作品検索のためのオブジェクト操作データの時系列解析

    福地ユキ, 伊原彰紀, 山本豪志朗, 橋谷直樹 （Part： Corresponding author )

    情報処理学会関西支部支部大会講演論文集(CD-ROM)   2021   2021.09

  • Scratchにおけるコンピュテーショナル・シンキングスキルに基づく学習者の習熟度到達予測

    安東 亮汰, 伊原 彰紀 （Part： Corresponding author )

    ソフトウェアエンジニアリングシンポジウム2021論文集   2021   59 - 66   2021.09  [Refereed]

  • READMEにおける見出しの同定処理に向けた説明文分析

    石岡直樹, 伊原彰紀, 南雄太 （Part： Last author )

    情報処理学会 第83回全国大会講演論文集     1 - 2   2021.03

  • オブジェクト操作入力に基づくビジュアルプログラミング作品検出の試み

    福地ユキ, 伊原彰紀, 山本豪志朗, 橋谷直樹 （Part： Last author,　Corresponding author )

        1 - 2   2021.03

  • An Analysis of Source Code Feature Evolution until Solving Coding Standard Violation

    南雄太, 福元春輝, 伊原彰紀

    情報処理学会研究報告(Web)   2021 ( SE-207 )   2021

  • A Classification of Micro Benchmark using Program Snippets

    才木一也, 伊原彰紀

    情報処理学会研究報告(Web)   2021 ( SE-207 )   2021

  • Scratchにおいて再利用される作品の説明文の分析

    橋谷直樹, 伊原彰紀, 安東亮汰 （Part： Corresponding author )

    第27回ソフトウェア工学の基礎ワークショップ     151 - 152   2020.11  [Refereed]

  • 社会的相互作用に着目したGitHubリポジトリへのスター付与数の見積もり手法

    橋本大輝, 伊原彰紀, 小口知希

    情報処理学会関西支部支部大会講演論文集(CD-ROM)   2020   2020.09

  • Scratchプログラミング学習におけるコンピュテーショナル・シンキングスキルの習熟過程の分析

    安東亮汰, 伊原彰紀 （Part： Corresponding author )

        2020.09

  • Analysis of Software Performance Improvement Approach in Microbenchmarking Service

    才木一也, 安東亮汰, 伊原彰紀

    電子情報通信学会技術研究報告   119 ( 451(SS2019 41-60)(Web) )   2020.03

  • コンピューテーショナル・シンキングスキルに基づくScratchプログラムの特徴分析

    安東亮汰, 伊原彰紀

    情報処理学会関西支部支部大会講演論文集(CD-ROM)   2019   2019

  • プルリクエストにおける開発者の変更提案の分類

    福元春輝, 伊原彰紀, 石尾隆, 上田祐己

    情報処理学会関西支部支部大会講演論文集(CD-ROM)   2019   2019

  • 根圏微生物群の分布及びその共生効果の計測を通じた有用微生物の単離・活用

    晝間敬, 伊原彰紀, 岡田豪, 武富貴史, 山本豪志朗

    アグリバイオ   2 ( 2 )   2018

  • 根圏微生物群の分布及びその共生効果の計測を通じた有用微生物の単離・活用

    晝間敬, 伊原彰紀, 岡田豪, 武富貴史, 山本豪志朗

    アグリバイオ   2 ( 6 )   2018

  • ソフトウェア開発における同時バージョン変更される併用ライブラリの推薦

    桂川大輝, 伊原彰紀, ラウラ ガイコビナクラ, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2018 ( 1 )   2018

  • An Analysis of the Impact of Temporal Changes of Developers’ Activities on the Committer Candidate Prediction Model

    山崎大輝, 大平雅雄, 伊原彰紀, 柏祐太郎, 柏祐太郎, 宮崎智己

    電子情報通信学会技術研究報告   118 ( 137(SS2018 1-17)(Web) )   2018

  • ソーシャルコーディングにおけるソースコード中のIf文自動検証システムの開発

    上田裕己, 伊原彰紀, 石尾隆, 桂川大輝, 森田純恵, 菊池慎司, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2018 ( 1 )   2018

  • ソフトウェア開発において併用されるライブラリ機能の推薦

    桂川大輝, 伊原彰紀, ラウラ ガイコビナクラ, 松本健一

    情報処理学会研究報告(Web)   2017 ( SE-197 )   2017

  • X-ray Projection Imaging for Understanding Rhizosphere Flora Activities: Primitive Trials and Future Prospective

    武富貴史, 晝間敬, 岡田豪, 伊原彰紀, 山本豪志朗

    電子情報通信学会技術研究報告   116 ( 259(PRMU2016 90-109) )   2016

  • OSS開発におけるパッチの特徴量を用いた再投稿要求の予測

    安藤聡志, 伊原彰紀, 関浩之, 平尾俊貴, 則兼卓人, 松本健一

    情報処理学会研究報告(Web)   2016 ( SE-194 )   2016

  • Open Data in Software Engineering Field-Open Data for Source Code Review-

    則兼卓人, 伊原彰紀, 平尾俊貴, 松本健一

    電子情報通信学会技術研究報告   116 ( 259(PRMU2016 90-109) )   2016

  • Toward Building Fault-Prone Module Prediction Using Class Curve

    藤野 啓輔, 坂口 英司, Yongpisanpop Papon, 伊原 彰紀, 松本 健一

    ウィンターワークショップ2015・イン・宜野湾 論文集   2015   31 - 32   2015.01

  • Quantifying the Evolution of Open Source Software Focusing on Code Clone and Used Libraries

    若林洸太, 門田暁人, 伊原彰紀, 玉田春昭

    情報処理学会研究報告(Web)   2015 ( SE-190 )   2015

  • OSS開発のプロジェクト事情による不具合修正時間の分析

    若元亮樹, 伊原彰紀, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2015 ( 1 )   2015

  • オープンソースソフトウェアにおけるテストコードの保守頻度と生存期間の分析

    坂口英司, 南智孝, 伊原彰紀, 松本健一

    情報処理学会研究報告(Web)   2015 ( SE-190 )   2015

  • An Analysis of Developers' Activities Contributed to Multi-open Source Projects

    坂口 英司, 伊原 彰紀, 尾上 紗野, 畑 秀明, 松本 健一

    研究報告グループウェアとネットワークサービス（GN）   2014 ( 15 ) 1 - 4   2014.05

    　View Summary

    オープンソースソフトウェア (OSS) プロジェクトは，複数のプロジェクトに参加する開発者が OSS プロジェクトを成功に導いていると過去の研究では示唆している．しかし，具体的なエビデンスは示されていない．なぜなら，以前は多くのプロジェクトが独自で開発履歴を記録するサーバを構築していたため，複数のプロジェクトに参加する開発者の開発経験を正確に理解することが容易ではなかったからである．近年，多くの OSS プロジェクトがホスティングサイト GitHub を利用するようになり，複数のプロジェクトに参加する開発者の活動経験を調査することが容易になった．本論文では，複数のプロジェクトで活動する開発者が OSS プロジェクトに与える影響を明らかにするために，GitHubに記録される開発者の各プロジェクトへの貢献を調査する．

  • Tracing Patch Review Process in Open Source Software Project

    大坂 陽, 伊原 彰紀, 亀井 靖高, 鵜林 尚靖

    ウィンターワークショップ2014・イン・大洗 論文集   2014   19 - 20   2014.01

  • クラッシュレポートが不具合修正に与える影響の分析

    小須田光, 亀井靖高, 伊原彰紀, 鵜林尚靖

    情報処理学会研究報告(Web)   2014 ( SE-183 )   2014

  • パッチレビュープロセスによるパッチ作成者の継続性の違い

    大坂陽, 伊原彰紀, 亀井靖高, 松本健一, 鵜林尚靖

    情報処理学会研究報告(Web)   2014 ( SE-184 )   2014

  • オープンソースプロジェクト特性に基づくバグ収束過程の理解

    坂口英司, SHADE Ruangwan, 伊原彰紀, ARNON Rungsawang, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2014 ( 1 )   2014

  • An Analysis of Developers' Activities Contributed to Multi-open Source Projects

    SAKAGUCHI HIDESHI, IHARA AKINORI, ONOUE SAYA, HATA HIDEAKI, MATSUMOTO KEN-ICHI

    IEICE technical report. Life intelligence and office information systems ( 一般社団法人電子情報通信学会 )  114 ( 32(LOIS2014 1-10) ) 87 - 90   2014

    　View Summary

    オープンソースソフトウェア(OSS)プロジェクトは,複数のプロジェクトに参加する開発者がOSSプロジェクトを成功に導いていると過去の研究では示唆している.しかし,具体的なエビデンスは示されていない.なぜなら,以前は多くのプロジェクトが独自で開発履歴を記録するサーバを構築していたため,複数のプロジェクトに参加する開発者の開発経験を正確に理解することが容易ではなかったからである.近年,多くのOSSプロジェクトがホスティングサイトGitHubを利用するようになり,複数のプロジェクトに参加する開発者の活動経験を調査することが容易になった.本論文では,複数のプロジェクトで活動する開発者がOSSプロジェクトに与える影響を明らかにするために,GitHubに記録される開発者の各プロジェクトへの貢献を調査する.

  • OSS開発におけるレビュアー間の合意形成の分析

    林宏徳, 伊原彰紀, 松本健一

    ワークショップ2013 （GN Workshop 2013) 論文集   2013   1 - 8   2013.11

  • 不具合修正プロセス効率化に向けた修正者の立場から見た管理者別タスク優先度の比較

    吉行勇人, 大平雅雄, 伊原彰紀

    ソフトウェアエンジニアリングシンポジウム2013論文集   2013   1 - 2   2013.09

  • 学習データの時間的変化に伴う欠陥モジュール予測モデルの評価

    内垣聖史, 伊原彰紀, 門田暁人, 松本健一

    ソフトウェアエンジニアリングシンポジウム2013論文集   2013   1 - 2   2013.09

  • 第10回MSRの参加報告

    山下一寛, 角田雅照, 伊原彰紀, 亀井靖高

    研究報告ソフトウェア工学（SE） ( 一般社団法人情報処理学会 )  2013 ( 13 ) 1 - 2   2013.07

    　View Summary

    本稿では，2013 年 5 月にサンフランシスコで開催された Working Conference on Mining Software Repositories (MSR) の内容について報告する．

  • OSS開発におけるコミッターによる協調作業の一考察

    林宏徳, 伊原彰紀, 門田暁人, 松本健一

    研究報告セキュリティ心理学とトラスト（SPT）   2013 ( 6 ) 1 - 4   2013.05

    　View Summary

    昨今，ソフトウェア開発のコスト削減を目的として，商用ソフトウェアの一部にオープンソースソフトウェア (OSS) を利用する企業が増加している．OSS 導入時には，対象プロジェクトのリリース後における保守体制を理解することが重要であり，OSS 開発の不具合修正プロセスを分析する研究が進んでいる．不具合修正プロセス中のコミッターによるレビュー作業は，ソフトウェアをリリースする直前の作業であり，ソフトウェアの品質に最も影響を与える．したがって，コミッターの不十分なレビュー作業は開発の手戻り （再修正） を引き起こし作業効率の低下に繋がる．そこで本稿はコミッターのレビュー作業による OSS 品質への影響について考察する．

  • クラッシュログを用いたソースコード不具合箇所の特定に向けた分析

    長本貴光, 亀井靖高, 伊原彰紀, 鵜林尚靖

    研究報告ソフトウェア工学（SE）   2013 ( 12 ) 1 - 6   2013.03

    　View Summary

    ソフトウェアの品質向上を目的として，クラッシュレポートを収集する開発プロジェクトが増えている．クラッシュレポートは，ソフトウェアがクラッシュした際に自動的に開発プロジェクトに送信され，その内容は実行環境に関する情報 （バージョン，OS，メモリ情報等） をまとめたものである．本研究では，不具合の修正箇所の特定にかかる労力を軽減するために，クラッシュレポートからソースコードの不具合箇所を自動的に特定することを最終的な目標としている．本稿では，その前段階として，クラッシュレポートからソースコードの修正箇所をどのように関連付けられるかについて分析を行った．Firefox を対象に行ったケーススタディの結果，クラッシュレポートのバグ含有率，及び，リンク率は，全バージョンの平均でそれぞれ 62．26 %と 15．4 %であった．

  • Industry Application of Research Findings from Mining Software Repositories

    門田 暁人, 伊原 彰紀

    ウィンターワークショップ2013・イン・那須 論文集   2013   21 - 22   2013.01

  • Discussion of A Method for Redundancy to Invoke Tasks and A Method To Keep A Priority Order for Dispatching A Task in the Embedded RTOS

    平井勝彦, 伊原彰紀, 門田暁人, 松本健一

    情報処理学会研究報告(CD-ROM)   2012 ( 6 )   2013

  • クラッシュログを用いたソースコード不具合箇所の特定に向けた分析

    長本貴光, 亀井靖高, 伊原彰紀, 鵜林尚靖

    情報処理学会研究報告(CD-ROM)   2012 ( 6 )   2013

  • OSS開発における一般開発者の協調作業と不具合の再修正に関する一考察

    林宏徳, 伊原彰紀, 門田暁人, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2013 ( 2 )   2013

  • Predicting the Bug Fixing Time Based on the Bug Assignment Patterns in OSS Development

    正木仁, 大平雅雄, 伊原彰紀, 松本健一

    情報処理学会論文誌ジャーナル(CD-ROM)   54 ( 2 )   2013

  • OSSプロジェクトにおけるユーザ用メーリングリストの実態調査

    伊原彰紀, 松本健一

    電子情報通信学会技術研究報告   113 ( 43(LOIS2013 1-5) )   2013

  • Linking Fixed Bug Report to Source Code Using N-gram

    河居寛樹, 上野秀剛, 伊原彰紀

    電子情報通信学会技術研究報告   112 ( 457(MSS2012 59-86) )   2013

  • OSS開発におけるコミッターによる協調作業の一考察

    林宏徳, 伊原彰紀, 門田暁人, 松本健一

    電子情報通信学会技術研究報告   113 ( 43(LOIS2013 1-5) )   2013

  • Patch Reviewer Recommendation in OSS Projects

    John Boaz Lee, Akinori Ihara, Akito Monden, Ken-ichi Matsumoto

    2013 20TH ASIA-PACIFIC SOFTWARE ENGINEERING CONFERENCE (APSEC 2013), VOL 2 ( IEEE COMPUTER SOC )  2   1 - 6   2013

    　View Summary

    In an Open Source Software (OSS) project, many developers contribute by submitting source code patches. To maintain the quality of the code, certain experienced developers review each patch before it can be applied or committed. Ideally, within a short amount of time after its submission, a patch is assigned to a reviewer and reviewed. In the real world, however, many large and active OSS projects evolve at a rapid pace and the core developers can get swamped with a large number of patches to review. Furthermore, since these core members may not always be available or may choose to leave the project, it can be challenging, at times, to find a good reviewer for a patch. In this paper, we propose a graph-based method to automatically recommend the most suitable reviewers for a patch. To evaluate our method, we conducted experiments to predict the developers who will apply new changes to the source code in the Eclipse project. Our method achieved an average recall of 0.84 for top-5 predictions and a recall of 0.94 for top-10 predictions.

    DOI

  • OSSシステムとコミュニティの共進化の理解を目的としたデータマイニング手法

    山谷陽亮, 大平雅雄, PHANNACHITTA Passakorn, 伊原彰紀

    情報処理学会シンポジウムシリーズ(CD-ROM)   2013 ( 2 ) ROMBUNNO.7E-1   2013

  • OSS開発における共進化プロセスの理解のための遅延相関分析

    山谷陽亮, 大平雅雄, 伊原彰紀

    情報処理学会研究報告(Web)   2013 ( SE-181 ) WEB ONLY VOL.2013-SE-181,NO.3   2013

  • Why is collaboration needed in OSS projects? A case study of eclipse project

    Hironori Hayashi, Akinori Ihara, Akito Monden, Ken-Ichi Matsumoto

    2013 5th International Workshop on Social Software Engineering, SSE 2013 - Proceedings     17 - 20   2013

    　View Summary

    In open source software development, the collaboration among developers is the key to improve software quality. In particular, to fix a bug related to various parts of a system, developers need collaboration because each developer usually has very limited knowledge about a large software system. This paper aims to clarify how narrow (or how wide) is each developer's knowledge area in the Eclipse project, and how often do developers need to collaborate with each other. As a result of analysis, we found that 50 % of committers take care of just one or two modules, which indicates the necessity of collaboration when a bug-fix affects multiple modules. In addition, we also found the significant relationship between committers' collaborations and the re-opened bugs. We conclude that a committer should be aware the risk of re-opened bugs caused by the collaboration. Copyright 2013 ACM.

    DOI

  • 第34回ソフトウェア工学国際会議ICSE2012参加報告

    亀井靖高, 伊原彰紀, 畑秀明, 吉村健太郎, 吉田則裕

    研究報告ソフトウェア工学（SE）   2012 ( 5 ) 1 - 7   2012.07

    　View Summary

    本稿では，2012年6月にチューリッヒで開催されたソフトウェア工学の国際会議ICSE（InternationalConference on Software Engineering）2012に参加した際の会議の内容について報告する．

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

    伊原 彰紀, 亀井 靖高, 大平 雅雄, 松本 健一, 鵜林 尚靖

    ( 電子情報通信学会 )    2012.02

    　View Summary

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

  • An Investigation on Software Bug-Fix Prediction for Open Source Software Projects-A Case Study on the Eclipse Project

    Akinori Ihara, Yasutaka Kamei, Akito Monden, Masao Ohira, Jacky Wai Keung, Naoyasu Ubayashi, Ken-ichi Matsumoto

    2012 19TH ASIA-PACIFIC SOFTWARE ENGINEERING CONFERENCE WORKSHOPS (APSECW), VOL. 2 ( IEEE COMPUTER SOC )  2   112 - 119   2012

    　View Summary

    Open source software projects (OSS) receive a large number of bug reports from various contributors and developers alike, where many planned to be fixed by OSS developers. Given the next release cycle information, OSS users can be more effective and flexible in planning and to fix the bugs that are not to be fixed in the next release. It is therefore vital for OSS users to learn which bugs the OSS developers will fix, unfortunately such information may not be readily available, nor there is a prediction framework exists to serve such an important purpose. In this study, we would like to answer the question "Will this bug be fixed by the next release?", this is addressed by building a bug fixing prediction model based on the characteristics of a bug-related metric and by incorporating the progress of bug fixing measures such as status, period and developer metrics to provide aggregated information for the OSS users. The proposed model calculates the deviance of each variable to analyze the most important metrics, and it has been experimented using a case study with Eclipse platform. Result shows a bug fixing prediction model using both base metrics and state metrics provide significantly better performance in precision (139%) and recall (114%) than the standard model using only base metrics.

    DOI

  • OSS開発における保守対応の効率化のためのアウェアネス支援システム

    伊原彰紀, 山本瑞起, 大平雅雄, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2010 ( 1 ) 1620 - 1629   2010

  • OSS開発におけるパッチレビュープロセスの効率化に向けたコミッターの分類

    藤田将司, 伊原彰紀, 大平雅雄, 松本健一

    情報処理学会関西支部支部大会講演論文集(CD-ROM)   2010   ROMBUNNO.B-05   2010

  • 不具合管理システム利用時の不具合修正プロセス改善のための滞留時間分析手法の提案

    伊原彰紀, 大平雅雄, 松本健一

    情報処理学会シンポジウムシリーズ(CD-ROM)   2009 ( 1 ) 1221 - 1227   2009

▼display all

Awards & Honors

  • 論文編集貢献賞

    Winner： 伊原彰紀

    2023.05   情報処理学会  

  • 情報処理学会論文誌ジャーナル特選論文

    Winner： 安東 亮汰, 伊原 彰紀

    2022.04   情報処理学会  

  • 最優秀論文賞

    Winner： 安東 亮汰, 伊原 彰紀

    2021.09   情報処理学会ソフトウェアエンジニアリングシンポジウム2021  

  • 卓越研究賞（SE研究会）

    Winner： Bodin Chinthanet, Raula Gaikovina Kula, Shane McIntosh, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto

    2021.09   情報処理学会  

  • インタラクティブ・ポスター賞

    Winner： 福元 春輝, 伊原 彰紀

    2021.09   情報処理学会ソフトウェアエンジニアリングシンポジウム2021  

  • IPSJ SIG Software Engineering (SIGSE) Achievement Award

    Winner： Kenichi Matsumoto, Akinori Ihara

    2021.03   情報処理学会  

  • 卓越研究賞（SE研究会）

    Winner： Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto

    2020.09   情報処理学会  

  • 卓越研究賞

    Winner： Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto

    2019.08   IPSJ   The Review Linkage Graph for Code Review Analytics

  • People's Choice Award

    Winner： Yuki Ueda, Takashi Ishio, Akinori Ihara, Kenichi Matsumoto

    2019.02   International Workshop on Software Clones   Mining Source Code Improvement Patterns from Similar Code Review Works

  • Best Poster Award

    Winner： Ryota Ando, Akinori Ihara

    2018.12   IWESEP2018   Toward identifying similar program without using Remix in Scratch

  • Young Professional Award

    Winner： Akinori Ihara

    2018.02   IEEE KANSAI Branch  

  • 貢献賞

    Winner： Shohei Ikeda, Akinori Ihara

    2017.11   ソフトウェア工学の基礎ワークショップ2017  

  • インタラクティブ特別賞

    Winner： Yuki Ueda, Akinori Ihara, Toshiki Hirao, Takashi Ishio, Kenichi Matsumoto

    2017.08   情報処理学会ソフトウェアエンジニアリングシンポジウム2017  

  • Best Paper Award

    Winner： Akinori Ihara, Daiki Fujibayashi, Hirohiko Suwa, Raula Gaikovina Kula, Kenichi Matsumoto

    2017.05   OSS2017  

  • インタラクティブ賞

    Winner： Toshiki Hirao, Akinori Ihara, Shane McIntosh, Kenichi Matsumoto

    2016.08   情報処理学会ソフトウェアエンジニアリングシンポジウム2016  

  • インタラクティブ賞

    Winner： Hideshi Sakaguchi, Akinori Ihara, Kenichi Matsumoto

    2015.08   情報処理学会ソフトウェアエンジニアリングシンポジウム2015  

  • Best Poster Award

    Winner： Keisuke Fujino, Akinori Ihara, Kenichi Matsumoto, Kiyoshi HOnda, Hironori Washizaki

    2014.11   IWESEP2014  

  • ベストペーパー賞

    Winner： 林 宏徳, 伊原 彰紀, 松本 健一

    2013.11   情報処理学会 GN研究会  

  • Best Paper Award

    Winner： 山谷 陽亮, 大平 雅雄, Passakorn Phannachitta, 伊原 彰紀, 松本 健一

    2013.09   DICOMO2013  

  • 優秀論文賞

    Winner： 林 宏徳, 伊原 彰紀, 松本 健一

    2013.09   情報処理学会DICOMO2013  

  • Best Student Award

    Winner： Akinori Ihara

    2012.03   Nara Institute of Science and Technology  

  • Best Student Paper Award

    Winner： Anakorn Jongyindee, Masao Ohira, Akinori Ihara, Kenichi Matsumoto

    2011.11   IWSM/MENSURA2011  

  • Best Paper Award

    Winner： Emad Shihab, Akinori Ihara, Yasutaka Kamei, Walid M. Ibrahim, Masao Ohira, Bram Adams, Naoyasu Ubayashi, Ahmed E. Hassan, Kenichi Matsumoto

    2010.10   WCRE2010  

  • 優秀プレゼンテーション賞

    Winner： Akinori Ihara, Mizuki Yamamoto, Masao Ohira, Kenichi Matsumoto

    2010.07   情報処理学会DICOMO2010  

  • ヤングリサーチャ賞

    Winner： Akinori Ihara, Masao Ohira, Kenichi Matsumoto

    2009.07   情報処理学会DICOMO2009  

  • 学生奨励賞

    Winner： Akinori Ihara

    2008.09   情報処理学会関西支部支部大会2008  

  • 優秀論文賞

    Winner： Akinori Ihara, Masao Ohira, Shinsuke Matsumoto, Yasutaka Kamei, Kenichi Matsumoto

    2008.09   情報処理学会DICOMO2008  

▼display all

Conference Activities & Talks

  • 条件付き採録を通すには

    伊原彰紀  [Invited]

    情報処理学会第85回全国大会 論文必勝法  2023.03.04  

  • 実行効率性改善に特化したモデル学習がソースコード自動修正に与える効果

    大森 楓己, 伊原 彰紀, 才木 一也

    第28回ソフトウェア工学の基礎ワークショップ  2022.11.11  

  • ナップサック問題に基づく検証すべき変更提案の選定

    上中 瑞稀, 伊原 彰紀, 柏 祐太郎

    第28回ソフトウェア工学の基礎ワークショップ  2022.11.11  

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

    Akinori Ihara  [Invited]

    第21回情報科学技術フォーラム（FIT2022）  2022.09.15  

  • データサイエンスのはじめの一歩

    伊原彰紀  [Invited]

    有田ロータリークラブ  2021.04.08  

  • The Review Linkage Graph for Code Review Analytics: A Recovery Approach and Empirical Study

    Toshiki Hirao, Shane McIntosh, Akinori Ihara, Kenichi Matsumoto  [Invited]

    ソフトウェアエンジニアリングシンポジウム2020  2020.09.11  

  • Identifying and Predicting Key Features to Support Bug Reporting

    Md. Rejaul Karim, Akinori Ihara, Eunjong Choi, Hajimu Iida  [Invited]

    ソフトウェアエンジニアリングシンポジウム2020  2020.09.11  

  • The International Conference on Software Maintenance and Evolution

    Md. Rejaul Karim, Akinori Ihara, Eunjong Choi, Hajimu Iida  [Invited]

    The International Conference on Software Maintenance and Evolution 2019  2019.10.02  

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

    Shade Ruangwan, atanamon Thongtanunam, Akinori Ihara, Kenichi Matsumoto  [Invited]

    ソフトウェアエンジニアリングシンポジウム2019  2019.08.31  

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

    Shade Ruangwan, Patanamon Thongtanunam, Akinori Ihara, Kenichi Matsumoto  [Invited]

    International Conference on Software Engineering  2019.05.31  

  • ソフトウェア自動検証技術の開発

    伊原彰紀  [Invited]

    わかやまテクノ・ビジネスフェア  2018.12  

▼display all

KAKENHI

  • 技術的負債エンジニアリング － 優先的に解決すべき技術的負債の解明とモデル化

    2018.04
    -
    2022.03
     

    Grant-in-Aid for Scientific Research(B)  Co-investigator

  • 実行トレース共有リポジトリを用いたソフトウェア変更の影響レビュー技術の研究

    2018.04
    -
    2022.03
     

    Grant-in-Aid for Scientific Research(B)  Co-investigator

  • 超長寿命ソフトウェアを実現する自律的な保守性強化技術の研究

    2018.04
    -
    2021.03
     

    Grant-in-Aid for Scientific Research(B)(Generative Research Field)  Principal investigator

  • 自発的ソフトウェア進化の加速に向けた基礎技術の開発

    2017.04
    -
    2020.03
     

    Grant-in-Aid for Scientific Research(A)  Co-investigator

  • OSSとコミュニティの共進化に基づくソフトウェア信頼性の理解と操作

    2016.04
    -
    2019.03
     

    Grant-in-Aid for Young Scientists(B)  Principal investigator

Competitive funding, donations, etc. from foundation, company, etc.

  • システム工学部寄附金（公益財団法人栢森情報科学振興研究助成金）

    2022.01
    -
    2023.12
     

    Research subsidy  Principal investigator

  • システム工学部寄附金（一般財団法人テレコム先端技術研究支援センター研究助成）

    2019.04
    -
    2020.03
     

    Research subsidy  Principal investigator

  • システム工学部寄附金（一般財団法人テレコム先端技術研究支援センター研究助成）

    2018.04
    -
    2019.03
     

    Research subsidy  Principal investigator

Joint or Subcontracted Research with foundation, company, etc.

  • 分散型IDの活用が社会に及ぼす影響に関する研究

    2023.03
    -
    2024.03
     

    Joint research  Principal investigator

Instructor for open lecture, peer review for academic journal, media appearances, etc.

  • 非常勤講師

    2023.10.01
    -
    2024.03.31

    放送大学

    　View Details

    データサイエンス

    和歌山学習センターにおける面接授業講師

  • 講師

    2022.10.14

    和歌山県立田辺高等学校

    　View Details

    データサイエンス

    本校に来校して頂き、和歌山大学システム工学部の学部説明及び生徒向けに出前講義をしていただきます

  • 非常勤講師

    2022.10.01
    -
    2023.03.31

    放送大学

    　View Details

    データサイエンス

    和歌山学習センターにおける面接授業「データサイエンス」の実施（講師）
    実施日：2022年10月29日（土）・30日（日）

  • 特任教官

    2022.07.20
    -
    2023.09.12

    国土交通省　航空保安大学校

    　View Details

    当校研修生への講義支援

    当校のシステム専門官基礎研修課程において「オブジェクト指向プログラミング演習」の講義を依頼するもの

  • システム評価アドバイザー

    2022.04.01
    -
    2024.03.31

    和歌山市

    　View Details

    地域システム評価

    システム評価会議においてシステム評価及び助言を行う。

  • プログラム委員

    2022.04.01
    -
    2023.03.31

    ソフトウェア科学会, 第29回ソフトウェア工学の基礎ワークショップ (FOSE2022)

    　View Details

    国内会議査読

    国内会議論文の査読

  • プログラム委員

    2022.04.01
    -
    2023.03.31

    情報処理学会, ソフトウェアエンジニアリングシンポジウム2022

    　View Details

    国内会議査読

    国内会議論文の査読

  • Program Committee

    2022.04.01
    -
    2023.03.31

    Asia-Pacific Software Engineering Conference (APSEC) 2022

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2022.04.01
    -
    2023.03.31

    IEEE International Conference on Software Maintenance and Evolution (ICSME) 2022

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2022.04.01
    -
    2023.03.31

    International Conference on Open Source Systems (OSS) 2022

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2022.04.01
    -
    2023.03.31

    ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) 2022

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2022.04.01
    -
    2023.03.31

    IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) 2023

    　View Details

    国際会議査読

    国際会議論文の査読

  • 論文誌査読委員

    2022.04
    -
    2023.03

    ソフトウェア科学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • Journal referee

    2022.04
    -
    2023.03

    Journal of Empirical Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2022.04
    -
    2023.03

    Journal of Transactions on Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • 論文誌査読委員

    2022.04
    -
    2023.03

    情報処理学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • 博士学位審査委員

    2021.11.04
    -
    2022.02.28

    奈良先端科学技術大学院大学情報科学研究科

    　View Details

    助言・指導

    本学博士後期課程学生が提出する博士学位論文に対する審査，ならびに，助言

  • 非常勤講師

    2021.10.01
    -
    2022.03.31

    放送大学

    　View Details

    非常勤講師

    和歌山学習センターにおける面接授業「データサイエンス」の実施（講師）
    実施日：2021年10月30日（土）・31日（日）

  • 学位審査委員

    2021.07.16
    -
    2021.09.09

    国立大学法人奈良先端科学技術大学院大学

    　View Details

    助言・指導

    博士後期課程学生の博士学位審査

  • 特任教官

    2021.07.01
    -
    2021.07.31

    国土交通省　航空保安大学校

    　View Details

    非常勤講師

    当校のシステム専門官基礎研修生に対し「オブジェクト指向プログラミング演習」に関する研修の講師を依頼（日程及び職務内容について内諾済み）。

  • 講演講師

    2021.04.08

    有田ロータリークラブ

    　View Details

    データサイエンス

    講演（卓話）
    ZOOMもしくは対面にて講演

  • 講演発表者

    2021.04.01
    -
    2022.03.31

    International Conference on Software Engineering (ICSE) 2021

    　View Details

    講演

    講演

  • 非常勤講師

    2021.04.01
    -
    2022.03.31

    国立大学法人奈良先端科学技術大学院大学

    　View Details

    助言・指導

    オープンソースソフトウェアの開発コミュニティに蓄積されている「ソフトウェア開発データ」を研究室における教育研究活動にどのように活用し、また、活用のために教育研究方法そのものをどのように工夫・改善すべきか、について助言を行う。

  • Program Committee

    2021.04.01
    -
    2022.03.31

    IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) 2022

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2021.04.01
    -
    2022.03.31

    Asia-Pacific Software Engineering Conference (APSEC) 2021

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2021.04.01
    -
    2022.03.31

    18th IEEE/ACIS International Virtual Conference on Software Engineering, Management and Applications (SERA) 2021

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2021.04.01
    -
    2022.03.31

    ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2021.04.01
    -
    2022.03.31

    IEEE/ACM International Conference on Automated Software Engineering (ASE) 2021

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2021.04.01
    -
    2022.03.31

    IEEE International Conference on Software Maintenance and Evolution (ICSME) 2021

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2021.04.01
    -
    2022.03.31

    International Conference on Open Source Systems (OSS) 2021

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2021.04.01
    -
    2022.03.31

    ACM/IEEE International Conference on Global Software Engineering (ICGSE) 2021

    　View Details

    国際会議査読

    国際会議論文の査読

  • プログラム委員

    2021.04.01
    -
    2022.03.31

    情報処理学会, ソフトウェアエンジニアリングシンポジウム2021

    　View Details

    国内会議査読

    国内会議論文の査読

  • プログラム委員

    2021.04.01
    -
    2022.03.31

    ソフトウェア科学会, 第28回ソフトウェア工学の基礎ワークショップ (FOSE2021)

    　View Details

    国内会議査読

    国内会議論文の査読

  • 講師

    2021.04.01
    -
    2022.03.31

    和歌山大学リカレント教育事業

    　View Details

    リカレント教育

    和歌山大学リカレント授業を担当

  • 編集委員

    2021.04.01
    -
    2022.03.31

    情報処理学会論文誌「若手研究者」特集

    　View Details

    学術論文誌

    学術論文誌の編集委員

  • 編集委員

    2021.04.01
    -
    2022.03.31

    情報処理学会論文誌「ソフトウェア工学」特集

    　View Details

    学術論文誌

    学術論文誌の編集委員

  • Guest Associate Editor-in-Chief

    2021.04.01
    -
    2022.03.31

    Special Section on Empirical Software Engineering

    　View Details

    学術論文誌

    学術論文誌の編集委員

  • 論文誌査読委員

    2021.04.01
    -
    2022.03.31

    ソフトウェア科学会

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員

  • 原稿執筆

    2020.08.19

    一般財団法人テレコム先端技術研究支援センター

    　View Details

    情報提供

    技術情報誌「TELECOM FRONTIER」第108号への伊原先生の研究成果執筆

  • 博士学位論文審査委員

    2020.07.10
    -
    2020.09.30

    国立大学法人奈良先端科学技術大学院大学

    　View Details

    「学協会、政府、自治体等の公的委員」以外の委員

    本学博士学位論文審査委員として専門的立場から意見をいただく。

  • 論文誌査読委員

    2020.04.01
    -
    Now

    情報処理学会

    　View Details

    学術論文誌

    論文誌査読

  • Journal referee

    2020.04.01
    -
    2021.03.31

    Journal of Software: Evolution and Process

    　View Details

    学術論文誌

    学術論文誌の査読

  • Program Committee

    2020.04.01
    -
    2021.03.31

    International Conference on Empirical Software Engineering and Measurement (ESEM 2019)

    　View Details

    国際会議査読

    国際会議論文の査読

  • Program Committee

    2020.04.01
    -
    2021.03.31

    International Conference on Automated Software Engineering (ASE 2020)

    　View Details

    国際会議査読

    国際会議査読

  • 非常勤講師

    2020.04.01
    -
    2021.03.31

    国立大学法人奈良先端科学技術大学院大学

    　View Details

    非常勤講師

    オープンソースソフトウェアの開発コミュニティに蓄積されている「ソフトウェア開発データ」を研究室における教育研究活動にどのように活用し、また、活用のために教育研究方法そのものをどのように工夫・改善すべきか、について助言を行う。

  • 論文誌査読委員

    2020.04.01
    -
    2021.03.31

    電子情報通信学会

    　View Details

    学術論文誌

    論文誌査読

  • 講師

    2020.04.01
    -
    2021.03.31

    和歌山大学リカレント教育事業

    　View Details

    リカレント教育

    和歌山大学リカレント授業「データサイエンス基礎コース」を担当

  • Journal referee

    2020.04
    -
    2022.03

    Journal of Systems and Software

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2020.04
    -
    2022.03

    Journal of Transactions on Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2020.04
    -
    2022.03

    Journal of Empirical Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2020.04
    -
    2021.03

    IEEE Software

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee

  • 平成30年度非常勤講師

    2019.06
    -
    2019.08

    国立大学法人奈良先端科学技術大学院大学

    　View Details

    非常勤講師等

    平成30年度非常勤講師,任期:2019年6月～2019年8月

  • 平成30年度非常勤講師

    2019.04
    -
    2020.03

    国立大学法人奈良先端科学技術大学院大学

    　View Details

    非常勤講師等

    平成30年度非常勤講師,任期:2019年4月～2020年3月

  • International Workshop on Empirical Software Engineering in Practice 2019

    2019.04
    -
    2020.03

    その他

    　View Details

    国際交流事業

    PC Chair

  • Editorial Committee

    2019.04
    -
    2020.03

    IEICE Special Issue on Empirical Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Editorial Committee,任期:1年

  • Journal referee

    2019.04
    -
    2020.03

    Journal of Empirical Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • 論文誌査読委員

    2019.04
    -
    2020.03

    人工知能学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • Journal referee

    2019.04
    -
    2020.03

    IEEE Transactions on Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2019.04
    -
    2020.03

    Journal of Systems and Software

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2019.04
    -
    2020.03

    Information and Software Technology

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee

  • 論文誌査読委員

    2019.04
    -
    2020.03

    ソフトウェア科学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • 論文誌査読委員

    2019.04
    -
    2020.03

    電子情報通信学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • 論文誌査読委員

    2019.04
    -
    2020.03

    情報処理学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • 社会人向け先端技術教育講座（高度先端技術リカレント教育事業）「データサイエンス基礎」

    2019.04

    和歌山大学

    　View Details

    公開講座・講演会の企画・講師等

    データサイエンス基礎,日付:2019年度1月-2月

  • 平成30年度非常勤講師

    2018.06

    奈良先端科学技術大学院大学

    　View Details

    非常勤講師等

    非常勤講師,任期:2018年6月～2018年6月

  • 論文誌編集委員

    2018.04
    -
    2019.03

    情報処理学会 論文誌ジャーナル/JIP編集委員会

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌編集委員,任期:3年

  • 論文誌編集委員

    2018.04
    -
    2019.03

    情報処理学会論文誌「ソフトウェア工学」特集

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌編集委員,任期:1年

  • 論文誌査読委員

    2018.04
    -
    2019.03

    電子情報通信学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • 論文誌査読委員

    2018.04
    -
    2019.03

    ソフトウェア科学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • Journal referee

    2018.04
    -
    2019.03

    Journal of Systems and Software

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2018.04
    -
    2019.03

    IEEE Transactions on Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • 論文誌査読委員

    2018.04
    -
    2019.03

    情報処理学会論文誌

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    論文誌査読委員,任期:1年

  • Journal referee

    2018.04
    -
    2019.03

    Journal of Software: Evolution and Process

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2018.04
    -
    2019.03

    Journal of Empirical Software Engineering

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee,任期:1年

  • Journal referee

    2018.04
    -
    2019.03

    Information and Software Technology

    　View Details

    学術雑誌等の編集委員・査読・審査員等

    Journal referee

  • 非常勤講師

    2017.04
    -
    2019.03

    国立大学法人奈良先端科学技術大学院大学

    　View Details

    非常勤講師等

    非常勤講師,任期:2017年～2019年３月

▼display all

Committee member history in academic associations, government agencies, municipalities, etc.

  • 学術論文誌運営委員会　主査

    2022.04.01
    -
    2023.03.31
     

    情報処理学会

    　View Details

    学術論文誌

    学術論文誌の審査

  • 編集委員

    2022.04
    -
    2023.03
     

    情報処理学会論文誌「ソフトウェア工学」特集

    　View Details

    学会運営

    学会運営

  • 編集委員

    2022.04
    -
    2023.03
     

    情報処理学会論文誌「ニューノーマル時代を支えるコラボレーション技術とネットワークサービス」特集

    　View Details

    学会運営

    学会運営

  • 幹事

    2021.04.01
    -
    Now
     

    情報処理学会ソフトウェア工学研究会

    　View Details

    学会運営

    学会運営

  • Member at Large

    2021.04.01
    -
    Now
     

    IEEE Computer Society Professional & Educational Activitites Board

    　View Details

    学協会、政府、自治体等の公的委員

    IEEEの組織運営委員

  • 支部運営委員

    2021.04.01
    -
    2023.05.31
     

    情報処理学会関西支部

    　View Details

    学会運営

    学会運営

  • システム評価アドバイザー

    2021.04.01
    -
    2022.03.31
     

    和歌山市役所

    　View Details

    システム評価

    システム評価会議においてシステム評価及び助言を行う

  • Committee

    2020.04.01
    -
    Now
     

    IEEE関西支部 Young Professionals

    　View Details

    学協会、政府、自治体等の公的委員

    若手技術者・研究者のキャリア育成、プロ意識の醸成、研究者間の連携の支援

  • 学術論文誌運営委員会　副査

    2020.04.01
    -
    2022.03.31
     

    情報処理学会

    　View Details

    学術論文誌

    学術論文誌の審査

  • 実行委員長

    2020.04.01
    -
    2021.03.31
     

    IEEE関西

    　View Details

    キャリア

    IEEE関西Young Professional Affinity Group主催で，関西圏を中心に活躍する若手研究者のキャリアについて討論するイベント

  • 実行委員長

    2020.04.01
    -
    2021.03.31
     

    情報処理学会関西支部支部大会

    　View Details

    研究発表会の開催

    研究発表会の開催

  • 学位論文審査

    2019.08
     

    奈良先端科学技術大学院大学

    　View Details

    国や地方自治体、他大学・研究機関等での委員

    学位論文審査,任期:2019年8月～

  • 幹事

    2019.05
    -
    2021.04
     

    情報処理学会関西支部

    　View Details

    学協会、政府、自治体等の公的委員

    学術会議の企画，等,任期:2年

  • Co-Secretary

    2019.04
    -
    2021.03
     

    IEEE Computer Society Professional & Educational Activitites Board

    　View Details

    学協会、政府、自治体等の公的委員

    IEEEの組織運営,任期:2年

  • Chair

    2019.04
    -
    2021.03
     

    IEEE関西支部 Young Professionals

    　View Details

    学協会、政府、自治体等の公的委員

    若手技術者・研究者のキャリア育成、プロ意識の醸成、研究者間の連携の支援,任期:_x0008_2年

  • 招待論文セッション委員長

    2019.04
    -
    2020.03
     

    情報処理学会, ソフトウェアエンジニアリングシンポジウム2019

    　View Details

    学協会、政府、自治体等の公的委員

    学術論文誌で採録された論文の選定，招待発表の依頼,任期:1年

  • 学位論文審査

    2018.08
    -
    Now
     

    奈良先端科学技術大学院大学

    　View Details

    国や地方自治体、他大学・研究機関等での委員

    学位論文審査,任期:2018年8月～

  • 運営委員

    2018.04.01
    -
    2021.03.31
     

    情報処理学会ソフトウェア工学研究会

    　View Details

    学会運営

    学会運営

  • Vice Chair

    2018.04
    -
    Now
     

    IEEE関西支部 Young Professionals

    　View Details

    学協会、政府、自治体等の公的委員

    学協会、政府、自治体等の公的委員

  • Registration Co-Chairs

    2018.04
    -
    2019.03
     

    International Workshop on Empirical Software Engineering in Practice (IWESEP 2018)

    　View Details

    学協会、政府、自治体等の公的委員

    参加登録者の管理,任期:1年

  • Program Chair

    2018.04
    -
    2019.03
     

    International Conference on Big Data, Cloud Computing, and Data Science Engineering (BCD 2018)

    　View Details

    学協会、政府、自治体等の公的委員

    投稿論文の中から採択論文の選別,任期:1年

  • Publicity Co-Chairs

    2018.04
    -
    2019.03
     

    International Conference on Open Source Systems (OSS 2018)

    　View Details

    学協会、政府、自治体等の公的委員

    論文募集のアナウンス,任期:1年

▼display all