TOGAF ( The Open Group Architecture Framework) can be said to be the most popular enterprise architecture framework theory. As of the time of writing this book, a large part of the top 50 companies on the Forbes list are already using this enterprise architecture. The framework has been established, and the recognition rate of Chinese enterprises has exceeded 50%. TOGAF can be said to be a typical case of enterprise architecture theory from the government to social research institutions. It originated from the US Department of Defense's Technical Architecture Framework for Information Management (TAFIM) After permission and encouragement, with the help of a large amount of funding from the US government, and after years of hard work, the first version of TOGAF was finally released in 1995. So far, TOGAF has been released to the ninth version, namely TOGAF 9 (the latest version is TOGAF 9.1 released in 2011), and this is exactly what this chapter describes.
Architecture Development Cycle
Here are the main points of ADM:
- ADM iterates throughout the process, between and within stages. For each iteration of ADM, a new decision must be made:
- The breadth of enterprise reach to be defined
- level of detail to define
- The target range for the timeframe, including the number and extent of any intermediate timeframes
- Architecture assets that will be used in the organization's Enterprise Continuum include:
- Assets created in previous iterations of the ADM cycle within the enterprise
- Assets in other areas of the industry (other frameworks, system models, vertical industry models, etc.)
- These decisions need to be made on the basis of a realistic assessment of resource and capability availability and can actually be expected to yield value to the business from the chosen scope of architectural work.
- As a general approach, ADM is designed to be used by businesses in a variety of geographies and across different verticals/industry types. Therefore, it may, but does not necessarily have to be tailored to specific needs. E.g:
- It can be used with another framework's deliverable set that is considered more suitable for a specific organization. (For example, many U.S. federal agencies have developed individual frameworks that define deliverables for specific sector needs.)
- It can be used in conjunction with the well-known Zachman framework, which is a good classification scheme but lacks a publicly available, well-defined approach.
In addition to the method itself being iterative, there are iterations within the ADM cycle, both between phases and between steps within each phase.
TOGAF ADM Reading List
- TOGAF ADM : Elaboration - Part 0: Overview of TOGAF Framework and Architecture Development Method
- TOGAF ADM : Elaboration - Part 1: Development Phase
- TOGAF ADM : Elaboration - Part 2: Activities in the Stages
- TOGAF ADM : Elaboration - Part 3: Preliminary Phase
- TOGAF ADM : Elaboration - Part 4: Phase A : Architecture Vision (phase A - Vision)
- TOGAF ADM : Elaboration - Part 5: Phase B : Business Architecture (Phase B - Business)
- TOGAF ADM : Elaboration - Part 6: Phase C : Information System Architecture (Phase C - Application)
- TOGAF ADM : Elaboration - Part 7: Phase D : Technical Architecture (Phase D - Application)
- TOGAF ADM : Elaboration - Part 8: Phase E : Opportunity and Solution Phase
- TOGAF ADM : Elaboration - Part 9: Phase F - Migration Planning Phase
- TOGAF ADM : Elaboration - Part 10: Phase G : Implementation Governance Phase
- TOGAF ADM : Elaboration - Part 11: Phase H : Architecture Change Management
- TOGAF ADM : Elaboration - Part 12: Architecture Requirement Management
- Free TOGAF Learning Resources
- TOGAF Manual - Free gitbook
- Free Manual - TOGAF 9 - Pocket Guide
TOGAF Tools and Articles