人月神话 The Mythical Man-Month
中文PDF:
http://www.pcbookcn.com/book/681.htm
http://download.csdn.net/down/964174/zhezhe7
英文PDF:
http://d.download.csdn.net/down/964173/zhezhe7
在软件领域，很少能有像《人月神话》一样具有深远影响力和畅销不衰的著作。Brooks博士为人们管理复杂项目提供了最具洞察力的见解，既有很多发人深省的观点，又有大量软件工程的实践。本书内容来自Brooks博士在IBM公司SYSTEM／360家族和OS／360中的项目管理经验，该项目堪称软件开发项目管理的典范。该书英文原版一经面世，即引起业内人士的强烈反响，后又译为德、法、日、俄、中、韩等多种文字，全球销售数百万册。确立了其在行业内的经典地位。
在本书第一次出版32年后的今天，我们重新整理了Brooks博士的经典内容，并将国内软件开发领域先行者们对《人月神话》中的实践及系统理论的使用经验和心得集结成册免费赠与大家共享，更使本书成为国内从业者的必读经典之一。
本书读者包括：软件开发人员、软件项目经理、系统分析师等IT从业者。
[编辑本段]
Freder ick P.Brooks，Jr.曾荣获美国计算机领域最具声望的图灵奖（A.M.TURINGAWARD）桂冠。美国计算机协会（ACM）称赞他"对计算机体系结构、操作系统和软件工程作出了里程碑式的贡献"。
Brooks博士是北卡罗莱纳大学KENAN-FLAGLER商学院的计算机科学教授。他被认为是"IBM 360系统之父"，曾担任360系统的项目经理，以及360系统项目设计阶段的经理。凭借在此项目中的杰出贡献，他与BobEvarls和Erich BIocll在1985年荣获了美国国家技术奖（NationalMedal of TecPlnoIogy）。Brooks博士早期曾担任IBM公司stretcPl和Harvest计算机的体系结构设计师。
Brooks博士创立了北卡罗莱纳大学的计算机科学系，并在1964-1984年期间担任系主任。他还曾任职于美国国家科技局和国防科学技术委员会。Brooks博士目前的教学和研究方向是计算机体系结构、分子模型绘图和虚拟环境设计。
[编辑本段]
第1章 焦油坑
编程系统产品l
职业的乐趣l
职业的苦恼l
第2章 人月神话
乐观主义l
人月l
系统测试l
空泛的估算l
重复产生的进度灾难l
第3章 外科手术队伍
问题l
Mills的建议l
如何运作l
团队的扩建l
第4章 贵族专制、民主政治和系统设计
概念的完整性l
获得概念的完整性l
贵族专制统治和民主政治l
在等待时，实现人员应该做什么l
第5章 画蛇添足
结构师的交互准则和机制l
自律-开发第二个系统所带来的后果l
第6章 贯彻执行
文档化的规格说明-手册l
形式化定义l
直接整合l
会议和大会l
多重实现l
电话日志l
产品测试l
第7章 为什么巴别塔会失败
巴别塔的管理教训l
大型编程项目中的交流l
项目工作手册l
大型编程项目的组织架构l
第8章 胸有成竹
Portman的数据l
Aron的数据l
Harr的数据l
OS/360的数据l
Corbato的数据l
第9章 削足适履
作为成本的程序空间l
规模控制l
空间技能l
数据的表现形式是编程的根本l
第10章 提纲挈领
计算机产品的文档l
大学科系的文档l
软件项目的文档l
为什么要有正式的文档l
第11章 未雨绸缪
试验性工厂和增大规模l
惟一不变的就是变化本身l
为变更计划系统l
为变更计划组织架构l
前进两步，后退一步l
前进一步，后退一步l
第12章 干将莫邪
目标机器l
辅助机器和数据服务l
高级语言和交互式编程l
第13章 整体部分
剔除bug的设计l
构件单元调试l
系统集成调试l
第14章 祸起萧墙
里程碑还是沉重的负担l
"其他的部分反正会落后"l
地毯的下面l
第15章 另外一面
需要什么样的文档l
流程图l
自文档化的程序l
第16章 没有银弹-软件工程中的根本和次要问题
摘要l
介绍l
是否一定那么困难呢？-根本困难l
以往解决次要困难的一些突破l
银弹的希望l
针对概念上根本问题的颇具前途的方法l
第17章 再论"没有银弹"
人狼和其他恐怖传说l
存在着银弹-就在这里！l
含糊的表达将会导致误解l
Harel的分析l
Jones的观点-质量带来生产率l
那么，生产率的情形如何l
面向对象编程-这颗铜质子弹可以吗l
重用的情况怎样l
学习大量的词汇-对软件重用的一个可预见，但还没有被预言的问题l
子弹的本质-形势没有发生改变l
第18章 《人月神话》的观点：是与非
第1章 焦油坑l
第2章 人月神话l
第3章 外科手术队伍l
第4章 贵族专制、民主政治和系统设计l
第5章 画蛇添足l
第6章 贯彻执行l
第7章 为什么巴别塔会失败l
第8章 胸有成竹l
第9章 削足适履l
第10章 提纲挈领l
第11章 未雨绸缪l
第12章 干将莫邪l
第13章 整体部分l
第14章 祸起萧墙l
第15章 另外一面l
第1版结束语l
第19章 20年后的《人月神话》
为什么要出版20周年纪念版本l
核心观点-概念完整性和结构师l
开发第二个系统所引起的后果-盲目的功能和频率猜测l
图形界面的成功l
没有构建舍弃原型-瀑布模型是错误的！l
增量开发模型更佳-渐进的精化l
关于信息隐藏，Parnas是正确的，我是错误的l
人月到底有多少神话色彩？-Boehm的模型和数据l
人就是一切（或者说，几乎是一切）l
放弃权利的力量l
更令人惊讶的新事物是什么？-数百万的计算机l
全新的软件产业-塑料薄膜包装的成品软件l
买来开发-使用塑料包装的成品软件包作为构件l
软件工程的状态和未来l
结束语：令人向往、激动人心和充满乐趣的50年
注解与参考文献
Some books are like an annuity, for both reader and author: they keep paying dividends, year after year. That certainly is the case with The Mythical Man-Month, though I didn't really appreciate it fully until I got a call from Professor Brooks in 1994.
The reason he was calling, he said, was that his publisher had asked him to update his book, which had first been published in 1975. I expressed a wee bit of jealous envy at the news, for my publisher has certainly never called me about updating a book approaching its 20th anniversary. Indeed, I even expressed the opinion that such ancient books would be considered irrelevant by the current generation of software engineers, and thus wouldn't be selling any copies. "Oh, no," replied Professor Brooks. "The Mythical Man-Month has been selling a steady 10,000 copies a year, all along."
More jealousy, more envy, and a sudden realization that what we have here really is like an annuity. I 'm happy to report that I've re-read the 1975 edition at least four times since its publication, and after Brooks' call, I took it down from the shelf and read it again. But this time, it was for a particular purpose: the real reason for his call, Professor Brooks had told me, was to find out if anything significant had happened in the computer field since the book had been published in 1975.
I must have sounded rather baffled by such a question, and Brooks went on to tell me that he had basically "dropped out" of the software engineering community, and had devoted most of his professional energies to teaching and research in the field of virtual reality. So, in preparation for a re-publication of his book, he wanted to know: what has changed, and what hasn't? Which of the premises in the original book turned out to be right, which ones were wrong, and which ones were irrelevant?
Of course, I wasn't the only person he contacted for this kind of information; several of my colleagues, and numerous gurus, authors, consultants, and "movers and shakers" in the industry were asked to respond to this question ... which we all did, quite happily. And, as you might expect, our inputs were processed, analyzed, filtered, and synthesized by Professor Brooks into a marvelous new edition that is truly a national treasure.
The original material is still there, but now there are four additional chapters, which reflect Professors Brooks' reflection on his original ideas and his reactions to the feedback he received from several of us. The first of the new chapters consists of a cogent condensation of the main themes in the original book, including what may well be regarded as its central argument: that large programming projects suffer management problems that are qualitatively different than small ones because of the division of labor; that the conceptual integrity of the software product is thus critical; and that it is difficult but possible to achieve this conceptual integrity. The second chapter summarizes Brooks' view of these themes a generation later, and the third chapter is a reprint of his classic 1986 paper, "No Silver Bullet," which first appeared in IEEE Software. The last of the new chapters is a reflection on Brooks' 1986 assertion that "there will be no silver bullet within ten years."
Young software engineers, penurious graduate students, and lazy software veterans often ask me to identify the best software book of all time. "If I were stuck on a desert island with only one computer book," they ask, "which one should it be?" It's a ridiculous question, but people insist on an answer. If indeed you should be banished to such an island (or if you decide to disappear to such a place in order to escape the dreaded Year-2000 software collapse!), The Mythical Man-Month is the book to take with you.
没有评论:
发表评论