![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
#author("2018-11-02T18:51:53+09:00","","") #author("2019-01-21T19:14:56+09:00","","") [[論文英語単語帳]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *イディオム [#daee2403] **が原因で [#k5dd8eaa] -due to --learning and using those APIs is often challenging due to the fast-changing nature of API frameworks for mobile systems **合計で [#kaa86872] -in total --In total, SALAD downloaded and analyzed 22,330 apps belonging to 26 categories from Google Play Store. **数十年， [#kac13312] -the last xxx decades, --Over the last couple of decades, --for the last several decades **どの程度まで〜か [#l3be9ad6] -to what extent --A natural question to ask is to what extent do performance bugs have the potential to go undetected if tested under default environments. **ある意味， [#q9c5d1be] - in a sense --In a sense, a newcomer is as integral to the project as their contributions, be they communications or bug fixes. **ある程度時間がかかる [#yb77d09e] - take some time --Contributors usually take some time to familiarize themselves with the code before submitting patch fixes. **繰り返しになりますが， [#ca42ac31] -Once again, --Once again, the assumption was that the most informative terms are enough to fully describe their corresponding documents from our application point of view. **〜の形で [#b56a167f] -in the form of --Release engineering is the process responsible for taking the individual code contributions of developers and bringing those to the end user in the form of a high quality software release. **最初から最後まで [#x9085ba2] -From start to finish, --From start to finish, a myriad of tasks need to be performed by an organization's release engineers. **今でも [#o0574601] -even today, --Even today, software organizations who are not at the forefront of the release engineering revolution need to consider what release practices should be adopted. **かかわらず [#xd39ee4b] -regardless of --Researchers should consider this checklist to avoid wrong conclusions, regardless of whether their study targets the release engineering process. **合計で [#ad5053bc] -In total, --In total, we captured 35 third-party libraries. The major functionality of each library, inferred by analyzing their code and retrieving publicly available information on the Web, is presented in Table 1. -From this total -- From this total, 646 merge scenarios have an errored build status. **詳細には [#hc4fb570] -in detail --In detail, we refer to Android-18 API documentation [26] and use the rules below (adopted by prior work [18]) to categorize exceptions: (1) Application Exception: the signaler is from the app itself (identified by the app’s package name). **を目的として [#t4e80545] -with the aim of --A CI environment such as Jenkins kicks off a build multiple times a day, either for each patch currently under review, each new commit entering the version control system or at set times during the day (e.g., nightly build), with the aim of notifying developers as soon as possible of breakage [1], [2]. **の点から [#z810eaae] -in terms of --Our findings can help researchers as this inflation could be responsible for bias in build results. The results can also help practitioners to prioritize the best OS/perl version to test on, in terms of expected value. --Numerical software relies heavily on floating point arithmetic, which brings additional challenges in terms of software reliability and performance. **のために [#oc933927] -for the sake of --. For the sake of locality, we present the research questions, their motivations, and their results in the next section. **どのていど〜か [#ifa15b53] -to what extent --To what extent do OSes impact build failures? **とは逆に [#r83b0e04] -In contrast to --In contrast to RQ3, RQ4 does not study chronological differences in build results, but rather how consistent builds fail across OSes. **と同様に [#z110d90a] -as well as --Table III shows the percentage of vectors with inconsistent builds, as well as how often those are caused by a minority of failing builds. **大まかに言えば [#g4012dbb] -broadly speaking --Broadly speaking, the patches of developers need to be re- viewed and integrated (merged) [13] from developer branches into team and product branches, where they are compiled [48] and tested [89] by the Continuous Integration (CI) system, until they land in the master branch. **終始一貫 [#iec399ac] -From start to finish --From start to finish, a myriad of tasks need to be performed by an organization’s release engineers, i.e., the personnel whose main duties are the development, maintenance, and operation of an organization’s release infrastructure. **の他には [#a73e3b33] -apart from --Apart from slow CI tests, another major reason for slow CI builds in organizations with large development teams, is the simultaneous submission of multiple commits, yielding a large number of new commits and merges in a short timespan. **下記参照 [#kad9afba] -see below --The deployment phase is typically followed relatively quickly by the release phase (see below), since in between deployment and release, the deployed files basically are inactive (and invisible to users). **を考えると [#sf42da61] -given that --Finally, given that the goal of the integration process (see Section II-A) is to bring high quality code changes as fast as possible to the master branch (and hence to the user), being able to profile the integration process for integration bottle- necks would be a major asset for companies. **仮に〜だとしても [#j63f2ab2] -granted that --Granted, not all of these challenges are release engineering-specific, but these activities would definitely reduce the risk of a bad mobile release for developers. **一般に [#bce34544] -in general --In general, the correctness of a build system is impacted by the way in which build specifications co-evolve with the source code, for example to include new source code files in the build. **突然 [#z155aee6] -all at once --Even the final release might not be released all at once, but might be revealed (released) to one user group at a time (see canary deployment in Section II-E). ***偶然 [#q3ff2ce6] -by accedent --If a study by accident would be measuring the bugs reported during feature freeze or the code changes reviewed in that period, a much larger proportion of bug fixes would be visible than usual, with hardly any new feature development [27]. ***本来 [#k1ca97f1] -by nature --By nature, floating point introduces imprecision in numerical calculations. ***ある程度 [#yf3bd15d] -in part --This has led, in part, to numerical bugs that have caused catastrophic failures ***関する [#fd5bb475] -with regard to --These previous works investigated the effect of size with regards to fault-proneness (i.e., a class is either faulty or it is not). ***AでなくBである [#c85b8d52] -not A but rather B --a moderation variable does not necessarily explain the relationship between variables but rather it explains the strength of this rela- tionship [1]. A moderator eect is indicated by the interaction of X and M in explaining Y . ***すでに述べたように [#n013d47e] -As noted above, --As noted above, in this study mediation analysis is conducted using a bootstrapping-based procedure [12, 14]. ***に対する返答 [#fa65e101] -in returning to --In returning to our research hypotheses (H0), based on the evidence resulting from our analysis of the systems in the two datasets individually, we cannot reject the null hypothesis that class size has no mediation effect on the relationship between the number of faults and the following OO metrics: RFC, WMC, LCOM and Fan-in. For CBO and Fan-out, while the mediation effect appears in the majority of systems, the evidence of this effect is not consistent across both datasets.
