Blog this item

人月神话

(影印版)

By 布鲁克斯

(100)

| Others | 9787508313030

Like 人月神话?
Join aNobii to see if your friends read it, and discover similar books!

Book Description

　　在软件领域中，很少能有像《人月神话》一样具有深远影响力和畅销不衰的著作。Brooks博士为人们管理复杂项目提供了最具洞察力的见解，既有很多发人深省的观点，又有大量软件工程的实践。本书内容来自Brooks博士在IBM公司 System/360家族和OS/360中的项目管理经验。在本书第一次出版20年后的今天，Brooks博士重新审视了他原先的观点，啬了一些新的想法和建议。既方便了熟悉原有内容的人们，又方便了第一次阅读它的读者。　　软件界的《圣经》——《The Mythical MAN-MONTH》（人月神话）在出版并畅销了20余年后，终于登陆中国，由中国电力出版社引进出版的英文原版影印版上市。　　　　该书原为“IBM 360系统之父”Fred Brooks的一本随笔集，是他为IBM开发OS/360系统的经验总结。但由于该书为人们管理复杂项目提供了极具洞察力的见解，发人深省的观点，以及大量的软件工程实践，一经出版便被广泛传播。在这部注重实效、条理明晰的书中，Brooks剖析了许多工程管理的“神话”，这些神话来自他在软件工业中的亲身实践。他抨击了在项目中增加人手可以促进项目完成的幻想。Brooks用实例、幽默与严密的逻辑，展示了这些神话实际上如何给软件项目带来灾难并导致延迟。　　　　在此书中，Brooks覆盖了成功完成一个主要软件项目必须做的所有因素，同时，在书的各部分中，他给出了一致的软件工程与项目管理的理论基础。可以说这是一本主要的正确汇集工程师需要的关于大型软件项目开发知识的书，书中相关知识来自于作者对已完成项目的看法，是作者数十年的项目管理经验的总结。这些篇幅每篇都值得一读，它们介绍了软件开发项目中的每一个过程，让我们可以轻易地从这里了解软件工程这一行业。　　　　该书原版的语言流畅通俗，经常以极为浅显的叙述讲解艰深晦涩的原理，作者驾驭文字的能力令人击节赞叹。　　　　相信通过阅读英文原版的《The Mythical MAN-MONTH》，可以很轻易地抓住问题核心，不会产生歧义或者理解错误，因为，你所阅读的正是Brooks当年亲笔写下来的。

5 Reviews

2 people find this helpful

Certainly one of the classics of software project management, this book first appeared a quarter of a century ago, when Fred Brooks tried to run one of the first very large scale software engineering projects (the OS/360 operating system at IBM) and became the first person to describe how radically ... (continue)

Certainly one of the classics of software project management, this book first appeared a quarter of a century ago, when Fred Brooks tried to run one of the first very large scale software engineering projects (the OS/360 operating system at IBM) and became the first person to describe how radically different software is from other types of engineering. This book is most famous for discovering the principle that adding more programmers to an already-late project makes it later, but that's only the tip of the iceberg. Understanding this book is a prerequisite for thinking correctly about managing software teams.

Is this helpful?

J.S. (testing) said on Oct 20, 2005 about the Paperback edition | Add your feedback

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) by Frederick P. Brooks (1995)

Is this helpful?

Reinhard said on Oct 4, 2010 about the Paperback edition | Add your feedback

One of the best in software planning

... when developing software did not means a collage of what can be found in Internet ...
... when developing software means think what you are doing ...
... when developing software was a "state of the art" process ...
... NOT NOW.
(sorry for my horrible English)

Is this helpful?

Albertuan said on Jun 8, 2008 about the Paperback edition | Add your feedback

Beautifully written, terribly true. Still true after 40 years.
A must read for those work under large software company, or those interested in software engineering.

Is this helpful?

小影 said on Apr 2, 2008 about the Paperback edition | Add your feedback

*** This comment contains spoilers! ***

This book is about software engineering. Some points to note:
(1) The surgical team: I buy this idea also. Being a few minds working on a project is the right way to get out of the hell of endless discussion over coding and design. The role of the lead programmer and an assistance is good. Bu ... (continue)

This book is about software engineering. Some points to note:
(1) The surgical team: I buy this idea also. Being a few minds working on a project is the right way to get out of the hell of endless discussion over coding and design. The role of the lead programmer and an assistance is good. But, the role is to lead, but not to dominate in every discussion making.
(2) The complexity of a software is the essence. I agree with this point. The software is one of the way to realize abstract idea into concrete structure(s). It is inevitably the reflection of one's mind. Unless the software is doing dull things, the complexity is the core, not the side-effects or ill-features. I think breaking down such a complexity is futile, instead we need to model as a complexity. To model the complexity is a great challenge, but not beyond today's scope. I hope that one unify way to model software will be out soon.
(3) The great minds are needed. As a educator, I don't buy this idea. But, from an industrial perspective, the great minds really work out effectively, with orders of improvement.
(5) Top-down design. I experienced myself. Without a concrete design and blindly developing "something" from bottom-up is definitely not the way out. It turns out that a project developing using a bottom-up approach would end up with many modules being difficult to communicate.
I end this writing here. But, it is not all the things about this book. It is worth reading, as a matter of fact. It is a valuable book for software managers, and team leaders, but not university students. It is because you can only know how to appreciate this book with a handful of experience.

Is this helpful?

Tsz-yeung Wong said on Jan 15, 2008 about the Paperback edition | Add your feedback