One of the worst book

Software Design Patterns is something to do with your coding - at least according to the classical design pattern book by "The Gang of Four". According to that particular book, a pattern has a name for recognition, a problem domain and solution.

Basically this book did not address software design patterns. It does employ a similar "writing architecture" from the gang of four book - Problem Context, Solution and so on, but it focuses mainly on other aspects instead of real "software design patterns".

To make it clear, say for example, we have a Singleton software pattern which there exist no more famous pattern. How does UML address this design pattern? God knows, from this book. What it address - for example, section 5.5: "Where can a UML model hold the business rules that guide system operation? Specifically, how can rules that describe fundamental knowledge in the domain be explicitly documented?"

This makes the book totally back to the UML problem doamin - how to use UML as a modelling tool, instead of "converging UML and Design Pattern", the book objective.

Even worse, Section 5.6 titled "Dynamic Object Types" and the problem is "An object must change types by representing different but similar things at different times." What it means is nothing more than "object inheritance", one of the basic object oriented programming knowledges. It simply makes things more complicated than it has to be.

To conclude, by turning over this book for 5 minutes I bet a real reader would close it and find another.

Other Reviews

• An author comments, somewhat belatedly
• One of the worst book
• Shoemaker's Son
• One of the 5 best computer science books I have ever read.
• Hard material