Rating: 
Summary: hmmm this one is lots cheaper in the UK...
Review: It seems that the US is getting ripped off here - which makes a change - if you want this book - order it from the UK - where it costs a little over £20 - and whilst its the "European Edition" still appears to cover the same scope and material...
Rating: 
Summary: A Vague book for a vague subject
Review: Its a typical mediocre college book. Nothing particularly insightful or interesting about software engineering here. Just a poorly constructed collection of chapters that vaguely map out a software engineering paradigm. Entity relationships?? Dataflow?? Hello?? Nothing like that here.
Rating: 
Summary: 3rd edition was excellent, but what happened to the price??
Review: Pressman gives an excellent encyclopedic coverage of all the essentials of Software Engineering. I would say every s/w company should have a couple of copies for reference, and every s/w engineer should study it.
However, I bought this book (3rd edition) for a list price of $42.50 in 1993. Now it lists for nearly double that (same edition)! This after 4 years of 3% inflation!? And of course the 4th edition is $10 more... why?
As an aside, I think this book would make an excellent companion to Steve McConnell's "Rapid Development": they cover many of the same topics but in very different ways.
Rating: 
Summary: A Book Aimed At the Top of the Totem Pole
Review: Pressman's text is squarely directed at the process of software development. He does not get bogged in details of a particular implementation methodology and thus provides a broadbased view of software process. It proposes tradition IT valuation principles with a sprinkling of more common management metrics.
Rating:
Summary: comprehensive coverage of software engineering
Review: The author achieves a commendable balance between breadth and depth. None of the topics are discussed at a superficial level. In addition, this text is written in a highly readable style. External sources are frequently referenced, quoted, and summarized. There is an emphasis on software metrics in chapter 5 and chapter 18. A section on structured methods is contained in chapters 11-14. A section on object-oriented methods is contained in chapters 19-23. Excellent introduction to advanced topics such as formal methods, reengineering, client/server, and computer-aided software engineering. Breaks CASE tools into 23 categories. Each chapter includes a set of problems and points to ponder.
Rating: 
Summary: Sorry Excuse for a textbook!
Review: The author of this book uses terminology that goes over your head. You get caught up in the vocabulary and forget what you are reading. This is more like a 888 page research paper (A paragraph, then a paragraph of quoting, then a few more paragraphs, and a bulleted list from someone else) Excuse me, write the book USING YOUR OWN WORDS, insead of quoting everyone else!
Rating:
Summary: Very Dry, lacks major examples
Review: The book is extremely dry and is very wordy. There is a lot of information present and the subject is rather dry to begin with, but this book still falls short. It also lacks examples of major documentation (requirements definition, requirements specifcation, etc.)
Rating:
Summary: Very Dry, lacks major examples
Review: The book is extremely dry and is very wordy. There is a lot of information present and the subject is rather dry to begin with, but this book still falls short. It also lacks examples of major documentation (requirements definition, requirements specifcation, etc.)
Rating:
Summary: Do not buy this book
Review: The book recommends itself to the last year undergraduate and first year graduate student. If you are looking for a tourist view of Software Engineering buy this book. It does not stand on its own, it briefly quotes other books. After reading selections from several chapters repeatedly I find it hard to believe anything useful can be gathered from it.
Rating:
Summary: Get it, read it, do it
Review: The range in scores for this book reflects the difference between the professional software engineer concerned about quality, and the hacker. Documentation is essential to gaining quality. This book earns it's position on many different organizations' list of "must have" books for the software engineer. Get it, read it, and follow it, and you're projects will have a chance of succeeding.
| 
