論文英語単語帳/名詞の履歴(No.16) - PukiWiki

[ トップ ] [ 新規 | 一覧 | 検索 | 最終更新 | ヘルプ ]

論文英語単語帳

リンク†

名詞†

不十分，不足†

insufficiency
- Due to the insufficiency of documentation,

利用できないこと、役に立たないこと、使い勝手の悪さ†

unavailability
- Due to the insufficiency of documentation,

新しい種類の、新手の†

novel
- a novel approach to learn API usages

特徴†

characteristic
- our approach has three distinctive characteristics.

関数の呼び出し順序†

method call sequence
- a given collection of method call sequences involving the API objects it models.

観察†

observation
- The observations are stored in enriched event streams that encode a holistic picture of the in-IDE development process.

現象・事象†

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.

事後検証†

post-mortem
- Post-mortem analysis of bugs for understanding various characteristics of various bugs can have many benefits.

専門用語†

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.

潜在能力†

potential
- An aggregation has the potential to be very useful in building descriptive or prescriptive models based on historical data.

状況†

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.

後方互換性†

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

研究構想†

research initiative
- Section II further explains the motivation for this research initiative.

有形資産†

tangibles
- In an area where the processes are so amorphous, the tangibles required for measurement and modeling are few.

追求†

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.

ユーザエクスペリエンス†

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.

範囲†

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.

（人生の）軌跡†

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.

適合†

congruence
- The congruence of a newcomer's social and technical activities is crucial for successful participation in an open source project.

僅かにことなるもの†

variant
- While the labels vary by project, they typically amount to some variant of Severe, Normal, and Minor.

観念†

notion
- We first briefly present the notion of a bug tracking system, and the levels of severity that such systems commonly use.

一貫性†

consistency
- This has created consistency problems when metrics data is pulled across projects.

仮定†

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.

熟考†

deliberation
- experts can help in design deliberations of complex problem and users can be made aware of the status of a bug