When considering the scope of an architecture, what dimension considers to what level of detail the architecting effort should go?

When scoping an architecture, "depth" refers to the level of detail that the architectural descriptions will include. A high-level architecture might only define major components and their interactions, which is considered "shallow". A more detailed, or "deep", architecture would specify interfaces, protocols, and internal component structures. This dimension helps control the amount of detail and effort required for the architecting work, ensuring it is appropriate for the project's objectives.

A. A project is the vehicle for executing the architecture work; it is not a dimension of the architecture's scope itself.
B. Breadth refers to the extent of the enterprise that the architecture will cover, such as a single department, a business unit, or the entire enterprise.
D. Architecture Domains (Business, Data, Application, Technology) define the different areas of the architecture, not the level of detail within them.

1. The Open Group, TOGAF® Standard, 10th Edition, ADM Techniques. Chapter 4, "Applying the ADM". Section 4.3, "Scoping the Architecture", explicitly discusses the dimensions for scoping, stating: "Depth: To what level of detail will the architecting be done?".

2. The Open Group, TOGAF® Standard, 10th Edition, The ADM. Chapter 5, "Phase A: Architecture Vision". Section 5.4.3, "Confirm and Elaborate Architecture Scope", describes the activities for determining the breadth, depth, and time period for the architecture effort.