This topic was presented on Japan LabVIEW User Conference #2.
I introduced why TDD, how does it improve our development process. I developed FizzBuzz with TDD way in live.
This topic was presented on Japan LabVIEW User Conference #2.
I introduced why TDD, how does it improve our development process. I developed FizzBuzz with TDD way in live.
This slide is for Ultimate Agilist Tokyo in Japan. 2012.Nov.
I want to think about agile programmer's skill set. and I want to introduce ICAgile to Japan.
I analyzed agile value, principles, practices and ICAgile.
and participant members created some mandatory skill set in this session.
See this blog entry , that will be better.
http://simple-architect.blogspot.jp/2012/11/agile-programmers-skill-set-ultimate.html
[db tech showcase Tokyo 2016] D24: データベース環境における検証結果から理解する失敗しないフラッシュ活用法 第三章 ~デ...Insight Technology, Inc.
フラッシュのGB単価はHDDと並び、オールフラッシュ導入が加速化する一方、インラインでの重複排除、圧縮機能のオーバーヘッド、メンテナンス / 障害時の影響など、気をつけなければいけない事は沢山あります。本セッションでは、オールフラッシュ製品(Pure Storage)上でOracle Databaseを稼働させた検証結果と生のデモンストレーションをベースに、DB on Pure Storageならではの活用法を考えます。
No one can predict unforeseen killer applications enabled by new wireless technologies (e.g., 5G network) beforehand. Looking back 20-year history of mobile wireless network, it has been very tough to prepare killer applications a prior to the emergence of new radio access technologies. NTT DOCOMO’s i-mode was not prepared for 2G always-on network., and invented after that. Smartphones with application markets became popular after the 3G network deployment, for which video conversation had been prepared a a killer service candidate and which didn’t make a success. 4G network brought us more capacity and low latency network, while youtube, hulu, Netflix, facebook messenger and others were natured by such a rich mobile communication environment with cloud platforms.
Everyone, nowadays, are talking about a buzz word “IoT” without having a solid idea for monetization. Such a bold discussion may mislead our radio access technology development to an unpromised land.
My recommendation is “Decide as late as possible, particularly for decisions that are irreversible.” According to software engineering terminology, it says also “late binding.” Don’t rush into a 10Gps broadband network nor a hyper low latency and 0% packet-loss assured network.
Having said that, the 5G beam forming radio technology (enabled by Massive MIMO) will bring a unique communication characteristics with a more reliable, higher capacity and 3D-positioning. My bet on 5G killer applications is “Night Golf” where you can play golf without seeing a ball which is being identified by the 5G radio. haha.
17. ペアプログラミングとは
"Write all production programs with two people sitting at
one machine. ... Pair programming is a dialog between
two people simultaneously programming (and designing
and testing) and to program better."
(Extreme Programming Explained 2nd)
「プロダクションコードはすべて、2人で1台のマシンに
向かって書くこと。…ペアプログラミングとは、プロ
グラミングしながら2人で会話することだ(設計もテス
トも同時にする)。会話するのは、もっと上手にプログ
ラムするためである。」
30. テスト駆動開発の効果
IBM
ドライバ
Microsoft
Windows
Microsoft
MSN
Microsoft
VisualStudio
チーム人数 9 6 5-7 7
コード量(KLOC) 41.0 6.0 26.0 155.2
開発規模(人月) 119 24 46 20
欠陥数
(TDD未使用に対
する)
61% 38% 24% 9%
開発時間の増加
(管理者の見積)
15~20% 25~35% 15% 20~25%
Nachiappan Nagappan, E. Michael Maximilien, Thirumalesh Bhat, Laurie Williams “Realizing
quality improvement through test driven development: results and experiences of four
industrial teams” 2008
http://research.microsoft.com/en-us/groups/ese/nagappan_tdd.pdf
31. 保守性への影響
※1 保守期間(260日間)中、変更要求の対応にかかった工数の平均
"The effectiveness of test-driven development: an industrial case study"
(Tomazˇ Dogsˇa • David Baticˇ , Software Qual J (2011))
生産性
(行数/工数)
保守性 ※1
(工数/変更件数)
プロジェクトA
(非TDD)
2.3 84
プロジェクトB
(非TDD)
2.5 80
プロジェクトC
(TDD)
1.8 59
32. TDDの効果の研究をまとめた研究
"Effects of Test-Driven Development: A Comparative
Analysis of Empirical Studies" Simo Makinen and Jurgen
Munch, 2013
• 既存の実証研究を調査し、10の内部・外部品質評
価項目で、各研究の結論を整理した
• TDDは欠陥の作り込み(introduced defects)を減
らし、メンテナンスしやすいコードを産む
• TDDで実装されたコードは、部分的に、サイズが
小さく、複雑度が低い場合がある
• メンテナンスがしやすくなるものの、初期開発で
は時間がかかる
37. テスト駆動開発の効果
IBM
ドライバ
Microsoft
Windows
Microsoft
MSN
Microsoft
VisualStudio
チーム人数 9 6 5-7 7
コード量(KLOC) 41.0 6.0 26.0 155.2
開発規模(人月) 119 24 46 20
欠陥数
(TDD未使用に対
する)
61% 38% 24% 9%
開発時間の増加
(管理者の見積)
15~20% 25~35% 15% 20~25%
Nachiappan Nagappan, E. Michael Maximilien, Thirumalesh Bhat, Laurie Williams “Realizing
quality improvement through test driven development: results and experiences of four
industrial teams” 2008
http://research.microsoft.com/en-us/groups/ese/nagappan_tdd.pdf