論文英語単語帳
リンク†
調査する†
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. 分類する†
classify
We classify configurations into three types. 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. 見る，†
turn to（の方をみる）
To answer RQ1, we turn to Figure 7. みなす†
see
We see this study as a way to share with researchers and practitioners the performance issues. （暗に，それとなく）言及する†
allude
However, note that the symptom does not allude to any possible cause of the defect and only identifies its effects. 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. 提案する†
propose
we propose a novel approach to learn API usages from byte code
of Android mobile apps. 考案する†
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. 取り組む†
address
To address this requirement,
embark <on, upon>(新しいことに)
we can embark on looking at what data is available for such a study. 持つ，含む†
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. 成り立つ†
consist
It can learn complex API
usages consisting large numbers of objects and methods. 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. 役割を担う†
play
software library plays an important role in modern software development 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. 道を作る，舗装する†
pave
To pave the road for future empirical studies on developer activities, 集める†
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. 維持する，保持する，保存する†
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. 悩ませる†
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. 制限する†
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. derive(引き出す)
In this area, the need to derive tractable measurements that are reasonable to undertake and intuitively plausible cannot be understated. 着手する†
undertake
In this area, the need to derive tractable measurements that are reasonable to undertake and intuitively plausible cannot be understated. 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. 努力する†
strive
Indeed, we strive to keep the analysis simple without straying far from the physical interpretation of data. 再現する†
reproduce
Their model can reproduce different aspects of software evolution. 必要とする†
require
our simulation model requires only parameters for effort and size. 反映する†
reflect
Our simulation also reflects relations between software entities and between developers. 複雑にする†
complicate
Modern computer systems are highly-configurable, complicating the testing and debugging process. 推測する†
conjecture
we conjecture that many of these techniques may not be effective in highly-configurable systems. 相互に作用する†
interact
The application can frequently interact with other system components such as shared libraries, environment variables. 前提とする†
assume
most existing work assumes default configurations while ignoring the influence of various configurations. 容易にする†
facilitate
In addition, understanding configurations can facilitate performance optimization. 現れる†
manifest
We consider both performance bugs caused by misconfigurations and those that can manifest under specific configurations. 操作する†
manipulate
we also utilized the APIs that have been provided to programmatically manipulate internal data structures. 定める†
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. 確かめる†
ascertain
One's online social footprint is arguably easier to ascertain and gather than one's technical contributions. 遵守する†
adhere
Apache projects, as well as many other OSS projects, adhere to the meritocratic governance model. 慣れる†
familiarize
Contributors usually take some time to familiarize themselves with the code before submitting patch fixes. 異なる†
vary by
While the labels vary by project, they typically amount to some variant of Severe, Normal, and Minor. 合計〜になる†
amount
While the labels vary by project, they typically amount to some variant of Severe, Normal, and Minor. 評価する†
assess
Such a person may find it difficult to accurately assess the severity of a bug. 変形させる†
distort
Excluding them from any automatic software engineering techniques could substantially distort the results. 否定する†
contradict
Contradicting Hypothesis 2, 深める†
deepen
Showing a representative example in each severity level to deepen their understanding about bug severity, comprise
We got 1000 responses from the students, comprising two responses for each bug report. 輪郭を書く†
delineate
To delineate the common reasons for misclassification, we also manually analyzed bug reports and students’ responses. 与える†
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. 変える†
vary
We vary the values of x and y to get a number of features. referred
A textual document contains many words. Each of such words is referred to as a token. 助ける†
aid
To aid bug triagers in assigning priority, we propose a new automated approach to recommend priority levels of bug reports. 測定する†
calibrate
we employ a thresholding approach to calibrate a set of thresholds to decide the class labels (i.e., priority levels) 満たす†
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. 仮定する†
suppose
Suppose a data set has 80% severity=5 issues and 20% severity=1 issues. 差し込む†
plug into
Feature values are plugged into the equation to find its class label 隠れる†
lurk in
The research shows that bugs usually lurk in specific spots with bugs reoccuring in buggy parts of a software systen
![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
