The Architecture Continuum provides a consistent way to describe and understand the implementation of the assets

A Foundation Architecture supports the complete enterprise operating environment.

Common Systems Architectures guide the creation of an architecture useful for building common solutions across a wide number of relevant domains

Industry Architectures guide the integration of common systems components with industry specific components.

Organization-Specific Architectures describe and guide the final deployment of user-written or third-party components that constitute effective solutions for particular enterprises

At relevant places throughout the ADM, there are reminders to consider which architecture assets from the Architecture Repository the architect should use

The practical implementation of the Enterprise Continuum will typically take the form of an Architecture Repository that includes reference architectures, models, and patterns mandated in TOGAF

In executing the ADM, the architect is only developing a snapshot of the enterprise at particular points in time, and populating the organization’s own Architecture Repository is outside the scope of ADM

The first execution of the ADM is simplified because of the re-use potential of the standard architecture assets available for re-use in TOGAF Architecture Repository

Architecture Repository is only accessed in the Requirement Management phase

Fundamental organization of the IT system

The principles governing its design and evolution IT system

Hardware, software, and communications technology and their relationships to each other and the environment

Technical implementation architecture

Target Technology Architecture that will form the basis of the subsequent implementation and migration planning

Architecture Landscape

Standards Information Base

Architecture Metamodel

Architecture Capability

E. Compliance Log

Implementing a system of controls over the creation and monitoring of all architectural components and activities

Improving the maturity level of architecture discipline within the organization

Implementing a system to ensure compliance with internal and external standards and regulatory obligations

Establishing processes that support effective management of the above processes within agreed parameters

Developing practices that ensure accountability to a clearly identified stakeholder community

Preliminary phase

Phase A

Phase B

Phase C

Phase D

To improve the maturity level of architecture discipline within the organization

To identify where the standards themselves may require modification

To identify services that are currently application-specific but might be provided as part of the enterprise infrastructure

To document strategies for collaboration, resource sharing, and other synergies across multiple architecture teams

To take advantage of advances in technology

The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution

A rigorous description of the structure of an enterprise, which comprises enterprise components (business entities), the externally visible properties of those components, and the relationships (e.g. the behavior) between them

An architecture is the most important, pervasive, top-level, strategic inventions, decisions, and their associated rationales about the overall structure (i.e., essential elements and their relationships) and associated characteristics and behavior

Architecture is the use of abstractions and models to simplify and communicate complex structures and processes to improve understanding and forecasting

A formal description of a system, or a detailed plan of the system at a component level to guide its implementation or the structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time

Enterprise Continuum is a virtual repository where as the Architecture Repository is a physical repository

Enterprise Continuum can be thought of as a view of the Architecture Repository

The Architecture Repository defines six classes for architectural information held in the repository

TOGAF recognizes the need to manage the content of the Enterprise Continuum using tools but does not provide any guidance on tool selection

The Solutions Continuum is a population of the architecture with reference building blocks – either purchased products or built components – that represent a solution to the enterprise’s business needs

Preliminary phase

Phase A

Phase B

Phase C

Phase D

this is the answer

this is the answer option 1

this is the answer option 1

this is the answer option 1