From HandWiki - Reading time: 6 min
Pattern-Oriented Software Architecture is a series of software engineering books describing software design patterns.
| Author | Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad and Michael Stal |
|---|---|
| Language | English |
| Subject | Computer programming |
| Published | 1996 |
| ISBN | 978-0471958697 |
| Author | Douglas C. Schmidt, Michael Stal, Hans Rohnert, Frank Buschmann |
|---|---|
| Language | English |
| Subject | Computer programming |
| Published | 2000 |
| ISBN | 978-0471606956 |
| Author | Michael Kircher, Prashant Jain |
|---|---|
| Language | English |
| Subject | Computer programming |
| Published | 2004 |
| ISBN | 978-0470845257 |
| Author | Frank Buschmann, Kevlin Henney, Douglas C. Schmidt |
|---|---|
| Language | English |
| Subject | Computer programming |
| Published | 2007 |
| ISBN | 978-0470059029 |
| Author | Frank Buschmann, Kevlin Henney, Douglas C. Schmidt |
|---|---|
| Language | English |
| Subject | Computer programming |
| Published | 2007 |
| ISBN | 978-0471486480 |
David E. DeLano of C++ Report praised the first volume, writing, "Overall this text is good and I recommend it as an addition to any collection of books on patterns." He said "some of the language and grammar usage feels awkward to the reader" and some of the book has "stiffness and flow problems".[1] Ian Graham reviewed the first volume in the Journal of Object-Oriented Programming.[2] DBMS columnist David S. Linthicum found the first volume to be "the best book on patterns for application architects", while Bin Yang of JavaWorld thought it had "many interesting architecture and design patterns".[3][4]
ACCU writer Ian Glassborow reviewed the second volume, writing, "This book is one of the more important contributions to the literature on 'patterns' and deserves to become a standard text on its specified area of interest."[5] The Software Engineering Institute author Paul Clemente found the first two volumes to be "the best-known catalog of architectural patterns".[6] Regarding the third volume, D. Murali recommended that software engineers should follow the "eager acquisition" pattern.[7]