| FlazX | Browse Computer Book | Community Board | Links | Blog | Login |
|
Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages
Google Search |
User review A briliant source on pattern language concepts We knew something about patterns and the relationships between patterns, but, this book addresses the concept of pattern language more deeply by classifying and naming those relationships, such as Complements, Compounds, and Sequences. These idea are covered in part II of the book, after talking about single patterns in part I, which I think we know more about it from the literature. The most interesting part, from my point of view, is part III, which relates the concepts of pattern language to the well-known jargon in theory of automation. I like the analogy of patterns as words and pattern sequences as sentences, and I think we can borrow some idea of compilers to build tools that help designers that are using a pattern language. This is what I'm working as my research right now. Finally, the book could be more compact, specially for the first two parts. But, considering the fact that the authors wanted to wrap up their ideas presented in the previous four volumes, it had to be wordy. User review A Book about Patterns I just saw that POSA5 does not have a review. It definitely deserves one, so here we go. In the spirit of full disclosure, I know Frank and Kevlin quite well through our work in the patterns community. But I am still entitled to my own opinions when it comes to book reviews! POSA5 is different from the other four POSA's. In a sense, it is a `meta` book, a book about patterns, rather than a book using patterns. In spirit it is closest to John Vlissides' insightful Pattern Hatching: Design Patterns Applied (Software Patterns Series), but on a somewhat grander scale. I have only read the first few chapers so far (the book is too heavy to carry around when I travel). Chapter 1 describes the evolution of an example pattern from an `OK` write-up to a rich, deep pattern. I love the example because the starting point is not even bad, but the end result is so much better. Later chapters in the book talk about relationships between patterns and pattern languages. Why another book on patters? When you look at the book shelves jock full with `patterns` books, you might get the impression that people have figured out how to write patterns. However, patterns have suffered a bit from their own success, having become a buzzword. `If you make it a pattern, people will take it more seriously` is often the attitude. But pattern != pattern. This book highlights what makes good patterns and pattern languages. It's a conceptual topic but the book uses a lot of examples. I wish the publishers could require every author who is sticking `Patterns` into their book title to read this book. Why only 4 stars? Because I have not finished reading yet. As in the stock market, uncertainty weighs. If it continues the way it starts, it'll certainly be 5 stars. Other books on Software Architecture | |||||||||||
Google Talk : admin-at-flazx-dot-us