软件工程规范
A discipline for software engineering
Watts S. Humphrey · 初版 1995 年
2人推荐
4位读者提及
10次提及
这部来自颇具影响力的《Managing the Software Process》一书作者 Watts Humphrey 的新作，拓展了他关于软件过程管理的系统性构想，并为规范化的软件工程方法奠定了基础。在其前作中，作者提出了管理软件开发与维护的具体方法。这些如今已在业界广泛应用的方法，为程序员和管理者提供了评估和提升自身软件能力的明确步骤。在这本新书中，Humphrey 将这些方法细化至个人层面，帮助软……
Hacker News 上怎么说
正在加载完整评论……
……肯定会有人提到《C程序设计语言》（The C Programming Language）。换作最近，这就意味着 Zed Shaw 肯定要被拉出来提一嘴，然后大家就开始喜闻乐见地看乐子了。我自己的话？我肯定会选《代码大全》（Code Complete，我第一版还留着呢），可能再加上《软件工程规范》（A Discipline for Software Engineering）和《软件预估：揭秘黑魔法》（Software Estimation: Demystifying the Black Art）。我发现 Dorset House 出版社的书基本上都值得花时间看，所以在《人件》（Peopleware）之外我还会加上《最后期限》（The Deadline）以及《Adrenalin Junkies and Template Zombies》……
…The C Programming Language will be mentioned. These days that means Zed Shaw will be named and hilarity will ensue. Myself? I'd definitely have Code Complete (I still have my first edition), perhaps A Discipline for Software Engineering and Software Estimation: Demystifying the Black Art. I've found pretty much everything from Dorset House to be worth my time, so to PeopleWare I'd add The Deadline and Adrenalin Junkies and Template Zombies.…
你可能会觉得 Watts Humphrey 写的《软件工程规范》（A Discipline for Software Engineering）读起来挺有意思。他在书里描述了一套方案，让你追踪自己犯下的所有错误，不管多微小，并耐心地摸索出防止它们以后再发生的方法。edit：听着，我知道……
You might find Watts Humphrey's book A Discipline for Software Engineering to be an interesting read. In it he describes a scheme where you track all your mistakes, no matter how tiny, and patiently develop ways to prevent them from happening in future. edit: Look, I know that…
原理与动机（How and why）：读 Tom Gilb 的《软件审查》（Software Inspection）。做中学（Learn by doing）：读 Watts S. Humphrey 的《软件工程规范》（A Discipline for Software Engineering）。直接跳到后面的练习题去做，因为这书 95% 的价值都在练习题里，正文写得不咋地（急需重写）。人们经常犯的错误是只做 code……
How and why: Read "Software Inspection" by Tom Gilb Learn by doing: Read "A Discipline for Software Engineering" by Watts S. Humphrey. Skip to the exercises at the back, as 95% of the value is in the exercises, the main book is not that good (wants a re-write). Often, people make the mistake of only doing a code…
……那个错误。过上一段时间，你就可以用自己的数据，通过……checklist（检查清单）来纠正你的常见错误了！当然还有其他工具和实践，但 checklist 是 PSP 的重要组成部分。哪怕你从来不用它，《软件工程规范》（A Discipline for Software Engineering）也值得一读。
…the mistake. After a while you use your data to correct your common errors with ... checklists! And other tools and practices, of course, but checklists are a big part of the PSP. It's worth reading A Discipline for Software Engineering, even if you never apply it.
你可能会觉得 Watts Humphrey 写的《软件工程规范》（A Discipline for Software Engineering）读起来挺有意思。
You may find A Discipline for Software Engineering by Watts Humphreys to be an interesting read.
质量控制方面的创新：需求评审、测试驱动开发（TDD）、Agile。去读一读 Tom Gilb 的《软件审查》（Software Inspection）吧。《软件工程规范》（A Discipline for Software Engineering）后面的练习也非常棒（虽然正文写得真不怎么样）。Edit：理解一下“每小时消除的 bug 数”（bugs removed per hour）是很有价值的。每一项质量控制“创新”都有一个 bug 消除率，并且能够提升……
Quality control innovations: Requirements reviews, Test driven development, Agile. Have a read of Software Inspection by Tom Gilb. The exercises at the back of A Discipline for Software Engineering are also very good (although the main book is not that good). Edit: It is worth understanding "bugs removed per hour". Every quality control "innovation", has a bug removal rate and will improve the…