DSpace Repository

Browsing by Author "Ihara, Akinori"

Browsing by Author "Ihara, Akinori"

Sort by: Order: Results:

  • Jiarpakdee, Jirayus; Tantithamthavorn, Chakkrit; Ihara, Akinori; Matsumoto, Kenichi (IEEE, 2016)
    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 ...
  • Phannachitta, Passakorn; Ihara, Akinori; Jirapiwong, Pijak; Ohira, Masao; Matsumoto, Kenichi (電子情報通信学会, 2012-09-01)
    Nowadays, software development societies have given more precedence to Open Source Software (OSS). There is much research aimed at understanding the OSS society to sustain the OSS product. To lead an OSS project to a ...
  • Ihara, Akinori; Ohira, Masao; Matsumoto, Ken-ichi (ACM, 2009-08-24)
    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 ...
  • Kitagawa, Norihito; Hata, Hideaki; Ihara, Akinori; Kogiso, Kiminao; Matsumoto, Kenichi (IEEE, 2016)
    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 ...
  • Takasawa, Ryohei; Sakamoto, Kazunori; Ihara, Akinori; Washizaki, Hironori; Fukazawa, Yoshiaki (Springer International Publishing, 2014)
    Do open source software projects provide and maintain tests? What metrics are correlated with the test success? This paper answers these questions by executing tests of 452 open source software projects in GitHub and ...
  • Ihara, Akinori; Kamei, Yasutaka; Ohira, Masao; Hassan, Ahmed E.; Ubayashi, Naoyasu; Matsumoto, Ken-ichi (IEEE, 2014)
    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 ...
  • Jewmaidang, Kanyakorn; Ishio, Takashi; Ihara, Akinori; Matsumoto, Kenichi; Leelaprute, Pattara (電子情報通信学会, 2018-03-01)
    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 ...
  • Jongyindee, Anakorn; Ohira, Masao; Ihara, Akinori; Matsumoto, Kenichi (電子情報通信学会, 2012-09-01)
    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 a software repository, plays a major role in this ...
  • Jongyindee, Anakorn; Ohira, Masao; Ihara, Akinori; Matsumoto, Ken-ichi (IEEE, 2011)
    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 ...
  • Ueda, Yuki; Ihara, Akinori; Hirao, Toshiki; Ishio, Takashi; Matsumoto, Kenichi (IEEE, 2017)
    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 ...
  • Tantithamthavorn, Chakkrit; Ihara, Akinori; Hata, Hideaki; Matsumoto, Kenichi (Springer Berlin Heidelberg, 2014)
    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 ...
  • Ueda, Yuki; Ihara, Akinori; Ishio, Takashi; Matsumoto, Kenichi (IEEE, 2018)
    Code review is key to ensuring the absence of potential issues in source code. Code review is changing from a costly manual check by reviewer to a cost-efficient automatic check by coding style checkers. So that patch ...
  • Ihara, Akinori; Monden, Akito; Matsumoto, Ken-Ichi (IEEE, 2014)
    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 ...
  • Ueda, Yuki; Ishio, Takashi; Ihara, Akinori; Matsumoto, Kenichi (IEEE, 2019)
    Code review is key to ensuring the absence of potential issues in source code. Code reviewers spend a large amount of time to manually check submitted patches based on their knowledge. Since a number of patches sometimes ...
  • 山谷, 陽亮; 大平, 雅雄; パサコーン, パンナチッタ; 伊原, 彰紀 (情報処理学会, 2015-01-15)
    オープンソースソフトウェア(OSS)を活用したシステム開発が一般的になりつつある一方,「サポートが得られるかどうか分からない」などの理由から,依然としてOSSの活用に躊躇するシステム開発企業は少なくない.本研究では,OSSシステムとコミュニティの共進化のプロセスを定量的に分析するためのデータマイニング手法を提案する.本手法は,時間的順序関係を考慮した相関分析を行うためのものであり,一方の系統の進化が一定時間後に他方の系統の進化に影響を与 ...
  • 伊原, 彰紀; 亀井, 靖高; 大平, 雅雄; 松本, 健一; 鵜林, 尚靖 (電子情報通信学会, 2012-02-01)
    本論文では,オープンソースソフトウェア(OSS)プロジェクトに参加する一般開発者の中からコミッターに推薦されるべき有能な開発者(コミッター候補者)を見つけ出すことを目的とする.近年,数百件もの不具合がプロジェクトに日々,報告されている現状から,コミッターへの過度な負担が原因となり不具合修正の長期化を招いている.コミッターの負担を軽減させるためにコミッターを増員するという手段があるが,プロジェクトに参加する一般開発者の中からコミッター候補 ...
  • 正木, 仁; 大平, 雅雄; 伊原, 彰紀; 松本 健一 (情報処理学会, 2013-02-15)
    大規模OSSプロジェクトには日々大量の不具合が報告されており,不具合修正時間(OSSプロジェクトに報告された不具合が解決するまでに要する時間)をより正確に見積もることが重要になってきている.OSSプロジェクト管理者は,次期バージョンのリリースまでにどの不具合を修正すべきかを判断しなければならないためである.しかしながら,不具合の修正範囲の大きさや問題の複雑さの違い,ボランティアを主体とする開発者のスキルセットの違いなどの要因によって,個 ...
  • Hirao, Toshiki; Ihara, Akinori; Matsumoto, Ken-ichi (IBM Corp. Riverton, NJ, USA, 2015-11-02)
    Political arguments and voting requirements often follow a simple majority method which is a decision rule that selects various alternatives that have a majority, that is, more than half the votes. On the other hand, Q&A ...
  • Shihab, Emad; Ihara, Akinori; Kamei, Yasutaka; Ibrahim, Walid M.; Ohira, Masao; Adams, Bram; Hassan, Ahmed E.; Matsumoto, Ken-ichi (IEEE, 2010)
    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 ...
  • Shihab, Emad; Ihara, Akinori; Kamei, Yasutaka; Ibrahim, Walid M.; Ohira, Masao; Adams, Bram; Hassan, Ahmed E.; Matsumoto, Ken-ichi (Springer, 2012-09-20)
    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 ...