Architecture Landscape Knowledge-Based Study

Study notes

1. The Architecture Landscape in the Architecture Repository

   Within the TOGAF Standard, 10th Edition, the Architecture Repository acts as the central holding area for all architecture-related assets, models, standards, and governance records across an enterprise.

   A critical component of this repository is the Architecture Landscape. The Architecture Landscape represents the architectural views of the state of the enterprise at particular points in time. It documents what the enterprise currently looks like, what it aspires to look like in the future, and the transitional steps planned along the way.

   Key Dimensions of Time

   The Architecture Landscape typically categorizes architectural representations across three temporal states:

   • Baseline Architecture: The existing, current operational state of the enterprise across business, data, application, and technology domains.
   • Target Architecture: The approved future operational state that realizes business strategy and strategic objectives.
   • Transition Architecture: Incremental interim states that describe the progression toward the Target Architecture, often aligned to program milestones or investment cycles.

   Structuring by Levels of Granularity

   Enterprises are too complex to be modeled as a single monolithic diagram or model. The TOGAF Standard organizes the Architecture Landscape into three distinct levels of granularity to support different stakeholder viewpoints, decision-making cycles, and levels of abstraction:

   1. Strategic Architecture

   • Scope: Enterprise-wide or across broad operating divisions.
   • Purpose: Provides a high-level summary framework for executive decision-making, strategic alignment, and overall portfolio planning.
   • Horizon: Typically long-term, setting corporate direction and constraints for subsequent architectures.

   2. Segment Architecture

   • Scope: A specific line of business, operational function, or cross-functional program (e.g., Supply Chain Management, Customer Experience).
   • Purpose: Structures operating models, processes, and service boundaries within a discrete business domain.
   • Horizon: Medium-term, guiding program execution and portfolio prioritization.

   3. Capability Architecture

   • Scope: A focused business capability or supporting solution group (e.g., Identity and Access Management, Real-Time Inventory Tracking).
   • Purpose: Delivers detailed architectural definitions, building blocks, and technical standards needed to design and deploy executable projects.
   • Horizon: Tactical to near-term, supporting immediate project delivery and operational realization.

   Interaction with the ADM Lifecycle

   The Architecture Landscape serves as both an input and an output throughout the execution of the TOGAF Architecture Development Method (ADM):

   • Preliminary Phase & Phase A (Architecture Vision): Practitioners consult the existing Architecture Landscape to understand current boundaries, determine the scope of new initiatives, and identify interdependencies with other ongoing architecture projects.
   • Phases B, C, and D (Domain Architectures): Baseline and target states for Business, Data, Application, and Technology are retrieved from the landscape to identify reuse opportunities and ensure architectural continuity. Newly elaborated models are drafted to update the landscape.
   • Phase E (Opportunities & Solutions) and Phase F (Migration Planning): Transition Architectures are defined and situated within the landscape to guide multi-year roadmaps and project delivery sequences.
   • Phase G and Phase H: Governed implementations provide feedback into the landscape, transitioning target architectures into established baseline architectures upon deployment.

   Conceptual Distinction: Landscape vs. Metamodel and Solutions

   It is vital not to confuse the Architecture Landscape with adjacent sections of the Architecture Repository:

   • The Architecture Metamodel defines the conceptual types, relationship rules, and structure used to build architectural artifacts, whereas the landscape stores the actual instances and views created using that metamodel.
   • The Solutions Landscape contains concrete, deployable physical assets (packaged software, hardware platforms, deployed services), whereas the Architecture Landscape contains the architectural models and abstractions that define and guide those solutions.