• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Pattern Oriented Software Architecture, Vol 1.

 
Bartender
Posts: 962
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
<pre>Author/s : Frank Buschmann, Regine Meunier, Hans Rohnert et al
Publisher : John Wiley & Sons Ltd.
Category : Design
Review by : Madhav Lakkapragada
Rating : 6 horseshoes
</pre>
The title "Pattern Oriented Software architecture" suggested to me that the book deals a lot with design patterns for software. Maybe because this book was compared to the GoF book in one of the online reviews at Amazon.com. Somewhere in this thought process I got lost reading this book. Defenitely, the book describes patterns. However, the book gives very few examples explaining the usage of the pattern. It describes the architecture details but with very few code examples. So, I do confess that this was not the kind of book I was expecting based on the title. On the other hand the book emphasises Smalltalk examples, although a handful of examples are in C++. A few others examples regarding client-server design patterns are in Java, since Soket programming is easy in Java, I assume.
The book is divided into three sections - Architectural Patterns, Design Patterns and other discussions on pattern systems and the future. It concentrates to a large extent on the Architectural patterns. I felt the book is very dry and theoritical as I read through the chapters. I was looking for a more dynamic approach where I could see code changing due to the application of a patterns.
Finally, I must admit its highly possible that this book describes a topic excellently but maybe I just couldn't make that connection. I, personally, could never connect with dry and theoritical subjects. I am rating the book above average giving due credit to the detailed explanations.
More info at Amazon.com || More info at Amazon.co.uk
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic