TOGAF Is the fastest growing adopted framework for enterprise architecture. Thousands of people per year are getting TOGAF certified (50,000+ to-date worldwide) and it has become the standard for enterprise architecture practices around the world.

We have been actively involved with applying TOGAF since 2006 (TOGAF version 7) and have helped numerous organizations adopt & implement enterprise architecture TOGAF. The purpose of this section is to share some of our experiences with enterprise architecture TOGAF, give people some tips and share our lessons learned.

Notification

Icon
Error

    TOGAF Overview

TOGAF is an EA Framework really an EA tool with a step-by-step procedure for development of enterprise architecture. The tool can be downloaded for free from the Open Group website.

TOGAF Goals
TOGAF has become a standard in enterprise architecture and a proven way for quicker and effective enterprise architecture development. This highly scalable framweork can be used by both big and small companies without exceptions. When it comes to the different levels of enterprise architecture a framework could support, TOGAF supports all levels from technology architecture to enterprise business architecture.

The Framework
TOGAF consists of these areas:

- An architectural development method (ADM)
- The enterprise continuum (theoretical base)
- A technical reference model (TRM)
- Standard information base (SIB)

We'll review each tool individually in the article.

Architectural Development Method
The architectural development method is a set of detailed instructions with step by step explanation on how to form, maintain and implement enterprise architecture. It has 8 different phases:

- Phase A - Architecture Vision
- Phase B - Business Architecture
- Phase C - Information System Architecture
- Phase D - Technology Architecture
- Phase E - Opportunities and Solutions
- Phase F - Migration Planning
- Phase G - Implementation Governance
- Phase H - Architecture Change Management

Requirements
All ADM phases have different requirements. TOGAF does not force a specific way of managing these requirements, it only states what an efficient Requirements Management process should be able to achieve. TOGAF does, on the other hand, contain specific technique for collection and description of requirements called Business Scenarios.

Business Scenarios
This is used to describe a framework in business taxonomy. Business scenarios are used to link the requirements to the enterprise architecture and aid the business process.

The Enterprise Continuum
While ADM describes the process and creates the architecture, the Enterprise Continuum is there to help with the communication and clarity of the company's architecture, by providing language consistency, so that individuals with different perspectives can discuss the same architecture equally.

The Architecture Continuum
The Architecture Continuum incorporates the relations between different architectures. Below is the picture of 4 architecture types that are a part of the Architecture Continuum.

The Solutions Continuum
This part of the Enterprise Continuum contains the implementation of the stages presented in the Architecture Continuum. Below is the picture of 4 corresponding solutions that are a part of the Solution Continuum.

When combined, we get the Enterprise Continuum which contains the relationship between the Solutions Continuum and the Architecture Continuum.


Technical Reference Model (TRM)
The TOGAF TRM contains Architecture taxonomy and a graphical representation of that taxonomy. There are three layers in TRM:

- Application Software contains specific applications and software needed for a particular company.
- Application Platform is a platform needed to run the software. Usually, it is reused in the Technology architecture as the building block.
- Communication Infrastructure is a way to interconnect systems. It can involve networking, online communication, basically, anything that is required to enable communication between applications.


Standards Information Base (SIB)
The SIB lists the standards of informational systems, created by the Open Group and is used for developing architectures. These standards are proven the technology and the biggest part of industry support them, so by using them we can avoid many possible issues with vendors.

Conclusion
Enterprise architecture takes time and money to be successful and there are still a few reasons why EA initiatives fail . Many companies don't get the planned benefits mainly because the management doesn't make an effort to pair the business goals with the architecture goals. With proper planning and TOGAF, your changes to be successful will increase significantly.

keywords: TOGAF, enterprise architecture, enterprise architecture framework, EA tools, TOGAF framework

Enterprise Architecture Software using TOGAF

Why use EAComposer use as your TOGAF Software?

  • Full support for the TOGAF and Archimate, with real-life templates for all 80+ architecture artifacts defined by the ADM. There for you to use.
  • Our repository is fully aligned with the TOGAF Enterprise Continuum meaning you can segregate your architecture content as the Enterprise Continuum outlines.
  • A visual modeler that can produce any TOGAF viewpoint and support all the Archimate notations as well as the flexibility to extend where needed.
  • Supports the TOGAF Governance in a practical, simple but very effective way. Produce monthly alignment assessments in minutes using our unique dashboards.
  • The Free Trial will give you instant and full access to the product & features, after 4 weeks the trial automatically expires. No catches!