|
Data Structures and Algorithms with Object-Oriented Design Patterns in Java
 |
Author: Bruno R. Preiss
List Price: $84.95
Our Price: Click to see the latest and low price
ISBN: 0471346136
Publisher: Wiley Text Books (30 July, 1999)
Edition: Hardcover
Sales Rank: 278,008
Average Customer Rating: 2.71 out of 5
|
Customer ReviewsRating: 5 out of 5
I used this book at school
Hi, as an undergrad engineering student, I had this book for the coursebook in my algorithms course. Honestly speaking, it's good , very readable text. I never used any of the code examples fom the book in my assignments, yet they proved rather helpfull in understanding the material. Something, that I think is missing from this book is the answeres to the problems at the end of the chapter that are not programming projects. Ading them to the book could help students a lot ( no need to relay on TA's )
Rating: 2 out of 5
decent for soft eng, bad for data structures
As a second year student, the use of design patterns (see chapter 5) bothers me. It really detracts from what the author is trying to convey. It's extremely hard to ignore them because you have to backtrack to previous chapters frequently which creates more confusion.This book may be useful to learn the basics of software engineering. But given complexity of the design patterns in this book, it could be glossed over in one lecture. ...
Rating: 4 out of 5
Don't believe these other reviews...
Some people are reviewing this book as hard to read, confusing, and complaining that the code doesn't compile. Such is the state of higher education these days...I would actually say that this is a very readable introductory treatment on data structures. Granted, there seems to be the occasional error in implementing classes that strictly conform to given definitions, and some of the implementations seem a bit simplistic, but overall its a fine piece of work. I found the implementations for tree traversals in chapter 9 to be rather clever.There is something of a reliance upon a hierarchy structure (introduced in ch. 5) which i think might turn some people off in using this book as a text. Chapters seem to build upon previous chapters, requiring you to read most of the book. Professors have a tendency to skip around to fit the curricula into the time of the class term which might make the book seem confusing--i've just been reading it straight through for personal amusement so i'm not as influenced by this. I think this class hierarchy is justified because the book isn't just about data structures, its also about design patterns. If you know something about either data structures or design patterns you can gain insight into both from reading this. And as for compiling the code...the purpose of books like this shouldn't be to copy and paste code. If you have even a vague understanding of the material "filling in the blanks" and writing your own code should be a simple matter.
|
