An architect sees things differently from a developer’s point of view, much in the same way a meteorologist might see clouds differently from an artists point-of-view. This is called architectural thinking. Unfortunately, too many architects believe that architectural thinking is simply just “thinking about the architecture” as depicted in Figure 2-1.
Architectural thinking is much more than that. It is seeing things with an architectural eye, or an architectural point-of-view. Thinking like an architect is understanding the difference between architecture and design and knowing how to collaborate with development teams to make architecture work. Thinking like an architect is about having a wide breadth of technical knowledge while still maintaining a certain level of technical depth, allowing the architect to see solutions and possibilities that others do not see. Thinking like an architect is about understanding, analyzing, and reconciling tradeoffs between various solutions and technologies. Finally, thinking like an architect is about understanding the importance of business drivers and how they translate to architectural concerns.
In this chapter we explore these four aspects of thinking like an architect and seeing things with an architectural eye.
The difference between architecture ...