![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
#author("2019-01-21T19:14:47+09:00","","") #author("2019-01-21T19:15:02+09:00","","") [[論文英語単語帳/表現集]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) ** 表現集[#s089e92b] #ls2(論文英語単語帳/表現集/) *分野について [#gfb56649] ***重要な側面の一つ [#p5d07965] -one of the key aspect --Performance is one of the key aspects of non-functional qualities, where performance bugs can cause significant performance degradation and lead to poor user experience. ***の役割のため [#i3861dc3] -Due to their key role in --Due to their key role in the allocation and prioritization of effort in testing and maintenance, the software engineering community has shown enduring interest in building and evaluating fault prediction models. *この研究について [#d114c1b5] **良さ [#a1d88369] ***今までにない [#re61d706] -no study thus far has focused --To the best of our knowledge, no study thus far has focused on numerical bugs, or has considered inspecting numerical libraries, despite the reputation of being particularly subtle and error prone. -our work is the first --To the best of our knowledge, our work is the first systematic study of versioning principles in a large collection of Java libraries. However, several case studies on backward compatible and incompatible changes in public interfaces as appearing in these libraries have been performed [2], [7], [9]. -is the first to --To the best of our knowledge, our work is the first to examine the effect of size in continuous fault prediction models. ***貢献 [#v4f1fd53] -Our observations provide --Our observations provide empirical evidence of the bias introduced by build inflation and provide insights on how to deal with this inflation. -form --The results of our study form the basis of future qualitative and quantitative studies on builds and CI. ***目的 [#s9f2b605] -goal --The goal of this paper is to study the causes, symptoms, and fixes of numerical bugs in numerical libraries, and provide a high-level categorization that can serve as a guide for researchers to develop tools for finding and fixing numerical bugs. --The goal of this work is to revisit the effect of size on the association between OO metrics and the number of faults in a class using robust statistical methods. **問題 [#b9aab568] ***チャレンジ [#mb638c82] -face --We faced a number of challenges while conducting this study. ***問題点 [#g8f633b2] -there is a gap --However, there is a gap of knowledge in understanding the characteristics of numerical bugs in real-world numerical software. What are the most common numerical bugs? How prevalent are these bugs? Are existing tools capable of detecting them? How are such bugs fixed? -lack basic knowledge --we lack basic knowledge on the breadth and depth of the adoption of CI by open-source projects. ***着目する [#g7930564] -focus --The focus of this work is on continuous fault prediction models; that is, models that predict the number of faults in a class or a file. ***既存研究と比べ [#v279204c] -In contrast to --In contrast to prior studies on fault-proneness, the mediation effect is not evident across all systems examined. Alternatively, we found that 2) there is more evidence that size has a significant moderation effect, especially for CBO and Fan-out metrics, as it impacts the strength/magnitude of the relationship between OO metrics and faults. -complements --Our study complements previous studies in that it is the first to address the issue of the effect of size in continuous fault prediction models. *その他 [#d11dc4d0] **リサーチクエスチョン [#g9d1901f] -need answers to questions --We need answers to questions such as: does CI advantages surpass its disadvantages? Do developers use CI? **本研究では〜する [#ia58fb71] -provide study --This, we provide the larger quantitative observational study to date on build failures and build inflation. **最初の段階として [#t64422ef] -As a first step towards --As a first step towards promoting release engineering research, this paper makes three major contributions: -takes a first step --This paper takes a first step towards answering these questions by conducting the first comprehensive study of real-world numerical bug characteristics. **論文の構成 [#xdd68ec1] -The remainder of this paper is organized as follows. - This paper is structured as follows. ***モチベーション (関連研究[前半パターン]) [#lca8c165] -We start out, in Section II, by sketching related work in the area of version analysis. -Section II further explains the motivation for this research initiative. -Section II provides background information about patch uplift. -we first describe the nature of the imbalanced learning problem in Section 2, which provides the foundation for our review of imbalanced learning solutions. -First, we provide background about the Linux kernel integration process (Section II) -Section 2 discusses the related work. ***アプローチ [#d011ea30] - In Section III, we formulate the research questions we seek to answer. -Section IV gives an overview of our approach to the mapping exercise. -In Section 3, we provide a critical review of the innovative research developments targeting the imbalanced learning problem, including sampling methods, cost-sensitive learn- ing methods, kernel-based learning methods, and active learning methods. -Section II describes the context and the approach used to collect data for the study. -followed by an explanation of our case study methodology (Section III). - Section 3 describes the design of our case study ***実験 [#rb831638] -Section III describes the design of our case study. -Then, in Section IV, we describe our approach to answer these questions, and methods of measurement. In Section V we provide descriptive statistics of the Maven dataset. -Assessment metrics for imbalanced learning are reviewed in Section 4, which provides various suggested methods that are used to compare and evaluate the performance of different imbalanced learning algorithms. ***結果 [#l6b480e6] -Section IV presents the results of the case study, and -In Sections VI–IX we present our analysis in full detail. -Section III presents the results of the study -Section 5 presents practical suggestions that are informed by our study results. -Section IV presents the results of our case study, -Section 4 presents the results. ***考察 [#yec41ae8] - Section VI discusses threats to the validity of this study. -Section V elaborates on the implications of these results. -We discuss the wider implications and the threats to the validity of our findings in Sections X and XI. -Considering how learning from imbalanced data is a relatively new topic in the research community, in Section 5, we present a detailed discussion on the opportu- nities and challenges for research development in this field. -Section IV discusses the implications of the findings. -followed by a discussion of threats to validity (Section V). -Section 6 discloses the threats to the validity of our study. ***関連研究 [#t21bbd43] -Section VII summarizes related works -We finish the paper with related work (Section VI) ***結論 [#gefbea83] - Section VIII concludes the paper. - We end with some conclusions, as well as a summary of recommendations for those engaged in similar activities, in Section VI. -We conclude the paper in Section XII. -Finally, a conclusion is provided in Section 6. -Finally, Section V presents some concluding remarks and observations on organizational factors. -We finish the conclusion (Section VII). -Finally, Section 7 draws conclusions.
