TOGAF 9.1 Series — ADM Phase — D — Technology Architecture

Have you ever heard of TOGAF and never really understood it? In my TOGAF 9.1 series of articles, I will give you summary points what TOGAF is and what you will learn in TOGAF.

I have written the TOGAF exam a while back. I thought that writing this series will let me review the TOGAF content and believe that it would be valuable to others. It is always a good practice to regularly review the contents of a topic that you have learned.

I’m not going to rewrite the official TOGAF books content in my article series. Some sections will only contain bullet points of key terms used in TOGAF. Always reference the official TOGAF book for more details.

Legal Points

TOGAF is a trademark of The Open Group. They maintain the TOGAF standard and release new versions of the framework. I highly recommend that you read the official website and content of TOGAF on the official site: http://www.opengroup.org/subjectareas/enterprise/togaf

The contents in my article series are my opinions and in no way reflects the views of The Open Group.

If you are interested in learning all the finer details of TOGAF or want to write the exam then buy the official book:

Figure 1: TOGAF Version 9.1 book

ADM Phase — D — Technology Architecture

Objectives

  • Develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholders concerns.
  • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architecture.

Steps

  • Select reference models, viewpoints, and tools.
  • Develop Baseline Technology Architecture Description.
  • Develop Target Technology Architecture Description.
  • Perform gap analysis.
  • Define candidate roadmap components.
  • Resolve impacts across the Architecture Landscape.
  • Conduct formal stakeholder review.
  • Finalize the Technology Architecture.
  • Create Architecture Definition Document.

Inputs

  • Request for Architecture Work
  • Business principles, business goals and business drivers
  • Capability Assessment
  • Communications Plan
  • Organizational Model of Enterprise Architecture
  • Technology principles
  • Tailored Architecture Framework
  • Application principles
  • Statement of Architecture Work
  • Architecture principles, including business principles
  • Architecture Repository
  • Architecture Vision

Draft Architecture Definition Document

  • Baseline Business Architecture (detailed)
  • Baseline Data Architecture (detailed)
  • Baseline Application Architecture (detailed)
  • Baseline Technology Architecture (high level)
  • Target Business Architecture (detailed)
  • Target Data Architecture (detailed)
  • Target Application Architecture (detailed)
  • Target Technology Architecture (high level)

Draft Architecture Requirements Specification including:

  • Gap analysis results
  • Relevant technical requirements

Business, Data and Application Architecture components of an Architecture Roadmap

Outputs

  • Statement of Architecture Work, updated if necessary.
  • Validated technology principles or new technology principles

Draft Architecture Definition Document containing content updates:

  • Baseline Technology Architecture (detailed)
  • Target Technology Architecture (detailed)
  • Technology Architecture Views corresponding to selected viewpoints addressing key stakeholder concerns.

Draft Architecture Requirements Specification including content updates:

  • Gap analysis results
  • Requirements output from Phases B and C
  • Constraints on the Technology Architecture
  • Updated technology requirements

Technology Architecture components of an Architecture Roadmap


Originally published at cecilblog.com on March 16, 2016.