بالنسبة لكتاب هندسة البرمجيات
المرجع
http://www.amazon.com/Software-Engin.../dp/0073375977
14 of 17 people found the following review helpful:
1.0 out of 5 stars
Horrible out of date Software Engineering book, December 12, 2009
By
J. Muller (VA) -
See all my reviews
(REAL NAME)
Amazon Verified Purchase(
What's this?)
This review is from: Software Engineering: A Practitioner's Approach (Hardcover)
This book is like a bloated piece of software. The author wastes so much of the book describing outdated methods and does not even seem to understand current methods. For example, many of the chapters describe procedural programming techniques such as data flow diagrams and then give a brief inaccurate deion of modern techniques such as UML. The author also makes a big deal about comparing "traditional" programming and object oriented. Given that object oriented has been the dominant style for about 20 years, it just seems irrelevant to discuss it so much in the book. The examples in the book are also very confusing and hard to relate to. Instead of picking something simple that everybody knows like a banking system, he often uses something like a convoluted sensor system. This is just a horrible book and it's unfortunate that many CS students have to get stuck using it.
Help other customers find the most helpful reviews
Was this review helpful to you?
Report this| Permalink
Comment Comments (4)
1.0 out of 5 stars
Unbearable, September 7, 2010
By
Matt -
See all my reviews
Amazon Verified Purchase(
What's this?)
This review is from: Software Engineering: A Practitioner's Approach (Hardcover)
This book is unreadable. I'm just three chapters in, and I can't bear the thought of having to read more. Nearly every paragraph is inflated with buzzwords, obscure new phases and acronyms. The author drones on and on about archaic software models when a simple table and summary of each would suffice. Pressman writes almost as if he is trying to fill a word quota.
Before reading this book, I believed software engineering was dead. And after reading some of this book, I now know why: Software Engineering == Software Bureaucracy.
Potential buyers of this book might want to read the article "Software Engineering: An Idea Whose Time Has Come and Gone?" by Tom DeMarco.
Help other customers find the most helpful reviews
Was this review helpful to you?
Report this| Permalink
Comment Comment
1.0 out of 5 stars
Waste of money, July 5, 2010
By
mc16 -
See all my reviews
Amazon Verified Purchase(
What's this?)
This review is from: Software Engineering: A Practitioner's Approach (Hardcover)
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 deions 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.
Help other customers find the most helpful reviews
Was this review helpful to you?
Report this| Permalink
Comment Comment
Share your thoughts with other customers:
Create your own review
› See all 4 customer reviews...