TOGAF

The Open Group Architecture Framework (TOGAF) is a framework for developing an enterprise architecture for use within that organisation. TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. It is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.
Like many other frameworks in the IT architecture and management arena TOGAF 9.1 is not a  "use it right out of the box item". It has some 690 pages and is first of all a major challenge to read. Also, like many other IT frameworks, TOGAF will tell you more about WHAT to do than HOW to do it. Hence, when you start e.g. a new job as an Enterprise Architect and somebody passes you a copy of TOGAF 9.1 you might not really know what to do, unless you have had some other work experience besides TOGAF and have read a few other books.
There is also the criticism that TOGAF does not provide you with working examples, document templates and other quickstart tools. Providing such material would indeed be very tough, as processes, documents and other material will differ depending on the kind of enterprise for which you have to develop an architecture. The good news is that TOGAF provides you with very useful checklists and very extensive meta models. The bad news is, that TOGAF will not provide you with an idiot’s guide to Enterprise IT Architecture. If you are new to the field of enterprise architecture and/or TOGAF, you are recommended to read the:

• What is enterprise architecture?
• Why do I need an enterprise architecture?
• Why do I need TOGAF as a framework for enterprise architecture?

Structure of the TOGAF Document

The structure of the TOGAF documentation reflects the structure and content of an architecture capability within an enterpr ise, as shown in Figure tg.01

Figure tg.01 Structure of the TOGAF Document



There are seven main parts to the TOGAF document:

• PART I (Introduction). This part provides a high-level introduction to the key concepts of enter prise architecture and in particular the TOGAF approach. It contains the definitions of terms used throughout TOGAF and release notes detailing the changes between this version and the previous version of TOGAF.
• PART II (Architecture Development Method). This part is the core of TOGAF. It descr ibes the TOGAF Architecture Development Method (ADM) — a step-by-step approach to developing an enterpr ise architecture.
• PART III (ADM Guidelines and Techniques). This part contains a collection of guidelines and techniques available for use in applying TOGAF and the TOGAF ADM.
• PART IV (Architecture Content Framework). This part descr ibes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable architecture building blocks, and an overview of typical architecture deliverables.
• PART V (Enter prise Continuum & Tools). This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise.
• PART VI (TOGAF Reference Models). This part provides a selection of architectural reference models, which includes the TOGAF Foundation Architecture, and the Integrated Infor mation Infrastr ucture Reference Model (III-RM).
• PART VII (Architecture Capability Framework). This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture function within an enterprise.

The intention of dividing the TOGAF specification into these independent parts is to allow for different areas of specialization to be considered in detail and potentially addressed in isolation. Although all parts wor k together as a whole, it is also feasible to select particular parts for adoption whilst excluding others. For example, an organization may wish to adopt the ADM process, but elect not to use any of the materials relating to architecture capability.
As an open framework, such use is encouraged, particular ly in the following situations:

• Organizations that are new to TOGAF and wish to incrementally adopt TOGAF concepts are expected to focus on particular parts of the specification for initial adoption, with other areas tabled for later consideration.
• Organizations that have already deployed architecture frameworks may choose to merge these frameworks with aspects of the TOGAF specification.

Related Posts :
Enterprise Architecture
Architecture Development Method
Architecture Content Framework