Bubble diagrams, stacking diagrams, and proximity graphics are the visual language architects use to translate a building program into spatial organization before any floor plans get drawn. This topic covers how to read, interpret, and evaluate these diagrams during the programming and analysis phase.

The ARE expects you to analyze diagrammatic graphics that communicate building relationships. That means you won't just identify what a bubble diagram is. You'll evaluate whether a proposed diagram correctly represents the spatial and functional relationships described in a program. You'll judge whether a stacking diagram places departments on the right floors, whether circulation paths make sense given security or operational requirements, and whether adjacency priorities have been honored or violated.

Bubble diagrams represent horizontal relationships on a single floor. Circles (or ovals) represent program spaces, and their sizes roughly correspond to area requirements. Lines or overlaps between bubbles show adjacency needs. Stacking diagrams translate those relationships vertically, showing how departments distribute across multiple floors and how vertical circulation elements like stairs, elevators, and shafts connect them.

Proximity matrices, sometimes called adjacency matrices, assign numeric or categorical ratings to every pair of spaces in the program. They're the data behind the diagram. A matrix might rate each pair as "essential," "desirable," "neutral," or "undesirable" adjacency. The diagram then visualizes those ratings spatially.

On the exam, you'll see scenarios where you need to evaluate whether a proposed layout satisfies the adjacency requirements shown in a matrix or whether a stacking diagram correctly addresses vertical circulation and zoning constraints.