TOGAF Framework Overview
Summary
This post is an overview of The Open Group Architecture Framework (TOGAF).
I have created it while adopting TOGAF in various business organizations. It is a practitioners point of view, which summarizes the main concepts, components and goals.
It serves as a reference point to myself and can be valuable to others in technology architecture community.
Introduction to TOGAF
The TOGAF Standard is a framework for Enterprise Architecture. It is developed and maintained by members of The Open Group.
Original development of TOGAF is based on the Technical Architecture Framework for Information Management (TAFIM), and was developed by the US Department of Defense (DoD).
The DoD gave The Open Group explicit permission and encouragement to create the first edition of TOGAF in 1995. Currently, the most recent edition is TOGAF Standard 10, released in 2023.
TOGAF documentation works together as a whole, however it is expected by The Open Group that organizations will customize it during adoption. Choose some elements, customize some, exclude some, and create new ones.
What is Enterprise Architecture framework
- Enterprise architecture framework is a foundational structure which is used for developing range of technology architectures for organizations. Framework is usually tailored to meet the specific needs of the organization, including common vocabulary used within such organization.
Executive Overview
- Why is an Enterprise Architecture needed?
- Why use the TOGAF Standard as a framework for Enterprise Architecture?
The TOGAF Standard considers an "enterprise" to be any collection of organizations that have common goals.
According to TOGAF, the purpose of Enterprise Architecture is to optimize fragmented enterprise legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.
Good Enterprise Architecture enables you to achieve the right balance between business transformation and continuous operational efficiency.
There are multiple reasons for embarking on an Enterprise Architecture review or development, including:
- Business-driven initiatives to leverage digital services and products as revenue generating assets
- Technology-driven initiatives for efficiency and cost reduction
- Merger or acquisition, where the return on investment is only realized after technology efficiencies are realized
- To get the best benefit from Enterprise Architecture it should be done early and throughout the change process. To help decision-makers understand the implications of their decisions. Without this, costly mistakes can be made. Enterprise Architecture done after decisions are made becomes merely documentation of those decisions or at best enforcement.