TOGAF, the full name of Open Group Architecture Framework, is an enterprise architecture framework published by the organization The Open Group in 1995, and the latest version is 9.2. Open Group is an internationally renowned standardization organization with a history of more than 20 years of standard formulation and promotion, and TOGAF framework can be said to be its most famous contribution. TOGAF can be said to be a typical case of enterprise architecture theory entering various social research institutions from the government. It originated from TAFIM (Information Management Technology Framework) of the U.S. Department of Defense. With the permission and encouragement of the U.S. Department of Defense and the help of a lot of funds invested by the U.S. government, after years of efforts, the first edition of TOGAF was finally released from 65438 to 0995. So far, TOGAF is the most mainstream and well-known EA framework. It is used by 80% of the top 50 enterprises in the world, and the recognition of TOGAF by China enterprises exceeds 50%, so that when it comes to enterprise architecture, many people think it is TOGAF for the first time. It is also the only framework that provides authentication.
frame construction
The following official pictures illustrate the composition of TOGAF:
The colored parts in the figure are several main components of TOGAF, which are explained separately below.
TOGAF ADM (Architecture Development Method): This is the core part of TOGAF framework, and it is TOGAF's elaboration of enterprise architecture construction method. Based on a cyclic iteration model, the construction process of enterprise architecture is divided into several steps, and the input, output and adopted methods of each step are expounded in detail.
TOGAF content framework: this part is a new part of TOGAF 9, which describes in detail the various work products contained in the enterprise architecture and their relationships. Since then, it has changed the style of focusing only on the process and method of architecture development, and filled the gap in the description and guidance of architecture content in the past.
TOGAF capability framework: In order to run the enterprise architecture effectively and maximize its efficiency, it is necessary to define and combine a series of appropriate organizational structures, processes, skills, roles and responsibilities. TOGAF Capability Framework is providing guidance on how to organize these elements well.
TOGAF enterprise continuum and tools: Enterprise continuum is the view of enterprise architecture resource library, which provides a method to classify and organize various architecture and solution products in the enterprise.
The above four parts are relatively independent. Among them, the content of competency framework focuses on helping enterprises use enterprise architecture better, the framework development methods and content framework focus on helping enterprises improve the standardization level and execution efficiency in the process of enterprise architecture construction and maintenance, while enterprise continuum and various methods and tools pay more attention to providing reference and best practices for enterprises in the process of enterprise architecture development, use and maintenance. Although these three parts are relatively independent, the creation, use and maintenance of an excellent enterprise architecture are the result of their close cooperation and interaction.
In these four parts, I personally think that ADM, the architecture development method, is the core part of TOGAF. Understand, TOGAF can't live without it.
TOGAF architecture development method (TOGAF ADM (architecture? Development method))
ADM is famous for the following crop circle maps:
It defines 10 stages of ADM, in which the preparation stage is independent, the stage A to the stage H is iterative, and the demand management runs through the whole ADM process.
You can write an article at each stage of development, so I won't expand it here, just briefly introduce each link.
Preliminary: This phase describes the preparation and start-up activities of the new enterprise architecture required by the business instructions, including the framework and principles for defining the organization-specific architecture.
Stage A-Architecture Vision: A brief description of the target architecture, its business value and the enterprise transformation brought about by the successful deployment of the architecture is the ideal vision and dividing line of specific architecture development.
Stage B-business architecture: a description of a comprehensive multidimensional business view, including: capabilities, end-to-end value delivery, information and organizational structure; And the relationship between these business views and strategies, products, policies, plans and stakeholders.
Stage c? -Information system architecture: focusing on defining various data and applications used to support enterprise business architecture. The construction of information system architecture can be divided into data architecture and application architecture.
Stage D- Technical Architecture: Description of the structure and interaction of technical services and technical components.
Stage E-Opportunities and Solutions: This stage describes the process of determining the delivery method (project, plan or pedigree) in order to effectively deliver the target architecture formulated in the previous stage.
F stage? -Migration Planning: Finalize the detailed implementation and migration plan to migrate from the infrastructure to the target architecture.
Phase G-Achieving Governance: Monitor the implementation of the architecture to ensure that the defined architecture is consistent with the plan during implementation and deployment.
Stage H-Architecture Change Management: Evaluate the architecture performance, make suggestions for changes, and ensure that the baseline architecture continues to conform to the current reality. Establish an architecture change management process to realize the new enterprise architecture baseline established in the governance phase.
Requirements management: define a process so that the requirements of enterprise architecture can be identified, stored and interacted with other phases of the architecture development method.
Each stage will have its own corresponding methodological steps, and each step will have its own corresponding input and output. When the whole set is completed, there will be dozens, close to hundreds of output documents. It can be said that TOGAF is a framework that emphasizes processes and documents.
affect
TOGAF is a master of enterprise architecture framework, which has played a great role in spreading the concept of enterprise architecture, so that many people even think that enterprise architecture is equivalent to realizing TOGAF. At present, TOGAF has become the implementation standard of EA framework. It is constantly improving and strengthening itself, especially with the support of SOA, making it keep up with the trend of service.
However, for enterprise architecture, TOGAF is beneficial to communication at the conceptual level and unfavorable at the promotion level. People know that there is an enterprise architecture through TOGAF, but they dare not really try. The reason is that TOGAF seems to go to the other extreme compared with Zachman's simplicity. It is all-encompassing, cumbersome processes and heavy documents, which makes enterprises who want to implement EA flinch. Without the support of external consulting forces, many enterprises simply don't know how to do it. Although TOGAF claims that ADM and content framework can be tailored according to the actual situation, it is already a high threshold to know what to cut and how to cut it. How to evaluate the effect of TOGAF is also a very difficult thing. Is it possible to build a good enterprise architecture by just outputting a bunch of documents? These problems and concerns greatly limit the promotion of TOGAF and even enterprise architecture. If the framework is as simple as Zachman, it will be criticized as weak in guiding significance and as all-encompassing as TOGAF, and it will be considered too heavy and difficult to achieve. The road to EA is really a long way to go.