![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
#author("2018-12-05T10:44:03+09:00","","") #author("2019-01-21T19:14:40+09:00","","") [[論文英語単語帳/表現集]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *動詞 [#nfcbace8] ***述べる [#ke827b6c] -describe -mention --We will also mention the most common tools of each phase, but for a more complete listing of tools at the time of writing, we refer elsewhere [91]. ***与える [#i0543daf] -provide --Based on our experience, this section provides concrete advice about how release engineering can impact software engineering researchers who need to mine software repositories. -present --We present this advice in the form of a checklist, setting the stage with a fictional conversation between a naive professor and clever student, then discussing what is the recommended course of action in order to preserve the integrity of the research findings. ***調査する [#b8068db9] -study --In this paper, we study the challenges that configurability creates for handling performance bugs. -inspect --we manually inspect 193 performance bugs from three popular and highly-configurable open source applications. -examine --We examine the prevalence of configuration issues that have led to performance bugs. --We recommend that researchers consider the potential mediation and moderation effect of class size when building their prediction models, but this should be examined independently for each system. -determine --To determine the consistency with which a build fails across all OSes, we build OS build vector. ***分類する [#r07f0627] -classify --We classify configurations into three types. ***示す [#q76e4348] -show --Figure 8 shows two ARUSs of a method. Rectangle nodes are action nodes, -represent --the nodes represent method invocations and data objects -depict --Table 2 depicts an overview of the 20 approaches investigated. -present --We now present our results for each of the four research questions. -inform --Despite being a fairly expected phenomenon, it informs us that software obfuscation at this point is still not a general interest to mobile development. ***見る， [#o8c86118] -turn to（の方をみる） --To answer RQ1, we turn to Figure 7. ***みなす [#j1e8b843] -see -- We see this study as a way to share with researchers and practitioners the performance issues. ***（暗に，それとなく）言及する [#q2a01e5d] -allude --However, note that the symptom does not allude to any possible cause of the defect and only identifies its effects. ***狙う [#v96beaa9] -aim --The first set of experiments aims to study the run-time performance of SALAD in extracting method sequences from bytecode and in training its API usage models. ***提案する [#p166b2ca] -propose --we propose a novel approach to learn API usages from byte code of Android mobile apps. ***考案する [#na1aab78] -devise --So instead one must choose a set of discrete categories and devise mapping rules to convert the data consistently and coherently into the new categories. ***取り組む [#f0cc1c9d] -address --To address this requirement, -embark <on, upon>(新しいことに) --we can embark on looking at what data is available for such a study. ***持つ，含む [#p08fc4f7] -contain --the Javadoc of a class often contains only descriptions of its methods and rarely has code examples on the usage of its objects and methods. ***成り立つ [#u3e2c03b] -consist --It can learn complex API usages consisting large numbers of objects and methods. ***頼る [#o13d1ddd] -rely on -- programmers rely heavily on standard API frameworks and libraries. -resort to（好ましくない手段に） -- Unfortunately, conducting such studies is very expensive and researchers often resort to studying artifacts after the fact. ***役割を担う [#k8a5c572] -play -- software library plays an important role in modern software development ***争う [#z5e0a3ff] -compete --Improving quality assurance effort in software projects is an important task to keep the existing customers satisfied and to compete in a competitive market. ***道を作る，舗装する [#r0a17743] -pave --To pave the road for future empirical studies on developer activities, ***集める [#c8aa0b2b] -aggregate --An example situation in which such a mapping is necessary is when defect data from a variety of projects is aggregated to build a quality model that relates some characteristics of software development to resulting quality in terms of defects. --We then aggregate this data per period of six months to obtain the evolution of build failure ratio across time. ***維持する，保持する，保存する [#w10b2bd0] -preserve --Thus, some sort of mapping must be done to convert the data into a common format that still preserves as much of the meaning of the original data as possible. -sustain -- To sustain such pursuit and provide a focus for the activity a process description has been found useful. -go --A natural question to ask is to what extent do performance bugs have the potential to go undetected if tested under default environments. ***悩ませる [#eaa7cfd9] -beset --However, the area of software quality measurements and quantification is beset with undue complexity and has, in some ways, advanced away from the developer. ***制限する [#ee81439f] -confine --With the result academic pursuits that can’t be confined to the limitations of practice evolved and became distanced from the developer. -limit -- The analysis is qualitative and only limited by the range of human investigative capabilities. ***得る [#yc1f5703] -derive(引き出す) --In this area, the need to derive tractable measurements that are reasonable to undertake and intuitively plausible cannot be understated. ***着手する [#ic808348] -undertake --In this area, the need to derive tractable measurements that are reasonable to undertake and intuitively plausible cannot be understated. ***始める [#cd362d8d] -kick off --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]. ***除く [#ld80c12e] -eliminate --The goal of causal analysis is to identify the root cause of defects and initiate actions so that the source of defects is eliminated. --To reduce the burden of branches, merges and conflicts, companies have recently adopted "trunk-based development", which eliminates most branches below the master branch. -- Defects4J contains various types of defects from open source projects to eliminate the bias of the dataset [39] in terms of the defects types and the abundance of these defect classes [34, 39]. ***努力する [#s2c24cec] -strive --Indeed, we strive to keep the analysis simple without straying far from the physical interpretation of data. ***再現する [#y03009af] -reproduce --Their model can reproduce different aspects of software evolution. ***必要とする [#w065b19d] -require --our simulation model requires only parameters for effort and size. --Given a suitable branching structure, practitioners also re- quire approaches and tools to predict the presence of integration conflicts [18, 32, 67, 90] and amount of effort required to resolve them. ***反映する [#d62e8351] -reflect --Our simulation also reflects relations between software entities and between developers. ***複雑にする [#x4eb927e] -complicate --Modern computer systems are highly-configurable, complicating the testing and debugging process. ***推測する [#rf5373a9] -conjecture --we conjecture that many of these techniques may not be effective in highly-configurable systems. ***相互に作用する [#l46e6f59] -interact --The application can frequently interact with other system components such as shared libraries, environment variables. ***前提とする [#r9ad6480] -assume --most existing work assumes default configurations while ignoring the influence of various configurations. --Despite the advantages of JIT defect prediction, like all prediction models, they assume that the properties of past events (i.e., fix-inducing changes) are similar to the properties of future ones. --This work aims to estimate both mediation and moderation effects of size, assuming that size might have both effects on the relationship between OO metrics and the number of faults in a class. ***容易にする [#s1320eba] -facilitate --In addition, understanding configurations can facilitate performance optimization. ***現れる [#fd97a0f1] -manifest --We consider both performance bugs caused by misconfigurations and those that can manifest under specific configurations. ***操作する [#k1838040] -manipulate --we also utilized the APIs that have been provided to programmatically manipulate internal data structures. ***定める [#rae28da4] -hinge [on, upon]（条件次第で） --Maintaining a productive and collaborative team of developers is essential to Open Source Software (OSS) success, and hinges upon the trust inherent among the team. ***確かめる [#j3d47f52] -ascertain --One's online social footprint is arguably easier to ascertain and gather than one's technical contributions. ***遵守する [#ua80db75] -adhere --Apache projects, as well as many other OSS projects, adhere to the meritocratic governance model. ***慣れる [#ufd7c019] -familiarize --Contributors usually take some time to familiarize themselves with the code before submitting patch fixes. ***異なる [#e834d0c5] - vary by --While the labels vary by project, they typically amount to some variant of Severe, Normal, and Minor. ***合計〜になる [#g4fef114] -amount --While the labels vary by project, they typically amount to some variant of Severe, Normal, and Minor. ***評価する [#h2fa88b5] -assess --Such a person may find it difficult to accurately assess the severity of a bug. --To use robust statistical methods to assess whether there is evidence of any true effect of class size on fault prediction models. ***変形させる [#f836802f] -distort --Excluding them from any automatic software engineering techniques could substantially distort the results. ***否定する [#idd3e4fc] -contradict --Contradicting Hypothesis 2, ***深める [#g0e3e1ed] -deepen --Showing a representative example in each severity level to deepen their understanding about bug severity, ***含む [#hd8f6ea8] -comprise --We got 1000 responses from the students, comprising two responses for each bug report. ***輪郭を書く [#u30a49b5] -delineate --To delineate the common reasons for misclassification, we also manually analyzed bug reports and students’ responses. ***与える [#e45809c8] -be fed to --These features are then fed to the classification module. -take as input --In the training phase, our framework takes as input a set of bug reports with known priority labels. ***変える [#f64cd6ba] -vary --We vary the values of x and y to get a number of features. ***称す [#r434da2a] -referred --A textual document contains many words. Each of such words is referred to as a token. ***助ける [#x8bcbb12] -aid --To aid bug triagers in assigning priority, we propose a new automated approach to recommend priority levels of bug reports. ***測定する [#t0136b47] -calibrate --we employ a thresholding approach to calibrate a set of thresholds to decide the class labels (i.e., priority levels) *** 満たす [#k77c60c1] -meet --In most instances, the specific configuration of the information captured about an issue was tailored by the IV&V project to meet its needs. ***仮定する [#g77ae541] -suppose --Suppose a data set has 80% severity=5 issues and 20% severity=1 issues. ***差し込む [#p833ad29] -plug into --Feature values are plugged into the equation to find its class label ***隠れる [#c1b68644] -lurk in --The research shows that bugs usually lurk in specific spots with bugs reoccuring in buggy parts of a software systen ***入れる [#u983b523] -land in --The patches of developers need to be reviewed and integrated from developer branches and tested by the Continuous Integration system, until they land in the master branch. ***一員になる [#s175b1fc] -enter --When an upcoming release enters the feature-complete stage, release stabilization begins, where major bugs in the functionality of the release are addressed. ***変動する [#r85c05c3] -fluctuate --Unfortunately, the load of the CI system fluctuates across time, for example depending on the kind of features being developed or the progress of the current development sprint. ***計算する [#geb10300] -calcurate --we calculate agreement across the union of ratings of (round 1, group A) and (round 2, group B), and the union of (round 1, group B) and (round 2, group A), as these pairs of ratings consider the same comments. ***得る [#f616d5ae] -obtain --Love clearly obtains the highest κ agreement, corresponding to a moderate value. ***カバーする [#te901f1c] -cover --These cover more than 12,000 CPAN packages (“distributions”), 27 OSes and 103 environments to answer the following four questions: ***変化する [#x99fb8f7] -evolve --How do build failures evolve across time? -fluctuate --This initial research question aims at under- standing how often builds fail and whether the ratio of failing builds is a constant value or fluctuates across time. ***一致する [#q461f42c] -correspond --Build inflation seems to correspond to differences/similarities in OSes/environments, which can identify clusters of Perl versions/OSes with different failure ratio and value. ***と認める [#qd19903c] -identify with --Build inflation seems to correspond to differences/similarities in OSes/environments, which can identify clusters of Perl versions/OSes with different failure ratio and value. ***で発生している [#sfd8a0f1] ***で発生する [#sfd8a0f1] -take place on --The analyzed CPAN distversions have a me- dian of 179 builds, which take place on a median of 22 environments and 7 OSes. -raise --This approach has become the expected convention - in submitting our research previously, the need to consider the indirect (confounding) effect of size on the relationship between software characteristics and faults was raised frequently in reviews. ***に終わる [#x9a8e388] -end up with --On the other hand, 11% of the environment build vectors ended up failing in the most recent Perl versions and were unable to recover, or never succeeded at all (0-0 and 1-0 patterns). ***移植する [#k7db39ef] -port over --Especially if one OS is less popular than others, it might have seen less testing or some features might not have been ported over, causing test scripts to fail. Such failures would receive less weight in the build results than builds failing consistently across all OSes. ***超す [#v12058fb] -surpass --Linux causes more inconsistencies when being built with a small number of other OSes (small N ), but is surpassed by Windows (and Cygwin) in larger sets of OSes (large N). ***属する [#l94f2925] -belong --they no longer belong to a minority but make up the majority of OSes. ***反映する [#vb1a9d06] -flourish --The main take-home message is that, while release engineering technology has flourished tremendously due to industry, empirical validation of best practices and the impact of the release engineering process on (amongst others) software quality is largely missing and provides major research opportunities. ***到達する [#saf2aab9] -make it to --Other branches might see much higher percentages of code changes that never make it to the master branch, because they fail integration tests or reviews somewhere along the branch structure. -achive --To achieve this goal, Firefox changed its development pro- cess. First, versions are no longer supported in parallel, i.e., a new version supersedes the previous ones. ***（病気などを）移す [#v03f7781] -infect --Lately, security of the release engineering pipeline in general, and the CI server in particular, also has become a major concern [9], since any malicious script capable of injecting a payload in the CI’s build output could infect the rest of the release engineering pipeline. ***影響がある [#xb6cbd2a] -impact --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. -affect --To understand whether and how transitioning to a rapid release model can affect the quality of a software system as observed by users, we empirically study the historical field testing data of Mozilla Firefox. -transmit --Given an independent variable X and a dependent variable Y , the effect of X on Y may be transmitted through a third intervening (mediating) variable M. ***拾う [#c837f38c] -glean --For example, researchers can provide value by analyzing release engineering data stored in industrial version control systems, bug/review repositories, CI servers and deployment logs, with the aim of gleaning actionable insights for release engineers. ***間に差し込む [#a1775170] -interleave --Other factors that can impact the findings of an empirical study are the differences in scope between major, minor and patch releases, as well as the interleaving of releases. ***置く [#w13958b5] -situate --The latter refers to how releases with successive major version numbers are situated relative to each other. ***普及する [#b87e8eee] -use --Floating point is a widely used representation that approximates real numbers. ***導く [#za6bdccb] -lead --This has led, in part, to numerical bugs that have caused catastrophic failures --These known issues with both techniques (i.e., the casual-steps and Sobel tests), combined with a level of conclusion instability across different studies, led us to seek alternative approaches to investigate the true indirect effect of size. ***関係する [#f4de064d] -relate --Numerical bugs are those related to either the finite approximate representation of real numbers, or to mathematical aspects of the computation. ***克服する [#a6e5e672] -overcome --We overcome these three challenges by leveraging Coq’s newly-added toolchain for asynchronous proof processing [7]. ***軽減する [#m89c4703] -mitigate -alleviate --In crowdsourced software testing, inspecting the large number of test reports is an overwhelming but inevitable soft- ware maintenance task. In recent years, to alleviate this task, many text-based test-report classification and prioritization techniques have been proposed. ***知られている [#n25d4370] -be acknowledged as --In object oriented (OO) software systems, class size has been acknowledged as having an indirect effect on the relationship between certain artifact characteristics, captured via metrics, and fault-proneness, and therefore it is recommended to control for size when designing fault prediction models. ***するように見える（思われる） [#w6eec0a1] -appear --On the other hand, size does appear to have a significant moderation effect on WMC and CBO in most of the systems examined. ***補完する [#zf671d95] -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. ***受け取る [#jb4b646b] -receive --Bootstrapping-based methods for estimating indirect effect have been discussed in the literature for some time (e.g., [4]), but the methods have received more attention in recent years [12, 19, 20]. ***描写する [#i3daf920] -portray --Simple slope analysis can visually portray how another variable moderates the association between the independent and dependent variable. ***穏やかにする [#y42d4863] -moderate --Simple slope analysis can visually portray how another variable moderates the association between the independent and dependent variable. ***引き出す [#dbee0a3a] -derive --To derive a 95% confidence interval, the elements of the vector of 1000 estimates of XY are sorted into ascending order. ***提供する [#w52d947b] -offer --The study of Zhou et al. [25] used the same dataset, which offers us an opportunity to com- pare our results. ***除外する [#p78e230e] -exclude --Finally we also excluded systems comprising small numbers of classes (fewer than 60) as we consider them too small for our analysis. ***論争する [#p91fe25c] -contend --Therefore, we contend that the evidence provided regarding the moderation eect of size is not conclusive in regard to these two datasets.
