Introduction to TOGAF – Part 1

In this article I will try to give an overview on one of the Main Enterprise Architecture Frameworks – TOGAF.

The objective of this series is to provide a holo-view on the importance of TOGAF

  • Introduction to TOGAF

    • An Open Group Standard
    • Is a proven enterprise architecture methodology and framework used by the world’s leading organizations to improve business efficiency
    • First developed in 1995
    • TOGAF was based on the US Department of Defense Technical Architecture Framework for Information Management (TAFIM).
    • TOGAF 9.1 can be used for developing a broad range of different enterprise architectures.
    • TOGAF complements, and can be used in conjunction with, other frameworks that are more focused on specific deliverables for particular vertical sectors such as Government, Telecommunications, Manufacturing, Defense, and Finance.
  • Architecture in the context of TOGAF

    • ISO/IEC 42010:20071 defines “architecture” as: “The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.”
    • In TOGAF, “architecture” has two meanings depending upon the context:


  • A formal description of a system, or a detailed plan of the system at a component level to guide its implementation
  • The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time


  • TOGAF deals with the following architectures

    • Covers the development of four related types of architecture
      • Business Architecture

        • The business strategy, governance, organization, and key business processes.
      • Data Architecture

        • The structure of an organization’s logical and physical data assets and data management resources.
      • Application Architecture

        • A blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization.
      • Technology Architecture

        • The logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, and standards.
  • Structure of the TOGAF Standard

    • TOGAF is divided into 7 parts, as follows:
      • Part I: Introduction

        • provides a high-level introduction to the key concepts of enterprise architecture and, in particular, to the TOGAF approach,
        • contains the definitions of terms used throughout TOGAF,
        • Contains release notes detailing the changes between this version and the previous version of TOGAF.
      • Part II: Architecture Development Method

        • is the core of TOGAF
        • describes the TOGAF Architecture Development Method (ADM) approach to developing an enterprise architecture.
      • Part III: ADM Guidelines and Techniques

        • contains a collection of guidelines and techniques available for use in applying the ADM
      • Part IV: Architecture Content Framework

        • describes the TOGAF content framework
        • including a structured meta-model for architectural artifacts,
        • the use of re-usable Architecture Building Blocks (ABBs),
        • an overview of typical architecture deliverables.
      • Part V: Enterprise Continuum and Tools

        • discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise.
      • Part VI: TOGAF Reference Models

        • provides two architectural reference models
          • TOGAF Technical Reference Model (TRM)
          • The Integrated Information Infrastructure Reference Model (III-RM)
      • Part VII: Architecture Capability Framework

        • discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture practice within an enterprise
  • What does TOGAF Contain

    • TOGAF reflects the structure and content of an architecture capability within an enterprise
  • Architecture Development Method (ADM)TOGAF-ADM

    • describes how to derive an organization-specific enterprise architecture that addresses business requirements.
    • is the major component of TOGAF
    • provides guidance for architects on a number of levels:
      • provides a number of architecture development phases in a cycle
        • Business Architecture
        • Information Systems Architectures
        • Technology Architecture)
      • Provides an overall process template for architecture development activity.
    • provides a narrative of each architecture phase,
      • describing the phase in terms of objectives, approach, inputs, steps, and outputs.
        • The inputs and outputs sections provide a definition of the architecture content structure and deliverables
        • detailed description of the phase inputs and phase outputs is given in the Architecture Content Framework


  • ADM Guidelines and Techniques

    TOGAF-ADM Guidelines & Techniques

    provides a number of guidelines and techniques to support the application of the ADM

    • address adapting the ADM to deal with a number of usage scenarios, including different process styles (e.g., the use of iteration) and also specific specialty architectures (such as security).
    • The techniques support specific tasks within the ADM such as
      • defining principles
      • business scenarios,
      • gap analysis,
      • migration planning,
      • risk management.


  • Architecture Content Framework

    TOGAF-Architecture Content Framework

    provides a detailed model of architectural work products including

    • deliverables,
    • artifacts within deliverables,
    • and the Architecture Building Blocks (ABBs) that deliverables represent
  • Enterprise Continuum


    provides a model for structuring a virtual repository

    • provides methods for classifying architecture and solution artifacts
    • showing how the different types of artifacts evolve
    • Showing how different types of artifacts can be leveraged and re-used.
    • is based on architectures and solutions (models, patterns, architecture descriptions, etc.) that exist within the enterprise and in the industry at large
  • TOGAF Reference Models


    provides two reference models for possible inclusion in an enterprise’s own Enterprise Continuum

    • Technical Reference Model (TRM)
    • Integrated Information Infrastructure Model (III-RM).
  • Architecture Capability FrameworkTOGAF-Architecture Capability Framework

    • is a set of resources, guidelines, templates, background information, etc.
    • provided to help the architect establish an architecture practice within an organization.

Business Information Service Library (BiSL) introduction

BiSL is an abbreviation of Business Information Services Library, previously known as Business Information Service Management Library, It is a vendor independent public domain library for the implementation of business information management.

Starting the late 90s, ITIL® (IT Infrastructure Library) has been used to improve the maturity of service management processes, particularly in the area of IT infrastructure management. As the maturity level of organizations increases, it has become clear that application management had additional needs; ASL® (Application Services Library) was developed and introduced into the public domain in 2002. Similarly, once it was realized that the demand side of IT also had specific needs that were not addressed sufficiently by existing frameworks, there was a justification for a framework for this domain. Customers of IT organizations had very little focus on their own role and all hopes were set solely on the IT and technology vendors and they were not capable to sufficiently influence the effectiveness and efficiency of IT on their own. The client or demand role is a crucial factor in achieving a situation where IT is worth money spent.

The framework describes a standard for processes within business information management at the strategy, management and operations level. BISL is closely related to the ITIL and Application Service Library (ASL) frameworks, while the main difference between these frameworks is that ITIL and ASL focus on the supply side of information (the purpose of an IT organization), whereas BISL focuses on the demand side (arising from the end-user organization)

Based on separation of duties, Information Delivery can be divided in two main areas:

  • IT Managementrepresenting ‘Supply’

IT Management is the domain that builds and runs the information systems. It is composed of various disciplines, including Systems Management, Application Management (framed by ASL), Facility and Infrastructure Management, and IT Service Management (framed by ITIL).

  • Information Managementrepresenting ‘Demand’

Information Management is the domain that forms the specification of the functional requirements that the IT services have to deliver to the end-users, the management of the corporate data model, and the management of the delivery of IT services by IT management. Information Management is supported by the most recent BISL standard.


  1. IT infrastructure management is responsible for maintaining the operations of the IT infrastructure that is part of the information system. This includes hardware, equipment, networks, software and databases which are the main areas of focus for the computer center or the IT center. ITIL is a much-used framework in this context.
  2. Application management is responsible for maintaining the application software and the databases. Application management corresponds to the operation of a software company: the creation, maintenance and renovation of software applications. ASL (Application Services Library) is the standard for organizing application management.
  3. Business information management on behalf of the business and user organization is responsible for maintaining the functionality of the information systems. This section concentrates on the provision of information to support the organization and its business processes.