模板
教程
環境
性能
功能
管理
對結合BDD進行DDD開發的一點思考和整理(5)
之前那種依賴于語言本身對How和What進行的討論，此時便顯得如此拙劣。對此，Gojko有這樣一段精彩的闡述：
But now I advise people not to think about that, instead to think about impacts and deliverables. Deliverables are stuff you do in your zone of control, impacts are how those things influence actors in your sphere of influence. You can call these questions "what/how" or "how/what" or not think about the questions at all, depending on what the group in the room understands better.
它回答了之前一直困擾我的問題。即What是在開發團隊控制范圍內的，能對Actor產生影響的那些事物。這些是我們努力就一定能做到的，比如系統能提供的具體功能。而How則是我們期望的、能對Actor產生的影響。這種影響相對開發團隊而言，是間接和被動的。對此，Gojko用一個手機App進行了形象的比喻：
Impacts - this is your sphere of influence - things you don't control directly, but things you think you can influence. Deliverables - this is your zone of control. The big question to differentiate between the two is: is there an assumption here, or are we guaranteed to achieve it if we decide to do it. Eg if we decide to build an iPhone App, we will. But if we decide to get people to buy the app on the appstore more, regardless of all our efforts that might not happen. The first one is in our zone of control, the second is in the sphere of influence.
期間我對Business Goal也重新進行了認識。 BDD in Action 曾用Specific（特定的）、Measurable（可量化的）、Achievable（可實現的）、Relevant（相關的）、Time-bound（有期限的）對其進行說明，而發掘Goal的工具真的是如此簡單——不停地問Why……然后，我又重繪了之前的圖：
再補上MelvinPerezCx對Impact Map與各種產出件之間關系的一張好圖：
繼續前進
原文轉自：http://www.cnblogs.com/Abbey/p/5143674.html
