thisisme-zhining

Thursday, September 23, 2010

Download The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)

 thisisme-zhining Thursday, September 23, 2010

Download The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)

Be concentrate on just what you truly want to acquire. Schedule that currently becomes your focus needs to be found sooner. Nevertheless, what kind of book that you really wish to check out. Have you found it? If confuse constantly disturbs you, we will certainly offer you a brand-new recommended publication to check out. The Mythical Man-Month: Essays On Software Engineering, Anniversary Edition (2nd Edition) is probably you will certainly require a lot. Love this book, like the lesson, as well as enjoy the impact.

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)


The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)


Download The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)

After as long time no see and locate a superb book, currently we are coming. Using the exceptional books become our works on a daily basis. We will share whatever about the kindness and finest of guides. This is not only guides from this country. The over boarded book collections are additionally numerous to seek for. You won't have to seek for various other places; this website is the very best readied to locate all book collections.

Checking out tends to be very dull activity to do; some individuals might claim concerning it. But, reviewing really will provide the viewers numerous benefits. It's not only the lesson or understanding; much home entertainment can be likewise acquired from reading book. Yeah, there are several sort of books as well as some of them are the fictions. The book to read will certainly certainly depend on how you wish to get the impression of guide. For this reason, we share The Mythical Man-Month: Essays On Software Engineering, Anniversary Edition (2nd Edition) as one of the product to review. It has to be among referred books in this suggested web site.

When you have decided to review it, you have made a decision to take one action to resolve the obstacle. It can be done by then reviewing it. Reading The Mythical Man-Month: Essays On Software Engineering, Anniversary Edition (2nd Edition) can be a male choice to satisfy your spare times in daily activity. It will certainly be better for establishing the soft file of this publication in your gizmo so you could enjoy reviewing it at any time and also any kind of were.

Associated with this problem, you will certainly additionally learn May books that can be resources for your life. It is not only this sort of subject; you could likewise locate others as good as this book to offer. Naturally, what we give is exactly what finest in this world. So, you may not be worried to pick The Mythical Man-Month: Essays On Software Engineering, Anniversary Edition (2nd Edition) as one of motivating reading book. Currently, regardless of what to do, you have to get this publication and obtain complying with the system to be much easier as well as quicker.

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)

Amazon.com Review

The classic book on the human elements of software engineering. Software tools and development environments may have changed in the 21 years since the first edition of this book, but the peculiarly nonlinear economies of scale in collaborative work and the nature of individuals and groups has not changed an epsilon. If you write code or depend upon those who do, get this book as soon as possible -- from Amazon.com Books, your library, or anyone else. You (and/or your colleagues) will be forever grateful. Very Highest Recommendation.

Read more

From the Inside Flap

To my surprise and delight, The Mythical Man-Month continues to be popular after twenty years. Over 250,000 copies are in print. People often ask which of the opinions and recommendations set forth in 1975 I still hold, and which have changed, and how. Whereas I have from time to time addressed that question in lectures, I have long wanted to essay it in writing. Peter Gordon, now a Publishing Partner at Addison-Wesley, has been working with me patiently and helpfully since 1980. He proposed that we prepare an Anniversary Edition. We decided not to revise the original, but to reprint it untouched (except for trivial corrections) and to augment it with more current thoughts. Chapter 16 reprints "No Silver Bullet: Essence and Accidents of Software Engineering," a 1986 IFIPS paper that grew out of my experience chairing a Defense Science Board study on military software. My co-authors of that study, and our executive secretary, Robert L. Patrick, were invaluable in bringing me back into touch with real-world large software projects. The paper was reprinted in 1987 in the IEEE Computer magazine, which gave it wide circulation. "No Silver Bullet" proved provocative. It predicted that a decade would not see any programming technique which would by itself bring an order-of-magnitude improvement in software productivity. The decade has a year to run; my prediction seems safe. "NSB" has stimulated more and more spirited discussion in the literature than has The Mythical Man-Month. Chapter 17, therefore, comments on some of the published critique and updates the opinions set forth in 1986. In preparing my retrospective and update of The Mythical Man-Month, I was struck by how few of the propositions asserted in it have been critiqued, proven, or disproven by ongoing software engineering research and experience. It proved useful to me now to catalog those propositions in raw form, stripped of supporting arguments and data. In hopes that these bald statements will invite arguments and facts to prove, disprove, update, or refine those propositions, I have included this outline as Chapter 18. Chapter 19 is the updating essay itself. The reader should be warned that the new opinions are not nearly so well informed by experience in the trenches as the original book was. I have been at work in a university, not industry, and on small-scale projects, not large ones. Since 1986, I have only taught software engineering, not done research in it at all. My research has rather been on virtual reality and its applications. In preparing this retrospective, I have sought the current views of friends who are indeed at work in software engineering. For a wonderful willingness to share views, to comment thoughtfully on drafts, and to re-educate me, I am indebted to Barry Boehm, Ken Brooks, Dick Case, James Coggins, Tom DeMarco, Jim McCarthy, David Parnas, Earl Wheeler, and Edward Yourdon. Fay Ward has superbly handled the technical production of the new chapters. I thank Gordon Bell, Bruce Buchanan, Rick Hayes-Roth, my colleagues on the Defense Science Board Task Force on Military Software, and, most especially, David Parnas for their insights and stimulating ideas for, and Rebekah Bierly for technical production of, the paper printed here as Chapter 16. Analyzing the software problem into the categories of essence and accident was inspired by Nancy Greenwood Brooks, who used such analysis in a paper on Suzuki violin pedagogy. Addison-Wesley's house custom did not permit me to acknowledge in the 1975 Preface the key roles played by their staff. Two persons' contributions should be especially cited: Norman Stanton, then Executive Editor, and Herbert Boes, then Art Director. Boes developed the elegant style, which one reviewer especially cited: "wide margins, and imaginative use of typeface and layout." More important, he also made the crucial recommendation that every chapter have an opening picture. (I had only the Tar Pit and Rheims Cathedral at the time.) Finding the pictures occasioned an extra year's work for me, but I am eternally grateful for the counsel. Deo soli gloria or Soli Deo Gloria -- To God alone be the glory. Chapel Hill, N.C., F.0201835959P04062001

Read more

See all Editorial Reviews

Product details

Paperback: 336 pages

Publisher: Addison-Wesley Professional; Anniversary edition (August 12, 1995)

Language: English

ISBN-10: 9780201835953

ISBN-13: 978-0201835953

ASIN: 0201835959

Product Dimensions:

6.1 x 1 x 9.2 inches

Shipping Weight: 13.6 ounces (View shipping rates and policies)

Average Customer Review:

4.4 out of 5 stars

300 customer reviews

Amazon Best Sellers Rank:

#7,188 in Books (See Top 100 in Books)

I read this book twenty years or so ago and I have given away several copies of it to others who manage groups of professionals engaged in scientific research and analyses. Although Dr. Brooks writes specifically about his experiences with software development, I feel that a reader could easily replace references to programming or software with the more generic "project" to imagine how Brooks' experiences might apply to their own work. The Mythical Man-Month is a very thoughtful treatment on the structuring of work groups and of the importance of communication within and among teams working on projects.

I love this book. I think it came out before Agile & Scrum took off. However there are so many wonderful concepts about organizing large technically complex projects. So much of what he talks about is just good project planning--forget software development. I am in the chapter now where they are discussing how it is better to have a project which adheres to the original well planned form for a project--rather than sloppily stringing a bunch of updated ideas together with the original base. It is a philosophy which can be related to everyday life--not just software development.

A fantastic read; the examples are a little dated but the message is exemplary and relevant. Frankly, this might be the most excellent piece of software engineering literature in existence.It is dense, every sentence is necessary and relevant. The allusions, metaphors, and examples all help to paint and SHOW not TELL the author's ideas.A cross between literary masterpiece and dialogue about software engineering, this novel will stand the test of time.

I am a retired computer programmer, 86 years old, a career therein dating from a chance occurrence in 1956, and having been laid off from U.S.Defense Dept. work finally in 1987, when the Cold War ended. I was actively involved in working with the big computer at a Navy base, and involved in choosing a replacement for IBM 7090, so I heard a lot of feedback from aerospace contractors who got the System 360 about which the author is writing. After our assessment of available machines, we chose not to go on with IBM, but got another vendor. I have heard about this book intermittently through the years, always intending to acquire it. When I lately found out about the 1995 edition, I acquired it and read it with great interest. A very good exposition of the nuts and bolts that exist behind large projects. From my experience, as employed by the U.S. government and then by a contractor to it, I concur with all his conclusions, and welcome the 1995 additional material in which he clarifies some matters. Good reading and good advice. Must have!

=== Excellent insights into software ===IMHO, Brooks has distilled fundamental truths; you might find his ideas slightly outdated; but all will agree Brooks offers at least excellent insights. To list but a few: build times determine programmer work cycle; agreement on high-level goals is essential; dev tools make a huge difference; visualizing code is a hard problem; programmers are optimists.=== Superbly edited ===If you've a background in editing (developmental down to line), you will be impressed by this text. "Perfection is achieved, "said Saint-Exupery, "when there's nothing left to take away"; and that is absolutely the case here. Every point is pertinent to the thesis, every sentence is necessary, every phrase concise. (I cannot say the same of Brooks's follow-on book, "Design of Design".)=== Classy ===Brooks was the project manager for the OS/300, a $5B endeavor that IBM bet its future on, an engineering effort of the highest magnitude, and a spectacular success. But whenever he mentions an aspect or feature where he feels OS/300 excelled, he always gives complete credit to whomever designed that aspect or implemented that feature; and whenever he mentions an area where he feels OS/300 fell short, he takes complete personal responsibility for the shortcoming.

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) PDF
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) EPub
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) Doc
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) iBooks
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) rtf
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) Mobipocket
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) Kindle

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) PDF

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) PDF

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) PDF
The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) PDF

  Ebooks

No comments:

Post a Comment

Newer Post Older Post Home
Subscribe to: Post Comments (Atom)

Updates

Follow

Get To Me!

What Is Lorem Ipsum?

Why It Is Useful?

Labels

  • Ebooks
Copyright © Way2Themes. All Rights Reserved. Blogger Templates