論文英語単語帳/名詞
の編集
https://floss-lab.org/pukiwiki/?%E8%AB%96%E6%96%87%E8%8B%B1%E8%AA%9E%E5%8D%98%E8%AA%9E%E5%B8%B3/%E5%90%8D%E8%A9%9E
[
トップ
] [
編集
|
差分
|
履歴
|
添付
|
リロード
] [
新規
|
一覧
|
検索
|
最終更新
|
ヘルプ
]
-- 雛形とするページ --
(no template pages)
[[論文英語単語帳]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *名詞 [#mc285cf7] ***不十分，不足 [#zcd3c2c3] -insufficiency --Due to the insufficiency of documentation, ***利用できないこと、役に立たないこと、使い勝手の悪さ [#o54ce4a6] -unavailability --Due to the insufficiency of documentation, ***新しい種類の、新手の [#q34d2d5d] -novel -- a novel approach to learn API usages ***特徴 [#p7d9d89b] -characteristic --our approach has three distinctive characteristics. ***関数の呼び出し順序 [#e3059d1c] -method call sequence -- a given collection of method call sequences involving the API objects it models. ***観察 [#w8b5d985] -observation --The observations are stored in enriched event streams that encode a holistic picture of the in-IDE development process. ***現象・事象 [#j69c6f5e] -phenomenon(複数形：phenomena) --we describe our approach of understanding, simulating and assessing software evolution and its phenomena. -symptom（兆候） --We find that performance bugs can be detected by observing internal symptoms. ***事後検証 [#w7c9b647] -post-mortem --Post-mortem analysis of bugs for understanding various characteristics of various bugs can have many benefits. ***専門用語 [#o86ba3e1] -terminology --Aggregating heterogenous data from different sources is always difficult, especially when the data definitions use different terminology or formats. --Our solution to the terminology problem was to rely on defect categorization definitions and actual defect descriptions. ***潜在能力 [#b13c19a6] -potential --An aggregation has the potential to be very useful in building descriptive or prescriptive models based on historical data. ***状況 [#pbc2ab5f] -situation --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. ***後方互換性 [#md187270] -backward compatibility --Our goal was to develop a unified defect categorization scheme that is completely “backward compatible” with existing data, that captures domain-specific elements of interest to NASA, and that has other desirable attributes of good defect taxonomies ***研究構想 [#t9dfafa0] -research initiative --Section II further explains the motivation for this research initiative. ***有形資産 [#e5ea620f] -tangibles --In an area where the processes are so amorphous, the tangibles required for measurement and modeling are few. ***追求 [#xee188c5] -pursuit -- With the result academic pursuits that can’t be confined to the limitations of practice evolved and became distanced from the developer. -- To sustain such pursuit and provide a focus for the activity a process description has been found useful. ***ユーザエクスペリエンス [#b8dd8045] -user experience --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. ***範囲 [#v79ada7c] -extent --A natural question to ask is to what extent do performance bugs have the potential to go undetected if tested under default environments. --We aim to uncover and quantify the extent to which the performance problem exists on real-world highly-configurable software systems. --Un- like mediation, which affects to the extent that it accounts for the relationship between the independent and dependent variables, a moderation variable does not necessarily explain the relationship between variables but rather it explains the strength of this relationship [1]. ***（人生の）軌跡 [#h88b0374] -trajectory --A typical trajectory to becoming a core developer is to start communicating with other project contributors and then gradually get more involved, by earning a more central position in the project's social network. ***適合 [#id3686d6] -congruence --The congruence of a newcomer's social and technical activities is crucial for successful participation in an open source project. ***僅かにことなるもの [#n1f2b8b1] -variant --While the labels vary by project, they typically amount to some variant of Severe, Normal, and Minor. ***観念 [#l32a03a8] -notion --We first briefly present the notion of a bug tracking system, and the levels of severity that such systems commonly use. ***一貫性 [#h8d6e848] -consistency --This has created consistency problems when metrics data is pulled across projects. ***仮定 [#k07700db] -assumption --Once again, the assumption was that the most informative terms are enough to fully describe their corresponding documents from our application point of view. ***熟考 [#bdcd3a78] -deliberation --experts can help in design deliberations of complex problem and users can be made aware of the status of a bug ***最先端 [#rb17dffd] -forefront --Even today, software organizations who are not at the forefront of the release engineering revolution need to consider what release practices should be adopted. ***膨張 [#tb60a243] -inflation --To perform our analysis of build inflation and its resulting bias, we empirically study 30 million builds of the Perl Comprehensive Perl Archive Network (CPAN)’s [5] CI environment, made between 2011 and 2016. ***経験則 [#q7e29094] -rules of thumb --There are rules of thumb that mitigate the risk of introducing merge conflicts. ***負荷 [#pe82ab54] -burden --To reduce the burden of branches, merges and conflicts, companies have recently adopted “trunk-based development,” which eliminates most (if not all) branches below the master branch. Instead, teams directly commit to the master branch (after review). ***基準 [#pecd9c95] -criteria --Other identification criteria should be considered, as well as how to determine and physically refactor an existing branching structure. ***原因 [#h972f5b2] -culprit --However, if the chunk-level build fails, it is not clear which of the commits in the chunk is responsible for the breakage, and one would need to rebuild each commit in the chunk individually to identify the culprit(s). -source --Sources of numerical errors include extreme sensitivity to roundoff, floating-point exceptions such as overflow/underflow, and nonreproducibility across machines or even across runs on the same machine. ***必要条件 [#c0496018] -prerequisite --Reproducible builds are a prerequisite to reliably identify security breaches or platform-specific problems on a build machine. ***知見 [#vf856347] -insight --Such insights could help them decide what best practices to adopt, understand why (and when) continuous delivery is feasible, and what compromises are necessary in terms of software quality and technical debt. ***完全性 [#z63e3c6c] -integrity --discussing what is the recommended course of action in order to preserve the integrity of the research findings. ***出現 [#k94d5b73] -advent --With the advent of shorter release cycles in March 2011, new features need to be tested and delivered to users faster. ***調停 [#gda3b5c2] -mediation --We examine the potential mediation and moderation effects of class size on the relationships between OO metrics and number of faults. ***適度 [#h2813167] -moderation --We examine the potential mediation and moderation effects of class size on the relationships between OO metrics and number of faults. ***習慣，因習 [#h884127b] -convention --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. ***主張 [#keb9b84a] -assertion --Unlike previous studies in fault-proneness, our results do not support the assertion that the size effect always exists in continuous fault prediction models.
タイムスタンプを変更しない
[[論文英語単語帳]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *名詞 [#mc285cf7] ***不十分，不足 [#zcd3c2c3] -insufficiency --Due to the insufficiency of documentation, ***利用できないこと、役に立たないこと、使い勝手の悪さ [#o54ce4a6] -unavailability --Due to the insufficiency of documentation, ***新しい種類の、新手の [#q34d2d5d] -novel -- a novel approach to learn API usages ***特徴 [#p7d9d89b] -characteristic --our approach has three distinctive characteristics. ***関数の呼び出し順序 [#e3059d1c] -method call sequence -- a given collection of method call sequences involving the API objects it models. ***観察 [#w8b5d985] -observation --The observations are stored in enriched event streams that encode a holistic picture of the in-IDE development process. ***現象・事象 [#j69c6f5e] -phenomenon(複数形：phenomena) --we describe our approach of understanding, simulating and assessing software evolution and its phenomena. -symptom（兆候） --We find that performance bugs can be detected by observing internal symptoms. ***事後検証 [#w7c9b647] -post-mortem --Post-mortem analysis of bugs for understanding various characteristics of various bugs can have many benefits. ***専門用語 [#o86ba3e1] -terminology --Aggregating heterogenous data from different sources is always difficult, especially when the data definitions use different terminology or formats. --Our solution to the terminology problem was to rely on defect categorization definitions and actual defect descriptions. ***潜在能力 [#b13c19a6] -potential --An aggregation has the potential to be very useful in building descriptive or prescriptive models based on historical data. ***状況 [#pbc2ab5f] -situation --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. ***後方互換性 [#md187270] -backward compatibility --Our goal was to develop a unified defect categorization scheme that is completely “backward compatible” with existing data, that captures domain-specific elements of interest to NASA, and that has other desirable attributes of good defect taxonomies ***研究構想 [#t9dfafa0] -research initiative --Section II further explains the motivation for this research initiative. ***有形資産 [#e5ea620f] -tangibles --In an area where the processes are so amorphous, the tangibles required for measurement and modeling are few. ***追求 [#xee188c5] -pursuit -- With the result academic pursuits that can’t be confined to the limitations of practice evolved and became distanced from the developer. -- To sustain such pursuit and provide a focus for the activity a process description has been found useful. ***ユーザエクスペリエンス [#b8dd8045] -user experience --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. ***範囲 [#v79ada7c] -extent --A natural question to ask is to what extent do performance bugs have the potential to go undetected if tested under default environments. --We aim to uncover and quantify the extent to which the performance problem exists on real-world highly-configurable software systems. --Un- like mediation, which affects to the extent that it accounts for the relationship between the independent and dependent variables, a moderation variable does not necessarily explain the relationship between variables but rather it explains the strength of this relationship [1]. ***（人生の）軌跡 [#h88b0374] -trajectory --A typical trajectory to becoming a core developer is to start communicating with other project contributors and then gradually get more involved, by earning a more central position in the project's social network. ***適合 [#id3686d6] -congruence --The congruence of a newcomer's social and technical activities is crucial for successful participation in an open source project. ***僅かにことなるもの [#n1f2b8b1] -variant --While the labels vary by project, they typically amount to some variant of Severe, Normal, and Minor. ***観念 [#l32a03a8] -notion --We first briefly present the notion of a bug tracking system, and the levels of severity that such systems commonly use. ***一貫性 [#h8d6e848] -consistency --This has created consistency problems when metrics data is pulled across projects. ***仮定 [#k07700db] -assumption --Once again, the assumption was that the most informative terms are enough to fully describe their corresponding documents from our application point of view. ***熟考 [#bdcd3a78] -deliberation --experts can help in design deliberations of complex problem and users can be made aware of the status of a bug ***最先端 [#rb17dffd] -forefront --Even today, software organizations who are not at the forefront of the release engineering revolution need to consider what release practices should be adopted. ***膨張 [#tb60a243] -inflation --To perform our analysis of build inflation and its resulting bias, we empirically study 30 million builds of the Perl Comprehensive Perl Archive Network (CPAN)’s [5] CI environment, made between 2011 and 2016. ***経験則 [#q7e29094] -rules of thumb --There are rules of thumb that mitigate the risk of introducing merge conflicts. ***負荷 [#pe82ab54] -burden --To reduce the burden of branches, merges and conflicts, companies have recently adopted “trunk-based development,” which eliminates most (if not all) branches below the master branch. Instead, teams directly commit to the master branch (after review). ***基準 [#pecd9c95] -criteria --Other identification criteria should be considered, as well as how to determine and physically refactor an existing branching structure. ***原因 [#h972f5b2] -culprit --However, if the chunk-level build fails, it is not clear which of the commits in the chunk is responsible for the breakage, and one would need to rebuild each commit in the chunk individually to identify the culprit(s). -source --Sources of numerical errors include extreme sensitivity to roundoff, floating-point exceptions such as overflow/underflow, and nonreproducibility across machines or even across runs on the same machine. ***必要条件 [#c0496018] -prerequisite --Reproducible builds are a prerequisite to reliably identify security breaches or platform-specific problems on a build machine. ***知見 [#vf856347] -insight --Such insights could help them decide what best practices to adopt, understand why (and when) continuous delivery is feasible, and what compromises are necessary in terms of software quality and technical debt. ***完全性 [#z63e3c6c] -integrity --discussing what is the recommended course of action in order to preserve the integrity of the research findings. ***出現 [#k94d5b73] -advent --With the advent of shorter release cycles in March 2011, new features need to be tested and delivered to users faster. ***調停 [#gda3b5c2] -mediation --We examine the potential mediation and moderation effects of class size on the relationships between OO metrics and number of faults. ***適度 [#h2813167] -moderation --We examine the potential mediation and moderation effects of class size on the relationships between OO metrics and number of faults. ***習慣，因習 [#h884127b] -convention --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. ***主張 [#keb9b84a] -assertion --Unlike previous studies in fault-proneness, our results do not support the assertion that the size effect always exists in continuous fault prediction models.
テキスト整形のルールを表示する
![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
