Learning Java Through Applications: A Graphical Approach (Programming Series) (Programming Series)

UML Distilled: A Brief Guide to the Standard Object Modeling Language, Third Edition

Head First Design Patterns

Uml

Fundamentals of Object-Oriented Design in UML

Format: Paperback
Author: Meilir Page-Jones
ReleaseDate: 03 November, 1999
Publisher: Addison-Wesley Professional
Rating:

UML as a useful accessory to OO design
But then again, this book is still very pertinent, regardless of which version of UML you are currently on. Maybe, just maybe, Page-Jones might update this book to account for the release of UML 2. The descriptions here let you describe many types of object oriented software packages, in a useful and concise manner. One that can be readily understood by others who have not worked on coding the packages. Plus, of course, another great advantage of being able to use UML is during the planning and coding of those packages.

While you can certainly do OO design without UML, Page-Jones suggests why UML can aid in the understanding.

Love Page-Jones books and .... hate OOP
I've been a programmer (after a few other things, like a regional planner, by example) almost for the last 20 yrs. Any positive thing, and there is a lot of them so far (I'm in page 65), in this book is a merit of the author, not of the subject itself, OOP.
I've been a witness of many revolutions: somebody remembers OS/2 and the Data Manager?, or the AI discussions, that filled thousands of computing papers and magazines, about which one is better: Prolog or LISP?
I remember the words of a scientist: "the best language is your mother tongue, that you naturally use for discuss and analyze problems, and for formulate solutions to them".
Only one little difference: those were freedom times, no software or hardware company had the total control, programmers, worked individually but at the same time, collaborated with each other, even being a rare species, didn't charge a thousand/hour, and managers weren't so worried about controlling and slavering programmers, which is the real motive behind of all sort of "magic" software development paradigms today in place: to take out from programmers the free spirit, the freedom of solve the user's problem the best way the programmer, him or herself, can figure out.
These days, the cool thing is project management, team meetings, lot of vacuum methodologies, infinite and continuous upgrades of tools and platforms. I'm sure 100% that in the core of the code of the couple of dozens of real outstanding software products nowadays, call it AutoCAD 25 or Doom 3, there are two or three programmers, the AUTHORS, and another 15 or 20 people around, doing complementary tasks, along the cycle of life. Everything else is market "hoopla", busine$$ in the best tradition of the snake oil and hair tonics.
Not a long time ago died Edgar (Ted) Codd, I think he couldn't stand to see how the worst database in PC history: Access, a database software packaged for secretaries and bookkeepers, became dominant in the desktop scene, and has yearned billions of dollars to computing moguls. As his colleague and another database giant, Chris Date, quoted: "sad thing is he never made money (and the side plates: fame, glory, etc. ) from his ideas, others did. "
I have to laugh every time I see some PC wizard going to the DOS command (in every Windows incarnation more hidden than in the prior) to do some obscure and arcane ritual, with the same looking in his face as he were landing in Mars or Jupiter.
Sorry for the rampage, once in a while you have to let it go.
As John Dvorak said a little while ago: "I don't get it". All I ask God is HE provides me the strength to hold another ten years, and then retire, to read historic novels.
.

Not a complete OO or UML fundamentals book
The examples are too simplified. The author uses his own dialect of UML in too many places, Skips Use-Cases all together. It is not fundamental OO because he doesn�t define OO terminology as it is in the standards. He gives his oppinion on everything and this colors his explanations and examples.
If you are looking for a beginners UML or OO forget about this book. If you like to read another angle on some parts of the OO or some UML diagrams then this is your book.