|
|
|
The primary goal of the Handbook is codify the architecture of a representative collection of interesting software-intensive systems, presenting them in a manner that exposes their essential patterns and that permits comparisons across domains and architectural styles. Reflecting on his work on patterns, Christopher Alexander once noted that he and his colleagues "made observations, looked to see what worked, studied it, tried to distill out the essentials, and wrote them down1." This approach is at the core of all good science; it is also the guiding principle behind the Handbook itself.
The second goal of this work is to collect the contemporary best practices for specifying, visualizing, documenting, governing, and evolving a system's significant design decisions.
The third goal of this work is to feed my insatiable curiosity. Whenever I encounter an interesting or useful software-intensive system, I often ask myself, "how did they do that?" By exposing the inner beauty of these systems through a study of their architectural patterns, I hope to offer inspiration to developers who want to build upon the experience of other well-engineered systems.
1 Alexander, p. 3.
|
|
|
|
Blog