Software Engineering: A Practitioner's Approach
N**.
Full of fluff
I would unfortunately have to agree with many of the other negative reviews of this book that have already been submitted. I found the book very hard to read, due in part to poor organization, writing style, and FLUFF! In every chapter that I have made it through, and in many of the sections within the chapter, the author introduces a subject only to say it will be covered much much later. I found this incredibly distracting and felt that it took away from any comprehensive quality to the book. The author also takes a first person narrative style in his writing, which gives the book a totally subjective and even anecdotal quality, which I had previously never experienced in a text, especially one meant to be somewhat technical.But the worst thing about the book is the enormous amounts of fluff you have to wade through before extracting any meaning out of what you have read. After reading a chapter, you may feel that you are now aware that the chapter's topic is a part of software engineering, but you will have learned almost nothing about how to implement that aspect of software engineering in practical use. Another source of fluff is seen in how little of each page is actually occupied by the book's instructive text. The margins are filled with hints and other extraneous information that serve only to make the page cluttered. There is also a running side story that continues throughout the text in which fictional characters working at a software engineering company apply the principles discussed in the text so that the reader can gain knowledge of how those concepts might function in the "real world." This could potentially be a helpful addition to the book, but unfortunately one merely gets to know the author's sense of humor.To sum it up, this book is a chore to read. Don't buy it if you have a choice. If it is a required text for a course, my condolences.
M**N
How to be Twit in Software "Engineering"
This book is a great example of the infiltration of computer science by "consultants." I don't know that the author necessarily lacks any hard skills, but the book gave me that impression. This book is just a compilation of meandering buzzword babble that makes no point and warrants no confidence. The topic is project management with lots of IT-ish buzzwords thrown around. Do not expect to learn anything reasonably classified as "engineering." For the reader who is currently peddling management fads and looking to bother people who make software, then this is the book for you. On the other hand, if you are someone who programs or is learning to program and wants to know more about the process of creating really great software, then stay as far away from this book as you can get. Every second spent reading this is a second of life that would've been better spent napping.
M**6
Waste of money
This book was purchased as a required text for a master's level class, and I am highly disappointed in it.The book broadly and superficially covers all software engineering concepts, and to the untrained reader might appear to be a comprehensive text. Just don't look too closely. If you know absolutely nothing about the software engineering process, and want to have a high level grasp of the uniqueness that is software, then this book could be of use. The descriptions do a good job of introducing SE concepts and theories, although some are dated.If you are tasked with developing a software engineering strategy, or running a software-intensive project, or are looking to build a solid foundation and understanding of the software engineering process, walk away. Just walk away. This book introduces new terms, redefining widely and commonly used words for the software development life cycle and others. The entire SE body of knowledge uses certain words that students and practitioners get used to, and this author seems to change them around just to be different. Furthermore, the author interchanges these terms around, and is not consistent when referring to the same concept. Not something I'd expect to see after 7 revisions.
J**P
If I could give a zero, I would.
The content is out dated. The data is presented in a long series of lists, which usually reads like a dictionary. I tried even using the references, but of the three I tried one was correct, one was broken, and one was a dating site.I initially bought the kindle version, however it only works on the PC. I returned that (Thanks Amazon) and bought the paper copy.Luckily I get to sell the book back to amazon.If anyone has to use this book, please use the student resources on the publisher's website. It has great multiple choice tests that will give you the answers.
D**R
The spaghetti code of textbooks
I have rarely despised a textbook more than this. This textbook does to textbooks what the goto statement did to programming. It appears the author cut portions of the text from various paragraphs, and developed those portions into new chapters. This approach would be fine if the existing chapter was rewritten to accommodate the new chapter, but instead the author simply inserts a statements that further information can be found in a different chapter. Between this approach to editing and the overuse of lists and block quotes the text is nearly unreadable. This textbook is a shining example of the hack job the publishing industry is doing to academia.
L**.
Just Awful!
This book is full of vague definitions and concepts. There is no programming. Never have I seen someone take such an interesting subject and make it such a chore. My professor assigns a lot of the end of the chapter problems to be completed in discussion format on Blackboard. I was just attempting to complete another one and I just got mad. The book is vague but the questions ask for concise answers. It's frustrating. There has to be a better way.
K**Z
The book was in good condition and arrived quickly
It arrived faster than I had expected and has proven most useful in my studies.
U**I
McGraw Hill publication: Check page numbers.
Pages 653 to 668 are missing. Instead I have pages 709 to 740 Twice. After 652 the next page number is 709 as shown in picture and that continues up to 740, After page 740, the next is 669. By the time I realized this, the window to return this book was closed.
L**O
The bible.
This book is the only thing you need.Fantastic, comprehensive and easy to understand.
S**A
It's s gud book but concepts would be difficult to ...
It's s gud book but concepts would be difficult to understand from this book if u r a beginner
D**S
There is hardly anything to add. This has been ...
There is hardly anything to add. This has been an authoritative reference for so long!With every edition, Pressman seems to manage the improvements amazingly well. Every edition meets your heightened expectations.
A**J
overall reviews
delivery is before time.... packaging are well .payment methods are also....perfect...overall everything is good and perfect
Trustpilot
2 days ago
5 days ago