The Open Group Architecture Framework (TOGAF) - Revision history

User at 20:41, 30 September 2025

2025-09-30T20:41:33Z

User at 23:35, 2 July 2024

2024-07-02T23:35:55Z

User at 23:34, 2 July 2024

2024-07-02T23:34:26Z

User at 16:32, 27 June 2024

2024-06-27T16:32:18Z

User at 16:36, 21 April 2023

2023-04-21T16:36:03Z

User at 16:14, 21 April 2023

2023-04-21T16:14:05Z

User at 15:32, 14 March 2023

2023-03-14T15:32:40Z

User at 22:43, 18 January 2023

2023-01-18T22:43:12Z

Show changes

User at 22:29, 18 January 2023

2023-01-18T22:29:08Z

User at 13:43, 22 December 2022

2022-12-22T13:43:26Z

@@ Line 66: / Line 66: @@
 *[[Business Transformation]] - TOGAF supports business transformation efforts.
 *[[Capability Maturity Model (CMM)]] - Often used alongside TOGAF to assess and improve an organization's architecture capabilities.
-*[[IT Strategy (Information Technology Strategy)]] - TOGAF helps align IT strategy with business goals.
+*[[IT Strategy (Information Technology Strategy)|IT Strategy]] - TOGAF helps align IT strategy with business goals.
 *[[Business Process Management (BPM)]] - Relevant as TOGAF includes processes for aligning IT with business processes.
 *[[Solution Architecture]] - TOGAF addresses the development of solution architectures.

@@ Line 62: / Line 62: @@
 *[[Architecture Development Method (ADM)]] - A core part of TOGAF, providing a step-by-step approach to developing an enterprise architecture.
 *Architecture Framework - A broader category under which TOGAF falls.
 *[[Information Systems Architecture (ISA)]] - Another key domain in TOGAF.
-*Technology Architecture - Also a key domain in TOGAF.
+*[[Enterprise Architecture Governance]] - TOGAF includes guidance on governance of the architecture process.
 *[[Business Transformation]] - TOGAF supports business transformation efforts.
 *[[Capability Maturity Model (CMM)]] - Often used alongside TOGAF to assess and improve an organization's architecture capabilities.

@@ Line 58: / Line 58: @@
 ===See Also===
 *[[Enterprise Architecture Framework]]
 *[https://cioindex.com/reference/togaf-vs-zachman/ TOGAF vs Zachman Framework]

← Older revision		Revision as of 16:32, 27 June 2024
Line 58:		Line 58:
	===See Also===		===See Also===
	*[[Enterprise Architecture Framework]]		*[[Enterprise Architecture Framework]]
		+	*[https://cioindex.com/reference/togaf-vs-zachman/ TOGAF vs Zachman Framework]

@@ Line 73: / Line 73: @@
 *[https://cioindex.com/reference/introduction-to-togaf-9/ Introduction to TOGAF 9]
 *[https://cioindex.com/reference/e-book-a-guide-to-enterprise-architecture-planning-using-togaf/ e-BooK – A Guide to Enterprise Architecture Planning Using TOGAF]
-*[https://cioindex.com/index/togaf/ References on TOGAF]
+*[https://cioindex.com/references/togaf/ References on TOGAF]

@@ Line 29: / Line 29: @@
 *[[Applications Architecture]]: a blueprint for structuring and deploying application systems and in accordance with business goals, other organizational frameworks and all core business processes.
 *[[Data Architecture]]: defining the organization’s data storage, management and maintenance, including logical and physical data models.
-*[[Information_Technology_Architecture|Technical Architecture]]: also called technology architecture; it describes all necessary hardware, software and IT infrastructure involved in developing and deploying business applications.
+*[[IT Architecture|Technical Architecture]]: also called technology architecture; it describes all necessary hardware, software and IT infrastructure involved in developing and deploying business applications.

← Older revision		Revision as of 15:32, 14 March 2023
Line 57:		Line 57:

	===See Also===		===See Also===
−		+	*[[Enterprise Architecture Framework]]

← Older revision		Revision as of 22:29, 18 January 2023
Line 57:		Line 57:

	===See Also===		===See Also===
−	~~[[Enterprise_Architecture\|Enterprise Architecture]]<br />~~	+
−	~~[[Adaptive_Enterprise_Framework_(AEF)\|Adaptive Enterprise Framework (AEF)]]<br />~~
−	~~[[Enterprise_Architecture_Framework\|Enterprise Architecture Framework]]<br />~~
−	~~[[Federal_Enterprise_Architecture_Framework_(FEA)\|Federal Enterprise Architecture Framework (FEA)]]<br />~~
−	~~[[Zachman_Framework\|Zachman Framework]]<br />~~
−	~~[[Department_of_Defense_Architecture_Framework_(DoDAF)\|Department of Defense Architecture Framework (DoDAF)]]<br />~~
−	~~[[Technical_Architecture_Framework_for_Information_Management_(TAFIM)\|Technical Architecture Framework for Information Management (TAFIM)]]<br />~~
−	~~[[Enterprise_Architecture\|Enterprise Architecture]]<br />~~
−	~~[[Architectural_Style\|Architectural Style]]<br />~~
−	~~[[Architectural_Pattern\|Architectural Pattern]]<br />~~
−	~~[[Architectural_Principles\|Architectural Principles]]<br />~~
−	~~[[Architectural_Risk\|Architectural Risk]]<br />~~
−	~~[[Architecture\|Architecture]]<br />~~
−	~~[[Architecture_Description_Language_(ADL)\|Architecture Description Language (ADL)]]<br />~~
−	~~[[Architecture_Development_Method_(ADM)\|Architecture Development Method (ADM)]]<br />~~
−	~~[[Service_Oriented_Architecture_(SOA)\|Service Oriented Architecture (SOA)]]<br />~~
−	~~[[Software_Architecture\|Software Architecture]]<br />~~
−	~~[[COBIT_(Control_Objectives_for_Information_and_Related_Technology)\|Control Objectives for Information and Related Technology (COBIT)]]<br />~~
−	~~[[ITIL_(Information_Technology_Infrastructure_Library)\|Information Technology Infrastructure Library (ITIL)]]~~
−	~~[[IT Strategy (Information Technology Strategy)\|Strategic Planning for Information Technology]]~~
−	~~[[IT Governance\|Governance of information technology]]~~

@@ Line 40: / Line 40: @@
 '''TOGAF Version 9.2 - Changes and Improvements'''<ref>TOGAF Version 9.2 - Changes and Improvements [https://www.itpreneurs.com/blog/more-focus-on-business-architecture-in-togaf/ ITpreneurs]</ref><br />
-The TOGAF [[standard]], version 9.2 brings a number of changes and improvements. An important change is the [[restructuring]] of TOGAF into a core and a number of additional guides, which together form the TOGAF Body of Knowledge. A general change is the refinement of the terminology, including the alignment with the ISO/IEC/IEEE 42010:2011 standard and other standards. The most interesting change is the enrichment of the business architecture part of TOGAF with business capabilities and value streams. These additions move TOGAF further away from the IT focus it had in the past. In this [[blog]], I’ll further describe these two additions. The most interesting change is the enrichment of the business architecture part of TOGAF with business capabilities and value streams.
+The TOGAF [[standard]], version 9.2 brings a number of changes and improvements. An important change is the [[restructuring]] of TOGAF into a core and a number of additional guides, which together form the TOGAF Body of Knowledge. A general change is the refinement of the terminology, including the alignment with the ISO/IEC/IEEE 42010:2011 standard and other standards. The most interesting change is the enrichment of the business architecture part of TOGAF with business capabilities and value streams. These additions move TOGAF further away from the IT focus it had in the past. In this blog, I’ll further describe these two additions. The most interesting change is the enrichment of the business architecture part of TOGAF with business capabilities and value streams.
 *[[Business_Capability|Business Capabilities]]: Business capabilities are not entirely new in TOGAF; the capability-based planning technique was already part of the previous version. In the new version business capabilities get even more focus and attention. This starts with more clarity on terminology, with a clear distinction between capabilities and business capabilities. A capability refers to an ability that an organization, person or [[system]] possesses. A business capability is a particular ability that a business may possess or exchange to achieve a specific purpose. A capability is thus a more general term, and also includes IT and architecture capabilities. A capability-based view of architecture puts emphasis on what the business needs in order to achieve its [[goals]]. It requires identifying, categorizing, and decomposing the business capabilities required for the business to have the ability to deliver value to one or more stakeholders. A business capability map is introduced to provide a self-contained view of the business that is independent of the current [[Organizational Structure|organizational structure]], business processes, and [[Information System (IS)|information systems]]. It provides a level of abstraction that the organization understands, and is thus a very appropriate way to talk with people about the changes that are needed.
 *[[Value_Streams|Value Streams]]: Value streams are totally new in TOGAF. A value stream is a representation of an end-to-end collection of value-adding activities that create an overall result for a [[customer]], [[stakeholder]], or end user. They are a result of a breakdown of activities that an organization performs to create the value being exchanged with stakeholders. They provide context and a grouping for the business capabilities. They provide valuable stakeholder context into why the organization needs these business capabilities. For every stage in the value chain, the business capabilities that are needed can be identified. The result can be depicted in a new artifact called a value stream stages catalog. Value streams have the same advantages as business capabilities in terms of easy communication with business stakeholders. They enable communication in business terminology, in terms of things that people recognize. They can be refined into processes at a later stage. Similarly, they can be translated together with the business capabilities in an organization structure. An organization map can be used to show how the organization relates to the business capabilities and thus also to the value stream stages.