mythsame的专栏

老外写的软件需求分析，打架可以看一看 Why is it one of first activities in software life cycle? Need to understand what customer wants first! Goal is to understand the customer’s problem Though customer may not fully understand it! Requirements analysis says: “Make a list of the guidelines we will use to know when the job is done and the customer is satisfied.” AKA requirements gathering or requirements engineering System specification says: “Here’s a description of what the program will do (not how) to satisfy the requirements.” Distinguish requirements gathering & system analysis? A top-level exploration into the problem and discovery of whether it can be done and how long it will take

对很多粗略接触到 Extreme Programming 的人来说，XP 似乎 宣告了软件设计的死刑。不只很多的设计被嘲笑为 "Big Up Front Design "[译注1]，连很多技术像UML、富有弹性的程序架构 (framework)，甚至连模式 (pattern) 都不受重视，或是近似忽略了。事实上，XP内含很多设计理念，但是它与现有的软件流程有着不同的运作方式。XP藉由多种实务技巧 (practice) 赋予演进式设计 (evolutionary design) 崭新的风貌，让演进变成一种实用的设计方法。它也让设计者 (designer[译注2]) 面临新的挑战与技巧，学习如何使设计精简，如何使用重构来保持一个设计的清楚易懂，以及如何逐步地套用模式。

风河关于DO-178B的课件，里面讲解了DO-178B的主要思想，目标，以及如何达成方面的东东。