TOGAF Terminology - A Comprehensive Guide 

TOGAF is a well-proven framework established for enterprise architecture to improve business efficiency and effectiveness. Before diving deep into the actual concept, it is crucial for aspirants to understand the key TOGAF Terminology involved.

According to CIO, by 2016, at least 80% of Global 50 and 60% of Fortune 500 organisations make use of TOGAF. To implement TOGAF effectively, companies need to have a complete understanding of the key technical terms and components involved.  

In this comprehensive glossary, we will explore in detail the key TOGAF Terminology and their definitions. Read ahead to learn more! 

Table of Contents 

1) TOGAF Terminology: Defined   

    a) Application 

    b) Architecture 

    c) Architecture Framework 

    d) Architecture Principles 

    e) Architecture Landscape 

    f) Architecture Building Blocks (ABB) 

    g) Architecture Model 

    h) Architecture View 

    i) Architecture Viewpoint 

    j) Architecture Vision 

2) Conclusion 

TOGAF Terminology: Defined 

Listed below are the key terminology involved in TOGAF, along with their definitions: 

1) Application 

Definition: In the context of TOGAF, an application is a software system designed to provide specific functionality or services to end-users. It typically consists of multiple software components or modules that work together within an enterprise computing environment.  

2) Architecture 

Definition: According to TOGAF, architecture can be defined in two ways: 

a) The inter-relationships and structure of components of a system, along with the guidelines and principles that govern the structure and relationships.  

b) The detailed formal description of a TOGAF system at the component level, which provides direction for its implementation
 

 

3) Architecture Framework 

Definition: An architecture framework is a set of methods, tools and practices for developing and managing enterprise architectures. It consists of four key components: 

a) Architecture Development Model (ADM) 

b) Enterprise Continuum 

c) Architecture Content Framework 

d) Architecture Capability Framework 

4) Architecture Principles 

Definition: Architecture principles are a set of guiding statements used by enterprise architects to inform real-time decisions. These principles are established and ranked based on their importance to the project, and they provide a fixed framework for making architectural choices. 

5) Architecture Landscape 

Definition: Architecture Landscape refers to a structured representation of the organisation’s architecture, assets, and the desired future state. It encompasses the applications, data, technology, and business architecture models that provide a holistic view of the organisation’s current and planned architecture. 

6) Architecture Building Blocks (ABB) 

Definition: Architecture Building Blocks (ABBs) are the fundamental components of an architecture that can be combined to create solutions. The Architecture Landscape encompasses the ABBs that are used in the organisation’s architecture, representing the building blocks that form the basis for the organisation’s overall architecture. 

7) Architecture Model 

Definition: An architecture model is a conceptual representation of an organisation’s architecture. It serves as a structured approach to organise and understand the various components of an enterprise architecture, including its business processes, data, applications, and technology infrastructure. It provides a visual and conceptual framework for describing the organisation's architecture and how its components interact with each other. 

8) Architecture View 

Definition: An architecture view is a representation of a specific aspect of an overall architecture. It provides stakeholders with a structured way to understand and analyse the architecture from a particular perspective. It offers a focused and organised view of relevant architecture components, relationships, and characteristics, allowing stakeholders to gain insights into specific aspects of the architecture and make informed decisions accordingly. 

9) Architecture Viewpoint 

Definition: An architecture viewpoint is a specific way of examining the entire architecture from a particular perspective. It provides a structured framework for understanding, analysing, and communicating various aspects of the specific architecture to the stakeholders involved. It offers a consistent and organised approach to examining the architecture from a particular viewpoint, enabling effective communication and collaboration among stakeholders with different areas of expertise and interests. 

10) Architecture Vision 

Definition: Architecture Vision is a high-level description of the objectives, goals, and outcomes of an enterprise architecture initiative. It outlines the desired future state of the enterprise, including its business, information, application, and technology architectures, and describes how these will be transformed over time to achieve the desired outcomes. It serves as a strategic direction for the enterprise architecture, providing a clear and compelling vision of the intended state and guiding the development and evolution of the architecture to align with the organisation's overall goals and objectives. 

11) Baseline 

Definition: In the context of TOGAF, a baseline refers to a snapshot or a description of an organisation’s architecture at a specific point of time. A baseline serves as a reference point that captures the current state of an organisation’s architecture in terms of its components, their relationships, and how they work together to support business goals and objectives. It provides a documented representation of the existing architecture, serving as a starting point for analysing, comparing, and evaluating changes and improvements to the architecture over time. 

12) Building Block 

Definition: A building block is a modular unit of architecture that can be combined with other building blocks to create a complete solution or system. Building blocks represent discrete pieces of functionality or capability that can be implemented and reused across different parts of the architecture. They are designed to be independent of other building blocks, with well-defined interfaces and dependencies that allow for easy integration. Building blocks provide a modular and scalable approach to designing and implementing architecture, enabling flexibility, reusability, and interoperability across the architecture landscape. 

13) Business Capability 

Definition: A business capability is a specific set of activities or functions that an organisation needs to perform in order to achieve its business goals and objectives. It represents a higher-level view of an organisation’s activities than a business process and describes what an organisation does rather than how it does it. Business capabilities provide a holistic perspective of an organisation's business functions, representing its core competencies, strengths, and areas of expertise. They serve as a foundation for understanding and analysing an organisation's business requirements and aligning them with its strategic goals and objectives. 

14) Business Function 

Definition: A business function is a specific set of activities or tasks that an organisation performs to achieve a particular business outcome. It is a lower-level view of an organisation’s activities, focusing on business processes. Additionally, it describes how an enterprise conducts its operations instead of what it does. Business functions provide a detailed view of the operational activities within an organisation and how they are interconnected to achieve business goals and objectives. They are typically organised into functional areas, such as finance, human resources, marketing, operations, and sales, and serve as the building blocks for defining business processes and activities within an enterprise architecture framework. 

15) Business Model 

Definition: A business model is a high-level representation of how an enterprise creates value for its stakeholders and how it generates its revenue and profits. It describes the key elements of an organisation’s business strategy, including its value proposition, target customers, revenue streams, cost structure, and competitive advantage. Business models provide a holistic view of an organisation's overall approach to doing business, capturing its unique value proposition, market positioning, and revenue generation mechanisms. They serve as a foundation for understanding and analysing an organisation's business operations and help in aligning its strategic goals and objectives with its value proposition and competitive advantage in the market. 

16) Capability Increment 

Definition: A capability increment is a planned set of changes to an organisation’s capabilities that are designed to achieve a specific business goal or objective. It represents an iterative and incremental approach to building and improving an organisation’s capabilities, with each increment helping to build on the previous one.  

17) Concern 

Definition: In the context of TOGAF, a concern is a specific area of focus or interest within an organisation’s architecture. A concern can be thought of as a particular viewpoint or perspective that is applied to the architecture to address a specific set of set of queries or issues raised by the stakeholders involved. 

18) Course of Action 

Definition: A course of action is a plan or strategy that outlines the steps required to achieve a specific set of goals or objectives within an organisation’s architecture. It typically involves a series of steps, such as: 

a) Identifying the desired outcomes  

b) Assessing the current state of architecture 

c) Defining the target state 

d) Identifying the specific initiatives that are required to achieve the target state 

19) Deliverable 

Definition: A deliverable is a tangible outcome or result of an architecture activity that is meant to be produced, reviewed, and approved as part of a specific phase or iteration of the architecture development process. They are typically created to communicate information, provide guidance, or support decision-making for stakeholders involved in the implementation, development, and maintenance of an enterprise architecture.  

20) Data Architecture 

Definition: Data Architecture is one of the four primary enterprise architecture domains alongside Application, Technology, and Business architectures. It defines the structure, storage, processing, and management of an organisation’s data assets. Additionally, Data Architecture provides a blueprint for how data is collected, processed, and used across the enterprise to support business goals and objectives.  

Obtain in-depth knowledge of the TOGAF concept with our TOGAF® BA Foundation Training course now!   

21) Enterprise 

Definition: According to TOGAF, an enterprise is a complex organisation or system that includes people, information, processes, and technology, and operates within a particular economic and competitive environment. It can be a public or private organisation, a government agency, or any other type of entity that seeks to achieve specific goals such as creating value for stakeholders, delivering products or services, or fulfilling a social mission.  

22) Enterprise Continuum 

Definition: Enterprise Continuum is a framework that provides a structured way to organise and classify architectural artefacts and deliverables within an enterprise. It is divided into distinct levels of abstraction, each one representing a different degree of detail and scope.  

23) Gap 

Definition: In the context of TOGAF, a gap is a difference between the present state and the desired future state of the enterprise architecture. It represents a deficiency or weakness in the existing architecture that needs to be addressed in order to achieve the desired business outcome.  

Gaps mainly occur due to deficiencies in one of the following architecture domains: 

a) Business 

b) Data 

c) Application 

d) Technology 

This is mainly due to factors such as changes in business requirements, technology obsolescence, lack of alignment between business processes and IT systems, or insufficient data quality.  

24) Governance 

Definition: Governance refers to a set of procedures, policies, and decision-making frameworks that guide and control the management, development, and usage of enterprise architecture. It ensures that the enterprise architecture meets the business objectives, aligns with the organisational strategy, and conforms to the best standards and practices. 

25) Interoperability 

Definition: Interoperability is the ability of different systems, applications, or components to work together in a coordinated and effective way, without any loss or distortion of data or functionality. It is essential for enabling seamless coordination, communication, and collaboration between different functionalities of the enterprise as well as with external stakeholders.  

26) Logical 

Definition: In the context of TOGAF, “logical” refers to the abstract or conceptual representation of a component, process, or system without any consideration of the physical implementation or technology platform.  

27) Metadata 

Definition: Metadata refers to the data that describes other data or information assets in the enterprise. It provides context, meaning, and structure to data and helps to manage and govern the data throughout its lifecycle.  

28) Metamodel 

Definition: Metamodel refers to a model that describes the structure, syntax, semantics, and relationships of other models used in the enterprise architecture. It provides a standard way of representing and defining the elements and relationships of the models, and helps ensure completeness, consistency, and quality of the models.  

29) Objective 

a) Definition: According to TOGAF, an objective is a  

b) Specific,  

c) Measurable, 

d) Achievable, and 

Time-bound target that the enterprise architecture is designed to achieve. Objectives present a clear and concise breakdown of the desired outcomes or results that the architecture intends to deliver and helps to align the architecture with the business goals and priorities.  

30) Repository 

Definition: A repository is a central location or database that stores and manages architecture artefacts and related information in a structured and controlled manner. It provides a secure, scalable, and accessible platform for storing and retrieving information such as standards, models, diagrams, policies, and guidelines.  

31) Service-Oriented Architecture (SOA) 

Definition: Service-Oriented Architecture (SOA) is a design approach that supports the creation of loosely coupled modular applications and systems. It is one of the architecture styles that can be used to implement the SOA Reference Model, which provides a step-by-step approach to developing an enterprise architecture.  

32) Service Portfolio 

Definition: A service portfolio is a catalogue of services that an organisation offers or plans to offer to its customers, partners, or other stakeholders. It is a key component of the SOA approach and provides a structured way to organise, manage, and govern the services offered by an organisation.  

33) Solution Building Block (SBB) 

Definition: A Solution Building Block (SBB) is a modular component that represents a specific capability or functionality that can be used in designing and implementing solutions to address specific business requirements. They can be combined and integrated with each other to create larger, more complex solutions.  

34) Taxonomy of Architecture Views 

Definition: Taxonomy of architecture views is a way of categorising and organising the different types of views that are used in enterprise architecture. It has four broad categories: 

a) Business Architecture Views 

b) Data Architecture Views 

c) Application Architecture Views 

d) Technology Architecture Views 

35) Technology Component 

Definition: In the context of TOGAF, a technology component is a modular unit of hardware, software, or infrastructure that is used to implement technology solutions within an enterprise architecture. It can refer to a single unit of hardware or software application that is crucial to the architecture of the organisation.  

36) Value Stream 

Definition: A value stream refers to a sequence of activities that is required to deliver a specific product, service or outcome to a customer or stakeholder. It is a key concept in the business architecture domain of enterprise architecture, and is responsible for defining the capabilities, goals, value additions, business strategy, and processes in the organisation.  

37) View 

Definition: In context with TOGAF, a view is a representation of an aspect of an architecture that is intended for a particular set of stakeholders. It is typically created as a customisable model of the architecture to demonstrate to the stakeholders and alleviate their concerns about the architecture.  

38) Viewpoint 

Definition: A viewpoint is a specific perspective or view of an enterprise architecture that is designed to communicate information about the complete architecture to a particular set of stakeholders. Viewpoints are key concepts in the architecture development process as they help define the requirements and solutions to the stakeholders involved.  

Conclusion 

To wrap it up, understanding the key TOGAF Terminology is crucial for organisations that want to implement a successful enterprise architecture practice. These terms provide a common language and framework for stakeholders to collaborate, communicate, and facilitate the development of a complex architectural structure that aligns with the business objectives. Mastery of the TOGAF Terminology can also aid in the selection of the right tools and techniques needed for the governance and refinement of the architecture.   

Understand more about the structure of the TOGAF Standards with our TOGAF® Essentials course now!