The Super Fun Kids' Graphic Novel Sale

Special Offers see all

Enter to WIN a $100 Credit

Subscribe to
for a chance to win.
Privacy Policy

Visit our stores

    Recently Viewed clear list

    Original Essays | September 23, 2015

    Bryan Doerries: IMG Using Greek Tragedies to Comfort the Afflicted and Afflict the Comfortable

    In ancient Athens, during the fifth century BC, military service was required of all citizens. To be a citizen meant being a soldier, and vice... Continue »
    1. $18.87 Sale Hardcover add to wish list


On Order

New Trade Paper
Currently out of stock.
Add to Wishlist
available for shipping or prepaid pickup only
Qty Store Section
- Local Warehouse General- General

Facts and Fallacies of Software Engineering


Facts and Fallacies of Software Engineering Cover


Synopses & Reviews

Publisher Comments:

The practice of building software is a “new kid on the block” technology. Though it may not seem this way for those who have been in the field for most of their careers, in the overall scheme of professions, software builders are relative “newbies.”

In the short history of the software field, a lot of facts have been identified, and a lot of fallacies promulgated. Those facts and fallacies are what this book is about.

There’s a problem with those facts–and, as you might imagine, those fallacies. Many of these fundamentally important facts are learned by a software engineer, but over the short lifespan of the software field, all too many of them have been forgotten. While reading Facts and Fallacies of Software Engineering , you may experience moments of “Oh, yes, I had forgotten that,” alongside some “Is that really true?” thoughts.

The author of this book doesn’t shy away from controversy. In fact, each of the facts and fallacies is accompanied by a discussion of whatever controversy envelops it. You may find yourself agreeing with a lot of the facts and fallacies, yet emotionally disturbed by a few of them! Whether you agree or disagree, you will learn why the author has been called “the premier curmudgeon of software practice.”

These facts and fallacies are fundamental to the software building field–forget or neglect them at your peril!

Book News Annotation:

With this book those who build and research software can rediscover fundamental facts, and a few fallacies, about management, the software development life cycle, quality, and software research. For each fact, there is a general discussion, then material on related controversies, and a list of recent and "ancient" (1970s and 1980s) sources of information. Glass has written many books on software engineering.
Annotation c. Book News, Inc., Portland, OR (


This title offers 55 facts (and ten fallacies) that explore why software projects fail or succeed. Each fact is supported by insightful discussion and detailed references. The book identifies many of the key problems hampering success in the field of software engineering.

About the Author

Robert Glass is the founder of Computing Trends. He has written more than a dozen books on software engineering and on the lessons of computing failures. Robert is trusted by many as a leading authority on software engineering, especially by those who read his columns in Communications of the ACM and IEEE Software. Robert also publishes a newsletter, The Software Practitioner, and speaks frequently at software engineering events.


Table of Contents



I. 55 FACTS.

Introduction. @CHAPTER 1. = About Management.


Fact 1. The most important factor in software work is the quality of the programmers.

Fact 2. The best programmers are up to 28 times better than the worst programmers.

Fact 3. Adding people to a late project makes it later.

Fact 4. The working environment has a profound impact on productivity and quality.

Tools and Techniques.

Fact 5. Hype (about tools and techniques) is the plague on the house of software.

Fact 6. New tools/techniques cause an initial loss of productivity/quality.

Fact 7. Software developers talk a lot about tools, but seldom use them.


Fact 8. One of the two most common causes of runaway projects is poor estimation.

Fact 9. Software estimation usually occurs at the wrong time.

Fact 10. Software estimation is usually done by the wrong people.

Fact 11. Software estimates are rarely corrected as the project proceeds.

Fact 12. It is not surprising that software estimates are bad. But we live and die by them anyway!

Fact 13. There is a disconnect between software management and their programmers.

Fact 14. The answer to a feasibility study is almost always “yes”.


Fact 15. Reuse-in-the-small is a well-solved problem.

Fact 16. Reuse-in-the-large remains a mostly unsolved problem.

Fact 17. Reuse-in-the-large works best for families of related systems.

Fact 18. Reusable components are three times as hard to build, and should be tried out in three settings.

Fact 19. Modification of reused code is particularly error-prone.

Fact 20. Design pattern reuse is one solution to the problems of code reuse.


Fact 21. For every 25 percent increase in problem complexity, there is a 100 percent increase in solution complexity.

Fact 22. Eighty percent of software work is intellectual. A fair amount of it is creative. Little of it is clerical.
2. About the Life Cycle.


Fact 23. One of the two most common causes of runaway projects is unstable requirements.

Fact 24. Requirements errors are the most expensive to fix during production.

Fact 25. Missing requirements are the hardest requirements errors to correct.


Fact 26. Explicit requirements “explode” as implicit (design) requirements for a solution evolve.

Fact 27. There is seldom one best design solution to a software problem.

Fact 28. Design is a complex, iterative process. Initial design solutions are usually wrong, and certainly not optimal.


Fact 29. Designer “primitives” (solutions they can readily code) rarely match programmer “primitives”.

Fact 30. COBOL is a very bad language, but all the others (for business applications) are so much worse.


Fact 31. Error-removal is the most time-consuming phase of the life cycle.


Fact 32. Software is usually tested at best at the 55-60 percent (branch) coverage level.

Fact 33. 100 percent coverage is still far from enough.

Fact 34. Test tools are essential, but many are rarely used.

Fact 35. Test automation rarely is. Most testing activities cannot be automated.

Fact 36. Programmer-created, built-in, debug code is an important supplement to testing tools.


Fact 37. Rigorous inspections can remove up to 90 percent of errors before the first test case is run.

Fact 38. But rigorous inspections should not replace testing.

Fact 39. Post-delivery reviews (some call them “retrospectives”) are important, and seldom performed.

Fact 40. Reviews are both technical and sociological, and both factors must be accommodated.


Fact 41. Maintenance typically consumes 40-80 percent of software costs. It is probably the most important life cycle phase of software.

Fact 42. Enhancements represent roughly 60 percent of maintenance costs.

Fact 43. Maintenance is a solution, not a problem.

Fact 44. Understanding the existing product is the most difficult task of maintenance.

Fact 45. Better methods lead to MORE maintenance, not less.
3. About Quality.


Fact 46. Quality IS: a collection of attributes.

Fact 47. Quality is NOT: user satisfaction, meeting requirements, achieving cost/schedule, or reliability.


Fact 48. There are errors that most programmers tend to make.

Fact 49. Errors tend to cluster.

Fact 50. There is no single best approach to software error removal.

Fact 51. Residual errors will always persist. The goal should be to minimize or eliminate severe errors.


Fact 52. Efficiency stems more from good design than good coding.

Fact 53. High-order-language code can be about 90 percent as efficient as comparable assembler code.

Fact 54. There are tradeoffs between size and time optimization.
4. About Research.

Fact 55. Many researchers advocate rather than investigate.


5. About Management.

Fallacy 1. You can't manage what you can't measure.

Fallacy 2. You can manage quality into a software product.


Fallacy 3. Programming can and should be egoless.

Tools and Techniques.

Fallacy 4. Tools and techniques: one size fits all.

Fallacy 5. Software needs more methodologies.


Fallacy 6. To estimate cost and schedule, first estimate lines of code.
About the Life Cycle.


Fallacy 7. Random test input is a good way to optimize testing.


Fallacy 8. “Given enough eyeballs, all bugs are shallow”.


Fallacy 9. The way to predict future maintenance cost and to make product replacement decisions is to look at past cost data.
7. About Education.

Fallacy 10. You teach people how to program by showing them how to write programs.

About the Author.

Index. 0321117425T09232002

Product Details

Glass, Robert L.
Addison-Wesley Professional
Boston, MA
Programming - General
Programming - Software Development
Software engineering
Miscellaneous Software
Software Development & Engineering - General
Software Engineering-General
Edition Description:
Trade paper
Agile Software Development
Series Volume:
Publication Date:
October 2002
Grade Level:
Professional and scholarly
9 x 7.2 x 0.6 in 372 gr

Other books you might like

  1. The Visual Display of Quantitative...
    Used Hardcover $20.00
  2. Inviting Disaster: Lessons from the... Used Trade Paper $6.50
  3. The Evolution of Useful Things: How... Used Trade Paper $6.50
  4. Contexts of Aging New Trade Paper $33.75
  5. The Wisdom of Crowds: Why the Many... Used Trade Paper $6.95
  6. Thinking in Java
    Used Trade Paper $36.00

Related Subjects

Computers and Internet » Computers Reference » General
Computers and Internet » Software Engineering » General
Computers and Internet » Software Engineering » Object Oriented Programming
Computers and Internet » Software Engineering » Project Management
Travel » General

Facts and Fallacies of Software Engineering New Trade Paper
0 stars - 0 reviews
$50.75 Backorder
Product details 224 pages Addison-Wesley Professional - English 9780321117427 Reviews:
"Synopsis" by , This title offers 55 facts (and ten fallacies) that explore why software projects fail or succeed. Each fact is supported by insightful discussion and detailed references. The book identifies many of the key problems hampering success in the field of software engineering.
  • back to top


Powell's City of Books is an independent bookstore in Portland, Oregon, that fills a whole city block with more than a million new, used, and out of print books. Shop those shelves — plus literally millions more books, DVDs, and gifts — here at