論文英語単語帳/接続詞
の編集
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/%E6%8E%A5%E7%B6%9A%E8%A9%9E
[
トップ
] [
編集
|
差分
|
履歴
|
添付
|
リロード
] [
新規
|
一覧
|
検索
|
最終更新
|
ヘルプ
]
-- 雛形とするページ --
(no template pages)
[[論文英語単語帳]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *AND [#z7d3d450] **Listing [#pb556952] ***Enumeration (points in order) [#jf7efa4b] -最初に,さらに,さいごに [#f475fee5] --first/furthermore/finally --one / a second / a third --first(ly), /second(ly), / third(ly), --to begin [start with], / in the second place, / moreover, /to conclude, -最後に --above all --last but not least -最初に --first and foremost --first and most importantly ***Addition-Reinforcement [#w92b5522] -さらに --besides (カジュアル) --furthermore ---Furthermore, we also find that security bugs involve more developers and impact more files in a project. ---Furthermore, lean web apps like the popular IMVU chat application1 release up to 50 times per day [26]. --in addition ---In addition, it is also error-prone because online code examples might not be up-to-date to the latest changes of the mobile API frameworks. --additionally ---Additionally, we find that the adherence to semantic versioning principles has only marginally increased over time. --moreover ---Moreover, typical API usage scenarios often include several API elements and follow special rules ---Moreover, the build system automates many other activities, such as test execution and sometimes deployment. A build system typically consists of a configuration layer and a construction layer [3]. --additionally --what is more -もまた --again --also --as well (as) ---Performance bugs are difficult to expose, primarily because detecting them requires specific inputs, as well as a specific execution environment. --too --not only ... but also ... --then -特に --particularly --specifically --especially --notably --obviously -実は --actually --indeed ---Indeed, it was market pressure, the influence of agile development and the desire to bring value to the customer faster that inspired the recent phenomenon of continuous delivery -その他 --above all --further ***Addition-Comparison [#eecea2fa] -もまた --also --both ... and ... --too -同様に --likewise --similarly --equally --in the same way --correspondingly **Transition (leads to a new stage) [#x0da0081] -次に --now --turning to -に関しては --as for --regarding --as to --with regard to --with respect to **Summary (gives a summary or conclusion) [#sdf342ea] -このように --therefore --thus ---More severely, mobile apps are often closed-source, i.e. their source code is not publicly available. Thus, finding and learning code examples from existing mobile app projects would be difficult. --hence --then -要するに --altogether --in brief --to summarise --in short --i.e. ---mobile apps are often closed-source, i.e. their source code is not publicly available. -結論として --to conclude --in conclusion --to sum up -全体的には --overall **Reference (refers to what was said before) [#jf7eca4d] -主に --chiefly --mainly --mostly -特に --notably --particularly --in particular -例えば --for instance --for example --- For example, an Android app might make 8-42% of its external dependencies to Android APIs and 7-68% to Java APIs --e.g. ---typical API usage scenarios often include several API elements and follow special rules, e.g. for pre- and post-conditions or for control and data flows --such as ---traditional testing such as coverage-based approaches may not be effective. -を含めて --including -つまり・すなわち --in other words --that is --namely -次の通り --as follows -その他(よくわからん) --and --or **Example [#l402d763] -for example -for instance -such as -to illustrate -as an illustration -to demonstrate **Result (the consequence of what was said before) [#web1c228] -それゆえ --accordingly --hence --therefore --thus ---those mobile apps often have very short time-to-market and upgrade cycles, thus, requiring short development time. -その結果 --as a result --as a consequence --consequently --so that --in order that --the consequence is --the result is -が原因で --because of --for this/that reason -それで --now --so --then **Place (refer to things in or outside the document) [#x51b0200] -above -adjacent -at the side -behind -below -elsewhere -here -in front -in the backgroud -in the foregrand -there -to the left -to the right **Time (refers to other studies) [#c978d89e] -after a while -afterwards -at last -at that time -at the same time -before -currently -earlier -eventually -finally -formerly -in the meantime -in the past -initially -laster -meanwhile -now -once --Once configured, the construction layer is used to specify the build tool invocations that are required to gen- erate deliverables from source code. -presently -previously -shortly -simultaneously -since -as --As these pioneering organizations successfully developed experimental tools and practices to make such rapid release cycles a reality, Facebook’s release engineering director, Chuck Rossi, claimed that “continuous delivery for web apps is a solved problem” [65]. -soon -subsequently -then -thereafter -until -until now -whenever -while --Modern software systems are highly-configurable, allowing users to customize a large number of configuration operations while retaining a core set of functionality. --most existing work assumes default configurations while ignoring the influence of various configurations. *OR [#g14b3bb2] **Reformulation (expresses something in another way) [#n58d15ee] -better -in other words -in that case -rather -that is -that is to say -to put it (more) simply **Replacement (expresses an alternative) [#l0e974f6] -again -alternatively -another possibility would be -better still -worse still -on the other hand -rather -the alternative is *BUT [#ib1b67d4] **Contrast (presents a different view) [#jd3f6b80] -In contrast to --In contrast to other research fields (even within the software engineering discipline), recent advances in release engineering have largely been made by industry, not academia. -by (way of) contrast -conversely -in comparison -in fact -in reality -instead --Instead, all test stages obtain the deliverables that were built by the CI process from a so-called “artifact repository.” -on the contrary -on the other hand -then **Concession (agrees that something is good, with limitations) [#c0189196] -なんといっても/とりわけ --after all --admittedly --doubtless --no doubt -それでもなお/それにもかかわらず --all the same --nonetheless --under certain circumstances --nevertheless ---Automated tests (hereafter referred to as just ‘tests’) can help ensure that production code is robust under many usage conditions and that code meets performance and security needs [15, 16]. Nevertheless, writing effective tests is as challenging as writing good production code. --notwithstanding --still --yet -けれども --although --although this may be true --at the same time --despite ---Despite careful reviewing of individual commits, branch merges still pose a risk of so-called merge conflicts [18, 67], which cause significant costs for companies [17]. --even though --in spite of -を覗いて --besides -としても --even if --even so -だが --however ---However, learning API usages is often challenging due to the fast-changing nature of API frameworks for mobile systems and the insufficiency of API documentation and source code examples. --while ---While researchers have developed techniques to analyze, quantify, detect, and fix performance bugs, we conjecture that many of these techniques may not be effective in highly-configurable systems. ---While most of the recent advances in release engineering, such as best practices and tooling, have been driven by industry, researchers can play an essential role in addressing the above questions. -ただし --only -もちろん --naturally -その点では --up to a point
タイムスタンプを変更しない
[[論文英語単語帳]] ***リンク [#f20ebad6] #ls2(論文英語単語帳/) *AND [#z7d3d450] **Listing [#pb556952] ***Enumeration (points in order) [#jf7efa4b] -最初に,さらに,さいごに [#f475fee5] --first/furthermore/finally --one / a second / a third --first(ly), /second(ly), / third(ly), --to begin [start with], / in the second place, / moreover, /to conclude, -最後に --above all --last but not least -最初に --first and foremost --first and most importantly ***Addition-Reinforcement [#w92b5522] -さらに --besides (カジュアル) --furthermore ---Furthermore, we also find that security bugs involve more developers and impact more files in a project. ---Furthermore, lean web apps like the popular IMVU chat application1 release up to 50 times per day [26]. --in addition ---In addition, it is also error-prone because online code examples might not be up-to-date to the latest changes of the mobile API frameworks. --additionally ---Additionally, we find that the adherence to semantic versioning principles has only marginally increased over time. --moreover ---Moreover, typical API usage scenarios often include several API elements and follow special rules ---Moreover, the build system automates many other activities, such as test execution and sometimes deployment. A build system typically consists of a configuration layer and a construction layer [3]. --additionally --what is more -もまた --again --also --as well (as) ---Performance bugs are difficult to expose, primarily because detecting them requires specific inputs, as well as a specific execution environment. --too --not only ... but also ... --then -特に --particularly --specifically --especially --notably --obviously -実は --actually --indeed ---Indeed, it was market pressure, the influence of agile development and the desire to bring value to the customer faster that inspired the recent phenomenon of continuous delivery -その他 --above all --further ***Addition-Comparison [#eecea2fa] -もまた --also --both ... and ... --too -同様に --likewise --similarly --equally --in the same way --correspondingly **Transition (leads to a new stage) [#x0da0081] -次に --now --turning to -に関しては --as for --regarding --as to --with regard to --with respect to **Summary (gives a summary or conclusion) [#sdf342ea] -このように --therefore --thus ---More severely, mobile apps are often closed-source, i.e. their source code is not publicly available. Thus, finding and learning code examples from existing mobile app projects would be difficult. --hence --then -要するに --altogether --in brief --to summarise --in short --i.e. ---mobile apps are often closed-source, i.e. their source code is not publicly available. -結論として --to conclude --in conclusion --to sum up -全体的には --overall **Reference (refers to what was said before) [#jf7eca4d] -主に --chiefly --mainly --mostly -特に --notably --particularly --in particular -例えば --for instance --for example --- For example, an Android app might make 8-42% of its external dependencies to Android APIs and 7-68% to Java APIs --e.g. ---typical API usage scenarios often include several API elements and follow special rules, e.g. for pre- and post-conditions or for control and data flows --such as ---traditional testing such as coverage-based approaches may not be effective. -を含めて --including -つまり・すなわち --in other words --that is --namely -次の通り --as follows -その他(よくわからん) --and --or **Example [#l402d763] -for example -for instance -such as -to illustrate -as an illustration -to demonstrate **Result (the consequence of what was said before) [#web1c228] -それゆえ --accordingly --hence --therefore --thus ---those mobile apps often have very short time-to-market and upgrade cycles, thus, requiring short development time. -その結果 --as a result --as a consequence --consequently --so that --in order that --the consequence is --the result is -が原因で --because of --for this/that reason -それで --now --so --then **Place (refer to things in or outside the document) [#x51b0200] -above -adjacent -at the side -behind -below -elsewhere -here -in front -in the backgroud -in the foregrand -there -to the left -to the right **Time (refers to other studies) [#c978d89e] -after a while -afterwards -at last -at that time -at the same time -before -currently -earlier -eventually -finally -formerly -in the meantime -in the past -initially -laster -meanwhile -now -once --Once configured, the construction layer is used to specify the build tool invocations that are required to gen- erate deliverables from source code. -presently -previously -shortly -simultaneously -since -as --As these pioneering organizations successfully developed experimental tools and practices to make such rapid release cycles a reality, Facebook’s release engineering director, Chuck Rossi, claimed that “continuous delivery for web apps is a solved problem” [65]. -soon -subsequently -then -thereafter -until -until now -whenever -while --Modern software systems are highly-configurable, allowing users to customize a large number of configuration operations while retaining a core set of functionality. --most existing work assumes default configurations while ignoring the influence of various configurations. *OR [#g14b3bb2] **Reformulation (expresses something in another way) [#n58d15ee] -better -in other words -in that case -rather -that is -that is to say -to put it (more) simply **Replacement (expresses an alternative) [#l0e974f6] -again -alternatively -another possibility would be -better still -worse still -on the other hand -rather -the alternative is *BUT [#ib1b67d4] **Contrast (presents a different view) [#jd3f6b80] -In contrast to --In contrast to other research fields (even within the software engineering discipline), recent advances in release engineering have largely been made by industry, not academia. -by (way of) contrast -conversely -in comparison -in fact -in reality -instead --Instead, all test stages obtain the deliverables that were built by the CI process from a so-called “artifact repository.” -on the contrary -on the other hand -then **Concession (agrees that something is good, with limitations) [#c0189196] -なんといっても/とりわけ --after all --admittedly --doubtless --no doubt -それでもなお/それにもかかわらず --all the same --nonetheless --under certain circumstances --nevertheless ---Automated tests (hereafter referred to as just ‘tests’) can help ensure that production code is robust under many usage conditions and that code meets performance and security needs [15, 16]. Nevertheless, writing effective tests is as challenging as writing good production code. --notwithstanding --still --yet -けれども --although --although this may be true --at the same time --despite ---Despite careful reviewing of individual commits, branch merges still pose a risk of so-called merge conflicts [18, 67], which cause significant costs for companies [17]. --even though --in spite of -を覗いて --besides -としても --even if --even so -だが --however ---However, learning API usages is often challenging due to the fast-changing nature of API frameworks for mobile systems and the insufficiency of API documentation and source code examples. --while ---While researchers have developed techniques to analyze, quantify, detect, and fix performance bugs, we conjecture that many of these techniques may not be effective in highly-configurable systems. ---While most of the recent advances in release engineering, such as best practices and tooling, have been driven by industry, researchers can play an essential role in addressing the above questions. -ただし --only -もちろん --naturally -その点では --up to a point
テキスト整形のルールを表示する