OGBA-101 VCE Exam Download

In TOGAF, the dimensions for scoping an architecture are Breadth (coverage across the organization), Depth (level of detail), Time Period (horizon of the architecture), and Architecture Domains (the four architecture domains of Business, Data, Application, and Technology). These dimensions ensure comprehensive scoping and contextual alignment.

References: TOGAF Standard, Chapter on Scoping the Architecture.

According to TOGAF, defining the scope of an architecture involves considering these four key dimensions:

Breadth:This refers to how much of the enterprise is covered by the architecture. It defines the boundaries of the architecture, which could range from a single department to the entire organization, or even extending to external partners.

Depth:This dimension determines the level of detail included in the architecture. It can range from high-level conceptual models to detailed specifications of individual components.

Time Period:This specifies the timeframe for the architecture, including the intended lifespan of the architecture and any planned phases or iterations. It addresses questions like "What is the architecture for now?" and "What should the architecture look like in the future?"

Architecture Domains:This dimension defines which of the four architecture domains (Business, Data, Application, Technology) are included in the scope. The selection of domains depends on the specific needs and objectives of the architecture development effort.

Phase A (Architecture Vision) of the TOGAF ADM builds out initial organizational maps to understand high-level organizational needs and link them to architecture goals. This step provides foundational insight that informs subsequent phases, particularly for stakeholder alignment.

References: TOGAF ADM Phase A.

In TOGAF, Phase A (Architecture Vision) is where the organization map is developed in detail and linked to overviews to understand the organizational needs. This phase focuses on:

Defining the scope of the architecture:This includes identifying the parts of the organization that will be affected by the architecture and the timeframe for the architecture development.

Identifying stakeholders and their concerns:Understanding the needs and expectations of different stakeholders is crucial for developing an architecture that meets their requirements.

Creating a high-level architecture vision:This vision outlines the desired future state of the architecture and how it will support the organization's strategic goals.

In TOGAF ADM, Phase B is the Business Architecture phase where the architect should locate existing architecture descriptions to create an information map. This phase involves developing a detailed understanding of the business environment, including business processes, roles, and information flows. Existing architecture descriptions provide a baseline for identifying how information is currently managed and how it can be optimized to support business objectives.

The chart depicted is a Gantt chart, which typically represents the schedule for project activities. In the context of TOGAF's ADM, it is used to illustrate the sequence and interdependencies of tasks across different phases of architecture development. The ADM is an iterative cycle that includes various phases, from the preliminary phase, through architecture vision, business, information systems, and technology architectures, to opportunities and solutions, migration planning, implementation governance, and architecture change management. Each phase must be conducted in a sequence to ensure that the outputs of one phase feed into the next, thereby producing a coherent and structured architecture.