cvpaper.challengeにおいてECCVのOral論文をまとめた「ECCV 2020 報告」です。
ECCV2020 Oral論文 完全読破(1/2) [https://www.slideshare.net/cvpaperchallenge/eccv2020-oral-12/1]
pp. 7-10 ECCVトレンド
pp. 12-72 Looking at humans
pp. 73-132 Low level vision
pp. 133-198 Recognition & detection
pp. 199-262 Segmentation & scene interpretation and description, language
pp. 263-294 Video & action understanding
pp. 295-296 まとめ
cvpaper.challengeはコンピュータビジョン分野の今を映し、トレンドを創り出す挑戦です。論文サマリ作成・アイディア考案・議論・実装・論文投稿に取り組み、凡ゆる知識を共有します。2020の目標は「トップ会議に30+本投稿」することです。
cvpaper.challengeにおいてECCVのOral論文をまとめた「ECCV 2020 報告」です。
ECCV2020 Oral論文 完全読破(1/2) [https://www.slideshare.net/cvpaperchallenge/eccv2020-oral-12/1]
pp. 7-10 ECCVトレンド
pp. 12-72 Looking at humans
pp. 73-132 Low level vision
pp. 133-198 Recognition & detection
pp. 199-262 Segmentation & scene interpretation and description, language
pp. 263-294 Video & action understanding
pp. 295-296 まとめ
cvpaper.challengeはコンピュータビジョン分野の今を映し、トレンドを創り出す挑戦です。論文サマリ作成・アイディア考案・議論・実装・論文投稿に取り組み、凡ゆる知識を共有します。2020の目標は「トップ会議に30+本投稿」することです。
Evolution of Pattern Languages: Designing Human Actions, Dialogue, & Films (P...Takashi Iba
Takashi Iba, "Evolution of Pattern Languages: Designing Human Actions, Dialogue, & Films", presented in the PUARL2013 conference, Portland, Oregon, on Nov. 3rd, 2013
Testing System Qualities Agile2012 by Rebecca Wirfs-Brock and Joseph YoderJoseph Yoder
Agile teams incrementally deliver functionality based on user stories. In the sprint to deliver features, frequently software qualities such as security, scalability, performance, and reliability are overlooked. Often these characteristics cut across many user stories. Trying to deal with certain system qualities late in the game can be difficult, causing major refactoring and upheaval of the system’s architecture. This churn isn’t inevitable. Especially if you adopt a practice of identifying those characteristics key to your system’s success, writing quality scenarios and tests, and delivering on these capabilities at the opportune time. We will show how to write Quality Scenarios that emphasize architecture capabilities such as usability, security, performance, scalability, internationalization, availability, accessibility and the like. This will be hands-on; we present some examples and follow with an exercise that illustrates how you can look at a system, identify, and then write and test quality scenarios.
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard WorkJoseph Yoder
Big Ball of Mud (BBoM) architectures are viewed as the culmination of many design decisions that, over time, result in a system that is hodgepodge of steaming and smelly anti-patterns. It can be arguably claimed that one of the reasons for the growth and popularity of agile practices is partially due to the fact that the state of the art of software architectures was not that good. Being agile, with its focus on extensive testing and frequent integration, has shown that it can make it easier to deal with evolving architectures (possibly muddy) and keeping systems working while making significant improvements and adding functionality. Time has also shown that Agile practices are not sufficient to prevent or eliminate Mud. It is important to recognize what is core to the architecture and the problem at hand when evolving an architecture.
This talk will examine the paradoxes that underlie Big Balls of Mud, what causes them, and why they are so prominent. I’ll explore what agile practices can help us avoid or cope with mud. I’ll also explain why continuous delivery and TDD with refactoring is not enough to help ensure clean architecture and why it is important to understand what is core to the architecture and the problem at hand. Understanding what changes in the system and at what rates can help you prevent becoming mired in mud. By first understanding where a system’s complexities are and where it keeps getting worse, we can then work hard (and more intelligently) at sustaining the architecture. This can become a key value to the agile team. The results will leave attendees with practices and patterns that help clean your code (refactor) as well as keeping the code clean or from getting muddier.
Additionally, I’ll talk about some practices and patterns that help keep the code clean or from getting muddier. Some of these include: Testing, Divide & Conquer, Gentrification, Demolition, Quarantine, Refactoring, Craftmanship and the like.. The original Big Ball of Mud paper described some best practices such as SHEARING LAYERS and SWEEPING IT UNDER THE RUG as a way to help deal with muddy architectures. Additionally there are some other practices such as PAVING OVER THE WAGON TRAIL and WIPING YOUR FEET AT THE DOOR that can make code more habitable.
大きな泥のカタマリを相手にするためのアジャイルと努力と苦労 by Joe Yoder (XP祭り2014)
1. 大きな泥のカタマリを 相手にするための アジャイルと努力と苦労
Copyright 2014 Joseph W. Yoder & The Refactory, Inc.
XP Matsuri–September 6th, 2014Joseph W. Yoder --www.refactory.comwww.teamsthatinnovate.com
2. 継続可能な アーキテクチャ
Copyright 2014 Joseph W. Yoder & The Refactory, Inc. Joseph W. Yoder --www.refactory.com
33. Sustaining Your Architecture シンプルな リファクタリングの例
Object
Concrete1
Concrete2
Object
Concrete1
Concrete2
NewAbstract
空クラスを作る Borrwedfrom Don Roberts, The Refactory, Inc.
34. Sustaining Your Architecture 複雑な リファクタリングの例 困難なリファクタリングもあるが、小さなステップ を多数積み重ねれば泥退治に大きな効果を得られる
Borrowed from Don Roberts, The Refactory, Inc.
Array
Matrix
Matrix
MatrixRep
ArrayRep
rep
SparseRep
IdentityRep
38. Sustaining Your Architecture コードの臭い (Code Smell) コードの臭いはコードのどこかで なにかマズいことが起きている兆候。 臭いを追跡して問題を発見するケント・ベック コードの不吉な臭いはケント・ベックと マーチン・ファウラーの書いたエッセイで、 「リファクタリング 既存のコードを安全に改善する」 の3章に収録----Ward’s Wiki
Have you ever looked at a piece of code that doesn't smell very nice?
54. Sustaining Your Architecture2種類のリファクタリング* デンタルフロスリファクタ リング 頻繁、小さな変化、他のプロ グラミング作業 (日々の健康管理)と一緒 根管治療リファクタリング 稀、長引く、その間プログラ マは他のことをできない(大規 模修理)
* Emerson Murphy-Hill and Andrew Black in“Refactoring Tools: Fitness for Purpose”
http://web.cecs.pdx.edu/~black/publications/IEEESoftwareRefact.pdf
55. Sustaining Your Architecture 共有の知恵 「ほとんどの場合、私はリファ クタリングの時間を別に取るの に反対だ。私の考えでは、リフ ァクタリングは時間を取ってや るようなものではない。リファ クタリングはいつでもやるものだ 。小さなまとりで(in little bursts)」 —Martin Fowler
リファクタリングを日々の業務に組み込む
64. Sustaining Your Architecture 継続的インスペクション
Asian PLoP2014 Paper
コードの臭い検出
メトリクス(テストカバレジ、循環的複雑度、技術的負 債、大きさ、……)
アプリケーションセキュリティ チェック
アーキテクチャへの適合性
できるだけ自動化する!!!