Wed, 24 Mar 2010 09:32:55 +0000

A few years back, as an exercise, I went thru the book - "Software Architecture Design Patterns in Java" by Partha Kuchana and created java programs for all the examples stated in this book. I dug up that code recently and decided to post it here. Click here to download the source code (browse to the bottom of the screen and click the download now button). Unfortunately you will have to wait for 30 seconds to download the file (Let me know if there is a better site to host files).

Disclaimer: All the java code has been written by refering to examples in "Software Architecture Design Patterns in Java" by Partha Kuchana

This above book is a very good read and a simple introduction into design patterns. Please refer to the README file located in the source code zip file.

This book serve mostly as historical note. In its time pepole use to think that “the answer” is OOP/OOD. If this book prove anything is that OOP/OOD is NOT the answer. For begginer this book is usless since they do not have the knowlage to read it and evaluate it ideas. For experience programmers this book may serve to prove that in some implemention they were using some ideas that other were using. For those with experience that realy find something new here then I think it only time for them to realized that they are very poor designers. You see in C++ you have many tools to use (and OOP is only one). This book seem to be writing by people who start to program in programming laguages that force you to use object – such as smalltalk. C++ is much more then that and now we know (I realy hope that those who are using C++ know) that OOP is just anther thing to use and not the most important one. Anther problem is that it may lead people to use those patterns in much the same way as OOP – seeing pattenrs everywhere (like many programmer who using OOP see object everywhere). Anther problem is that it like those books about “how to succeed in life in 10 steps”. Well like there is no magic in being successfull (you can’t realy learn how to become one) there is no way in becoming good designer. If you don’t know how to design system, no book can save you. Designing good software is like art, if you don’t have the gift you cannot do it – and ideas from architecture are the worst to take from. When you designing a system, look in the system that you are building for ideas and not in a book that try to solve problems that are not even there. By the way for Java/C# programmers it maybe more usefull (beacuse those lagauges only support OOP). If you are C++ programmer then learn the laguage realy well (there’s much to learn), this is the only thing that will realy help you.
Rating: 2 / 5