Win a copy of Getting started with Java on the Raspberry Pi this week in the Raspberry Pi forum!
  • 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Jeanne Boyarsky
  • Rob Spoor
  • Devaka Cooray
  • Liutauras Vilda
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
  • Piet Souris

Pattern Oriented Software Architecture, Vol 1.

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
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 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 || More info at
Do not meddle in the affairs of dragons - for you are crunchy and good with ketchup. Crunchy tiny ad:
Low Tech Laboratory
    Bookmark Topic Watch Topic
  • New Topic