![[PukiWiki]](image/wadanyan.png "[PukiWiki]")
#author("2019-01-21T19:14:44+09:00","","") #author("2019-02-15T21:24:19+09:00","","") [[論文英語単語帳]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *形容詞 [#v3c2fa30] ***猛烈な [#m43e4ce4] -fierce --Due to the fierce competition, ***最新の [#ge5c8beb] -up-to-date -- it is also error-prone because online code examples might not be up-to-date to the latest changes of the mobile API frameworks. -latest --the latest changes of the mobile API frameworks. ***特色のある [#t554c9b0] -distinctive --our approach has three distinctive characteristics. ***まとめられた [#o7695c17] -clustered --Android application framework contains over 3,400 classes and 35,000 methods, clustered in more than 250 packages ***指定の [#q1a65ebb] -specified --it can generate a method call and change to another state with specified probabilities. ***必須の [#n023a52e] -essential --A good understanding of the impact of different types of bugs on various project aspects is essential to improve software quality research and practice. --Such models are essential to properly manage the major software development outcomes (e.g., cost, schedule, quality) and to build up organizational knowledge. ***必要な [#w37ed527] -necessary --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. ***異種の [#xb6ce069] -heterogeneous --Aggregating heterogenous data from different sources is always difficult, especially when the data definitions use different terminology or formats. ***同等の [#u76b8990] -equivalent --The fit with four subpopulations will be better, since it is equivalent to fitting data with more parameters. ***重要な [#w1eb038a] -significant --To be effective, however, the models must be built using a significant base of historical data that describes numerous variations within the domain of the model (e.g., an organizational unit). ***主要な [#xe9fea9e] -staple --To enable swift detection of bugs and other quality issues, continuous integration (CI) has become a main staple in the quality assurance tool box of companies. ***多数の [#g9416db1] -numerous --To be effective, however, the models must be built using a significant base of historical data that describes numerous variations within the domain of the model (e.g., an organizational unit). -slew --Indeed, for every success and breakthrough that has been made, there are a slew of failures. ***無数の [#wf504dd9] -myriad -- indeed there is a myriad of reported research and industry attempts to quantify the parameters of the software development process with “metrics” --From start to finish, a myriad of tasks need to be performed by an organization's release engineers. ***大量の [#b47a2abc] -plenty --As it happens, there is plenty of data but not quite in the form that would allow us to answer the question. ***同一の [#ac68e55a] -identical --Often, such data, collected over a period of time by different people, and in different projects, do not have identical structures. ***直交の<数学> [#j05b94c2] -orthogonal --Some categorizations are orthogonal, i.e., they address different dimensions of interest (e.g., severity vs. technical cause), so combining them results in categories that are not mutually exclusive. ***排他的な [#s6640368] -exclusive --Some categorizations are orthogonal, i.e., they address different dimensions of interest (e.g., severity vs. technical cause), so combining them results in categories that are not mutually exclusive. ***離散の，別々の [#b8bda62e] -discrete --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. ***無定形の [#m3cc4a36] -amorphous --In an area where the processes are so amorphous, the tangibles required for measurement and modeling are few. ***扱いやすい [#t0f259d2] -tractable --In this area, the need to derive tractable measurements that are reasonable to undertake and intuitively plausible cannot be understated. ***もっともらしい [#vba596f2] -plausible --In this area, the need to derive tractable measurements that are reasonable to undertake and intuitively plausible cannot be understated. ***率直な [#pc5ed923] -straightforward --Given the nature of defect data there is no straightforward answer. ***役に立つ [#f8e53cff] -helpful(助けになる) --It can be helpful to have tool support. ***全体の [#q1775f45] -sheer --The sheer size of the configuration space makes the quality of software even harder to achieve. -holistic --This holistic view of a bug report is needed for us to support triagers in assigning priority levels to bug reports. ***高度な [#q37ac43f] -sophisticated --The complexity of the configuration space and the sophisticated constraints among configuration settings could easily cause performance bugs. ***流行している，普及している [#t041cb3d] -prevalent --How prevalent are performance bugs related to configurations? ***実力主義の [#mcfa0b8b] -meritocratic --Apache projects, as well as many other OSS projects, adhere to the meritocratic governance model. ***結合力のある [#if404c55] -cohesive --The communication activities that follow the initiation time would presumably be less cohesive, and more connected to individual preferences and styles of work. ***悲観的な [#d0d15095] -pessimistic --On the other hand, for the worst case, i.e., the most pessimistic view of the state of the software, we take the highest level of severity between the two responses. ***所有の [#rc9f7fdb] -proprietary --Thus, they often allow users to report such defects using bug reporting systems such as Bugzilla, Jira, or other proprietary systems. ***判別可能な [#m26897b4] -discriminative --The classification module would produce a discriminative model that could classify a bug report with an unknown priority level. ***結果として生じる [#p17c8a3e] -resultant --Each of the resultant word tokens corresponds to a feature. ***どちらか [#c32f79f5] -either --Given a new bug report and a bug tracking system, predict the priority label of the new report as either P1, P2, P3, P4, or P5. ***年代順の [#rd697d48] -chronological --We sort the bug reports in chronological order. ***異常の [#rc31ad64] -anomalous --We designed and built a tool named SEVERIS (SEVERity ISsue assessment) to automatically review issue reports and alert when a proposed severity is anomalous. ***形態的 [#l90b82b8] -morphological --The stem need not be identical to the morphological root of the word ***うんざり [#n507e6cd] -tedious --Bug triaging is a time-cosuming and tedious task in software maintenance. ***責任をもつ [#a7d853c9] -responsible --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. ***顕著な [#a658bfb4] -notable --The most notable kind of third-party libraries is for advertising purposes with both metrics being the highest in Table 1. ***あり得る [#l2784950] -likely --The first two points suggest that mobile apps related to health, finance, privacy, and intellectual property safety are more likely to get obfuscated, both actively or passively. --In essence, this reflects an assumption that larger classes are inherently ‘more likely to be faulty’, or ‘more faulty’, than smaller classes. --Intuitively, if there are many bugs reported in the last x days with a higher severity level than BR, BR is likely not assigned a high priority level since there are many higher severity bug reports in the bug tracking system that need to be resolved too. ***そんな [#hfd5b451] -such --Emotion mining from software development artifacts like issue reports, emails or change logs is not trivial, since such artifacts consist of unstructured, natural language text (Bacchelli et al 2010, 2012). ***宣言型の [#v2931f99] -declarative --Some infrastructure programming languages are declarative, while others rely on existing languages like Python or Ruby. ***が可能な [#s6f0ef10] -capable of --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. ***明白な [#u767a3ee] -explicit --Build correctness is challenging to measure or even observe, unless a build fails with explicit error messages. ***異なる [#zc0a4966] -different --Hence, maintenance effort as well as quality measures will likely be different between these languages. ***まっすぐに [#l7414f2d] -straight-forward --former Etsy’s Noah Sussman (“continuous delivery is mainstream”) [77] indicated that for large IT companies, implementing continuous delivery for web apps is straight-forward, given that tools have become widely available or even commodities. ***実態のある [#t1bcb7a3] -substantial --While large companies with substantial resources can afford trial-and-error and even failure (as discussed in the various keynote talks at the RELENG workshop [1]), younger companies with smaller margins for error do not have this luxury and want to adopt the right tools and practices from the start. ***具体的な [#q9c65e81] -concrete --Based on our experience, this section provides concrete advice about how release engineering can impact software engineering researchers who need to mine software repositories. ***類似して [#n081d609] -akin --Such projects use a staged release pipeline (akin to superscalar processor architectures [81]), where release i is in beta, while release i − 1 is in alpha and i − 2 in nightly testing. ***その次に続く [#o23c6dbb] -subsequent --As a result, for one project 4 weeks might be negligible compared to the total cycle time, while for another project this might be the full cycle time between two subsequent releases. ***固有の [#e06bd5fb] -inherent --Indeed, many of the difficulties faced by numerical programmers are inherent in the semantics of floating point. ***矛盾のない，一致した [#afd12951] -consistent --Again, the evidence provided is not consistent across all examined systems. ***矛盾する [#w87fb73d] -inconsistent --In general, it is observed that the evidence regarding the mediation effect of size is inconsistent and does not follow a pattern across all systems. -contradictory --In general, this study provides results contradictory to those of El Emam et al. [6] and Zhou et al. [25]. ***因習的な [#n7f9dc5d] -conventional --In fault prediction research for classes in object-oriented (OO) systems, it is conventional to account for the confounding effect of class size. ***困惑させる [#b3211022] -confounding ----In fault prediction research for classes in object-oriented (OO) systems, it is conventional to account for the confounding effect of class size. ***明確な [#wd8ac66d] -evident --In contrast to prior studies on fault-proneness, the mediation effect is not evident across all systems examined. ***現代の [#xca33284] -modern -contemporary --We also use contemporary robust statistical procedures to accurately estimate the true effect of size in these prediction models. ***結果として生じる [#idb0f540] -resulting --If zero does not fall between the resulting confidence interval values of LL and UL (i.e., both values are either positive or negative) then it is concluded that the indirect effect is not zero with 95% confidence [20]. ***決定的でない [#a19d716f] -inconclusive in --However, we still consider these results inconclusive in determining if the indirect effect is truly and always significant. ***わずかな [#yfd1aa78] -negligible --Even though previous literature has raised awareness on the prevalence of bugs in test files, such as the work by Vahabzadeh et al. [46], it may well be that these type of bugs constitute such a negligible number compared to defects found in production code that investing resources in reviewing them would not be advisable.
