Editorial Review:
For over 20 years, Software Engineering: A Practitioner's Approach has been the best selling guide to software engineering for students and industry professionals alike. The sixth edition continues to lead the way in software engineering. A new Part 4 on Web Engineering presents a complete engineering approach for the analysis, design, and testing of Web Applications, increasingly important for today's students. Additionally, the UML coverage has been enhanced and signficantly increased in this new edition. The pedagogy has also been improved in the new edition to include sidebars. They provide information on relevant softare tools, specific work flow for specific kinds of projects, and additional information on various topics. Additionally, Pressman provides a running case study called "Safe Home" throughout the book, which provides the application of software engineering to an industry project. New additions to the book also include chapters on the Agile Process Models, Requirements Engineering, and Design Engineering. The book has been completely updated and contains hundreds of new references to software tools that address all important topics in the book. The ancillary material for the book includes an expansion of the case study, which illustrates it with UML diagrams. The On-Line Learning Center includes resources for both instructors and students such as checklists, 700 categorized web references, Powerpoints, a test bank, and a software engineering library-containing over 500 software engineering papers. TAKEAWY HERE IS THE FOLLOWING: 1. AGILE PROCESS METHODS ARE COVERED EARLY IN CH. 4 2. NEW PART ON WEB APPLICATIONS --5 CHAPTERS
Cached date: AWS Called=true
You may also be interested in these products:
These categories may also be of interest to you:
Customer Reviews
Average Customer Rating: 
Pressman, you are not helping me  2008-06-22
This book will bring you up to speed on all the buzz words for all the methodologies, but thats the extent of the book.
This book covers very little of actually process, how to analyze and existing process, how to setup a new process or improve a process. It actually does a very poor job of explaining what sofrware engineering is all about and leaves you feeling that is about writing documents, not about creating reliable, verifiable software.
Roger Pressman, thanks for Engineering Confusion! 2007-12-13
I used this book in my Grad class and I'm still confused. I don't know what to make of this book. On the one hand, I think the author tries to cover most of the important topics, but on the other, the book falls short in intellectual substance.
Problems at the end of each chapter are very time consuming, and in some cases cannot be answered at all. This makes me wonder if the author can answer any of those tough questions that he wants you to ponder.
If you're looking for a good SE textbook, don't buy this one. You will regret it!
There is nothing much in this text that's closely related to what the author is asking you to consider. His book is based on fluff, and lacks the important stuff; just a bunch of snippets.
You will get an "F".
This is by far the worst textbook I have ever read, and isn't worth $128 dollars.
Thanks for nothing Roger, but you deserve at least 1 star!
Worthy Tome  2007-10-16
This is a good book. I have several editions of this book, including a very early one. In my view, in looking for a thorough perspective of software engineering, there are two major routes: McConnell/Weigers series or one of the comprehensive volumes by Pressman or Sommerville. McConnell's books (Code Complete, Rapid Software Development, and Software Estimation) and Weigers (Software Requirements) are each highly detailed. Hence, four-plus books. Pressman encapsulates (sic) the whole shebang into one big comprehensive volume. Not as detailed as those Microsoft Press authors, but that's not a drawback. If you've been practicing for a long time and you're the project manager, sometimes a substantive overview is what you need, not minute details. You're not living in the deep details anyway, your engineers are. Plus, the coverage of the more advanced development technologies, like formal methods, are very good and not included in the Microsoft Press books. Bottom line: if you're a technology director or project manager and want the big picture (in one place), get Pressman. If you're a systems analyst or software engineer and want the larger view, get McConnell and Weigers. (I have not read the Sommerville text, but from the table of contents there's a chapter on security which the other books only cover lightly.)
Great for studying for the CSDP Exam  2007-09-17
I had the 4th edition of the book back in college. When I started studying for the CSDP (Certified Software Development Professional) Exam, I ordered the 6th edition. The 6th edition is a huge improvement over the 4th.
This book covers just about everything you need to know on the subject of software engineering. Great book, great reading. Applying the concepts on the job will help out tremendously in your career.
Excellent Source Material 2007-03-01
I'm not a student. I am software development manager and have over 20 years of real-world experience developing sophisticated banking and financial applications. I have one of the original first addition books, and I have to say that this book was critical to my learning software engineering principles. The criticism of this book are unfounded in my opinion. This book contains the critical elements to implement SE principles.
The complaints seem to be from students and they seem to think it is a poor text book. Well, that's probably a good sign, as good text books are usually worthless for real world examples, and books that give you worthwhile information aren't usually good text books.
If you look through all the 5 star reviews, they are from Software Engineers working in the field. If you look at all the 1 star reviews, they are all from students who, frankly don't know what really is important and what isn't when it comes to developing quality software. (I know I didn't when i was a student). That alone gives speaks volumes about the book.
Some said that Code Complete is a better book. Where do you think the authors of Code Complete got their material? This book is first published 15 years before Code Complete. Code Complete is a good book, but doesn't explain the "why" of things, whereas this book does. Studying this book will give you the "why" on certain principles so you can enact them to whatever situation you are in. It is not an "ABC" book on how to do "XYZ."
The theories and examples on the programmer productivity were very valuable to me, and I have saved me countless hours and money on developers time because I learned how to maximize programmer productivity. This book is the framework on how to development high-quality software. I can speak from experience that the software I've been respopnsible for developing, using the priniciples I learned from this book, has been excellent. The software failure rates I have experienced are far lower than industry averages. I have some applications that have run for many years without any software failures. It can be done, but this doesn't garantee your success. This book shows you the blueprint. You still need experienced developers to be able to create high-quality code, but only by following the principles laid out in the book.
Perhaps if all you students had to see all the poorly written software in use in the world, you would appreciate this book more. This book is well worth it the price. If you plan on having anything to do with software development, keep this book, and don't sell back to a book store. I ordered the latest version and read it, and Pressman has done a good job in keeping up with the latest in software engineering. With out a doubt, the book is worth the price. My copy has paid for itself many times over.
|
|
