TOGAF is an architecture framework that provides methods and tools for developing, managing, and governing enterprise architecture. It defines architecture as the fundamental organization of a system, including its components and relationships. TOGAF deals with four architecture domains: business, data, application, and technology. The TOGAF Architecture Development Method (ADM) is a repeatable process for developing architectures within these domains through iterative phases from vision to migration planning and governance.
TOGAF is an architecture framework that provides methods and tools for developing, managing, and governing enterprise architecture. It defines architecture as the fundamental organization of a system, including its components and relationships. TOGAF deals with four architecture domains: business, data, application, and technology. The TOGAF Architecture Development Method (ADM) is a repeatable process for developing architectures within these domains through iterative phases from vision to migration planning and governance.
TOGAF is an architecture framework that provides methods and tools for developing, managing, and governing enterprise architecture. It defines architecture as the fundamental organization of a system, including its components and relationships. TOGAF deals with four architecture domains: business, data, application, and technology. The TOGAF Architecture Development Method (ADM) is a repeatable process for developing architectures within these domains through iterative phases from vision to migration planning and governance.
TOGAF is an architecture framework - The Open Group
Architecture Framework. TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. It is based on an iterative process model supported by best practices and a re- usable set of existing architecture assets. WHAT IS ARCHITECTURE IN THE CONTEXT OF TOGAF?
ISO/IEC 42010:2007 defines "architecture" as:
"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." TOGAF embraces but does not strictly adhere to ISO/IEC 42010:2007 terminology. In TOGAF, "architecture" has two meanings depending upon the context: A formal description of a system, or a detailed plan of the system at component level to guide its implementation The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time WHAT KIND OF ARCHITECTURE DOES TOGAF DEAL WITH? There are four architecture domains that are commonly accepted as subsets of an overall enterprise architecture, all of which TOGAF is designed to support: The Business Architecture defines the business strategy, governance, organization, and key business processes. The Data Architecture describes the structure of an organization's logical and physical data assets and data management resources. The Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization. The Technology Architecture describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc. ARCHITECTURE DEVELOPMENT METHOD
The TOGAF Architecture Development Method (ADM) provides a
tested and repeatable process for developing architectures. The ADM includes establishing an architecture framework, developing architecture content, transitioning, and governing the realization of architectures. All of these activities are carried out within an iterative cycle of continuous architecture definition and realization that allows organizations to transform their enterprises in a controlled manner in response to business goals and opportunities. PHASES WITHIN THE ADM ARE AS FOLLOWS: The Preliminary Phase describes the preparation and initiation activities required to prepare to meet the business directive for a new enterprise architecture, including the definition of an Organization-Specific Architecture framework and the definition of principles. Phase A: Architecture Vision describes the initial phase of an architecture development cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals. Phase B: Business Architecture describes the development of a Business Architecture to support an agreed Architecture Vision. Phase C: Information Systems Architectures describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures. Phase D: Technology Architecture describes the development of the Technology Architecture for an architecture project. Phase E: Opportunities & Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases. Phase F: Migration Planning addresses the formulation of a set of detailed sequence of transition architectures with a supporting Implementation and Migration Plan. Phase G: Implementation Governance provides an architectural oversight of the implementation. Phase H: Architecture Change Management establishes procedures for managing change to the new architecture. Requirements Management examines the process of managing architecture requirements throughout the ADM.