Rating: 
Summary: Difficult to follow
Review: I found this book to be very difficult to follow. I realize that software engineering is not necessarily a thrilling topic, but I found this book to be far slower reading than most textbooks. I had trouble following the author at points, and I especially disliked the questions at the end of the chapters. They often used different terms than those discussed in the chapters, which made answering them difficult. Also, many questions asked you to put together an example of some technique discussed in the book, but the example in the book was vague and didn't give enough information for you to be able to complete the exercise. I really haven't gotten anything out of this textbook at all.
Rating: 
Summary: I love/Hate this Book (but give it 5 stars)
Review: I got this book for my PMP CAQ-ITS test. The book is well written, but gets so technical, it turns your mind to jelly in no time. It is the most complete reference on software engineering I have seen in 30 years in the IT profession. It leaves no stone unturned. The bad news it that it leaves no stone unturned. The book incorporates a LOT of best practices that should be followed everywhere (but never are).I struggled with this book, but I can honestly say that this is the first book I will pick up if I am ever assigned to a software development project.
Rating:
Summary: Thorough and Practical
Review: I really enjoyed this book. I had the added benefit of being a student in this author's class. Her book is simple enough reading that an undergraduate can understand it, yet, at the same time it is in-depth enough to be usefull to professionals. There is considerable information on how to analyze and evaluate evidence. The book also benefits from a clear writing style. Thankfully, despite the fact that this book was written in a "user-friendly" manner, the irritating attempts at humor that waste space in otherwise good books was absent in this book. I liked the book.
Rating:
Summary: Buying this book is WASTING money.
Review: If you HAVE to read this book, you'll know what I mean. The first time I read this book, I hated it... Boring, and one reviewer is right, it covers EVERYTHING under the sun about S/E. Now, after about two years or so, I keep finding myself refering to this book over and over again. I am liking more now that I see how and where to use the topics that it talks about. 4 star, b/c this book could have been written better. First time around was very boring.
Rating: 
Summary: Good book - not at first though
Review: If you HAVE to read this book, you'll know what I mean. The first time I read this book, I hated it... Boring, and one reviewer is right, it covers EVERYTHING under the sun about S/E. Now, after about two years or so, I keep finding myself refering to this book over and over again. I am liking more now that I see how and where to use the topics that it talks about. 4 star, b/c this book could have been written better. First time around was very boring.
Rating: 
Summary: Should be better
Review: It is quite complete. The main issues are all there. And it isn't too difficult to follow. But the structure does wobble a bit. It also fails to galvanize the reader. It is a bit of a sleeper since it just presents one technique after the other. No sparkle, inflection nor much motivation. Right now I'm halfway through (chapter 6) and I will finish it, cause the subject matter is all there. But I wish I had another book to choose from.
Rating:
Summary: Well-conceived introductory text
Review: Organizes chapters according to a traditional software development sequence: introduction, process and life cycle, planning and managing, requirements, design, implementation, testing, delivery, maintenance, evaluation, and improvements. Includes extensive references to research papers and standard texts. An information system (scheduling television advertising) and real-time system (Ariane-5 rocket) example are threaded through each chapter. Compares effort estimation models including COCOMO II and neural-networks alternatives. Discusses architectural styles and strategies. Includes an excellent chapter on software maintenance and software rejuvenation. Explains system types such as S, P, and E. Analyzes methods for evaluating the results of software engineering research. Presents research on policy trade-offs such as "adjusting the workforce to keep the project on schedule" vs. "extending the schedule as needed." The coverage of specific structured and object-oriented methods is minimized.
Rating:
Summary: Most boring textbook I've ever read
Review: Reading this book is really a torture. The author tries her best to beat around the bush and use complex wording to make a very simple point become a very convoluted "theory", or patiently explain each and every tiny common sense no matter how obvious that is. Plus, in a lot of places in this book, the conclusion drawn from the analysis does not appear to follow the logic. Moreover, it is very disorganized too, not only from one section to another, even from the beginning of a paragraph to the end, you'll be like "I thought we were talking about something else ... ". The writing is so dry that you'll be so easy to doze off. Although Software Engineering is probably not as fun as EJB, do we really need to make an already boring subject less fun to read? Please.
Rating:
Summary: Covers all the essentials of Software Engineering
Review: Shari Pfleeger knows what she is talking about. I read this book for a distance learning course and found it entirely possible to grasp the concepts of software engineering, although Pfleeger presents a lot of complex mathematical models and programming examples (as well as many easier models). The book requires some re-reading to fully grasp. Pfleeger uses a lot of interesting drawings, tables, charts, and diagrams to illustrate concepts. I found this useful in most circumstances. Pfleeger's writing style is fairly straightforward and I didn't have any difficulty understanding her grammar. There were no syntax errors that I noticed in the book. The book covers a lot of material including (from the table of contents):
1. the software development life cycle
2. project planning
3. capturing the requirements
4. designing the system
5. object oriented programming concepts
6. writing the programs
7. testing the programs
8. testing the system
9. delivering the system
10. maintaining the system
11. evaluating products, processes and resources
12. improving predictions, products, processes, and resources, and
13. the future of software engineering The only drawback to this book is perhaps that Pfleeger goes waaaay into detail on EVERYTHING. For some people this is great (including me). This book is for professionals and for people that are very interested in software engineering (not beginners, or the casual reader) and can wade through a lot of (oftentimes boring) material.
Rating:
Summary: dennis
Review: Thanks for this information you are doing a great jo
| 
