Rating: 
Summary: Software Engineering : A Practitioner's Approach
Review: i this book very much but in the book they have some questions i dont understand much ..if anyone know where solution in this book please let me know
Rating: 
Summary: Underwhelming book
Review: I used this text in a software engineering course as an undergraduate. I think the problems with this book are two-fold. First, Pressman tries to cover too much and ends up covering nothing very well. The chapters on client/server architecture, realtime software engineering, and documentation are particularly weak. In many places, Pressman "discusses" an SE topic by citing a bunch of articles and books, thus avoiding the troubling task of having to actually present content. The second main problem with this book is that it is addressed to practitioners, as the subtitle suggests, not students. Pressman almost never addresses questions that start with "why", focusing instead on questions that start with "how". He answers questions like "How do I do a requirements analysis", not "why should I worry about requirements?" or "Why should I prefer cleanroom methods over other alternatives?" These are questions that students will want answers to, but software professionals probably already understand at least intuitively. If you are a professional developer, then you might find Pressman to be a moderately useful reference. If you are a student, forget it. Find another book. If you are doing anything OO-centric, run immediately and buy "Design Patterns" by Gamma, Helm, Johnson, Vlissides. If you are working on some other type of project, like a web or database project, I am sure you can find a better book than Pressman. The verdict: Unless you like shelling out money for mediocre books, avoid this one.
Rating:
Summary: Underwhelming book
Review: I used this text in a software engineering course as an undergraduate. I think the problems with this book are two-fold. First, Pressman tries to cover too much and ends up covering nothing very well. The chapters on client/server architecture, realtime software engineering, and documentation are particularly weak. In many places, Pressman "discusses" an SE topic by citing a bunch of articles and books, thus avoiding the troubling task of having to actually present content. The second main problem with this book is that it is addressed to practitioners, as the subtitle suggests, not students. Pressman almost never addresses questions that start with "why", focusing instead on questions that start with "how". He answers questions like "How do I do a requirements analysis", not "why should I worry about requirements?" or "Why should I prefer cleanroom methods over other alternatives?" These are questions that students will want answers to, but software professionals probably already understand at least intuitively. If you are a professional developer, then you might find Pressman to be a moderately useful reference. If you are a student, forget it. Find another book. If you are doing anything OO-centric, run immediately and buy "Design Patterns" by Gamma, Helm, Johnson, Vlissides. If you are working on some other type of project, like a web or database project, I am sure you can find a better book than Pressman. The verdict: Unless you like shelling out money for mediocre books, avoid this one.
Rating: 
Summary: Horrible piece of work
Review: I was going to reserve judgement on this book until I had completed the course that it was being used in. However, I feel compelled now to state that this book is one of the most poorly written books I've ever had the misfortune to be required to read. In *every* chapter I've read so far, I've found at least one, often several, spelling, grammatical, or technical errors. So far the most damning is Chapter 20, where, constantly, Pressman cites the work of "Rambaugh", such as the book "Object-Oriented Modeling and Design". Maybe if Pressman was more concerned with writing a useful text than he is in writing one to bring in more money, he'd have actually looked at the list of authors for "OOMD" and noted the correct spelling of James Rumbaugh's name.Save yourself the money and get another book.
Rating:
Summary: No evaluation and analysis
Review: I'm a PhD candidate in Software Engineering, and I have tried to use this text in several occasions both as a student and as a teaching assistant. I have always been disappointed. My largest problem is that the text attempts to do too much, and ends up doing nothing well. There is no analysis of the strengths and weaknesses of different methods. Why/When should I use OO instead of structured methods? Furthermore, since the book covers so many topics in a limited number of pages, there simply cannot be enough information in order to apply any of them. If you want to try to analyze, design, build and test even a toy problem, there are inevitably a raft of issues that this book does not address. This book does not provide a student a firm grasp of _any_ part of the software engineering process.
Rating:
Summary: Pretty bad textbook.
Review: I'm a software developer with almost 15 years experience. I'm taking a M.S. level class that uses this book, and I have to say that it's a horrible textbook. Although it imparts some useful knowledge, you will constantly find yourself looking for supplemental information on the Internet. There is not enough information supplied in the textbook to do the assigned homework! Explanations are sometimes jumbled and incoherent. Examples are extremely sparse--if you're lucky, you'll get 1 example of a particular topic, but most of the time you get none. I am very disappointed with this book. I can't imagine how this book has become so prominent in the software engineering world. Only in academia, I guess...
Rating:
Summary: verbose
Review: i'm using this book for a graduate software engineering course. i don't feel that i've gotten my money's worth. i expected a book that was clear and concise; i found it tobe neither. i've been very disappointed
Rating: 
Summary: Broad scope & highly usable content.
Review: I've owned this book a long time, and it remains a favorite. Pressman covers a wide range of engineering topics, starting from considering 'software engineering' as a true discipline, on to various team approaches, ways of acquiring project requirements, issues of quality control, and more. It is a solid and comprehensive overview of the issues a software engineer will face. One shortcoming of the book are that it is not as up-to-date on some topics as one would like, such as "extreme programming" and new cost estimation techniques. Additionally, you may find yourself shopping for additional books on specific topics, as the book does not treat all in equal depth. However, it is the best overall survey of software engineering I have found. I would recommend this both for the academic student, and the student of one's profession.
Rating:
Summary: Horribly written
Review: If you are a software engineer already, or if you are a CS professor, you might find this book marginally entertaining. Otherwise, if you are a student trying to learn the material, you will find this book horribly written. Here's an example: software process is defined as "process, methods, and tools layers described in Section 2.1.1 and the generic phases discussed in Section 2.1.2." Quite a lazy way to define one of the most important terms in the book.
Rating:
Summary: A Worthless Buy
Review: If you don't have to purchase this book for your college software engineering classes then please save your cash. This book is the absolute worst. After reading this book and completing the exercises for my classes you will change your mind about being a software engineer.
|
