Part 2. TOGAF and Architecture Roadmaps
The Open Group Architecture Framework is a widely used standard for Enterprise Architecture practices. It is important to refer to it, when developing a practice for architecture roadmaps. Roadmaps are very important and referred through many of the TOGAF process called the Architecture Development Method (“ADM”), yet there is very little describing how we should build the roadmaps and standards how to structure the roadmaps.
In any endeavor, it is useful to start with first principles, before drilling into the detail. The following is the essence of TOGAF, to define the Business, Application, Information, and Technology architecture layers, along with the drivers of the Business Model and the ultimate output of the projects to affect change.
Figure 1 Standard TOGAF Architecture Layers as a Context for a Consolidated Architecture Roadmap
TOGAF does define requirements for what it calls a Consolidated Architecture Roadmap, yet there is little definition about what belongs in it. We will put forward a simple definition of what belongs in it. In some ways, TOGAF is open by design since it assumes that each company will have different objectives about what belongs here.
TOGAF describes the following requirements for a Consolidated Architecture Roadmap1.
- The Architecture Roadmap lists individual increments of change
- Lays them out on a timeline to show progression from the Baseline Architecture to the Target Architecture.
- The Architecture Roadmap forms a key component of Transition Architectures
- Is incrementally developed throughout TOGAF ADM Phases B, C, D, E, and F within the ADM.
For more information on TOGAF and the TOGAF Architecture Development Method (ADM), refer to http://www.opengroup.org/architecture/togaf9-doc/arch/ .
The following is a proposal for a simple structure for a Consolidate Architecture Roadmap that “rolls-up” the most important object that summarizes each layer of the architecture and rolls up each of the relevant phases in the TOGAF ADM for a Consolidate Architecture Roadmap.
Figure 2 Proposed Standard Layers of a Consolidated Architecture Roadmap
So, how would that look like if you had a consolidated roadmap, summarizing each of these layers? In future blogs, we will go over an example of the Consoldiated Architecture Roadmap and drill down into each layer. A major assumption is that each layer may drill down to additional roadmaps that show supporting details and possibly additional objects that build up to the objects on the Consolidated Roadmap. For example, Capabilities on a Consolidated Architecture Roadmap should point to details about the Goals, Drivers, Objectives, and Measures that necessitated these capabilities to be included on the Consolidated Architecture roadmap. Ideally, you should be able to drill down on the rationale for the capabilities that appear in the Consolidated Architecture Roadmap. We will discuss this in more detail as we go through an example.
- There is a need for a more detailed Consolidated Architecture Roadmap guideline
- Consolidated Architecture Roadmap should include 5 Basic Layers corresponding to the TOGAF ADM Phases A through E
- o Business Model, Business, Information System, Technology, and Work Packages
- Detailed Roadmaps May Be Required for Each Layer
- Rollup each layer with Key Object i.e. Business Operating Model -> Competencies
Stay tuned to Part 3, when we drill down into the first layer of a Consolidated Architecture Roadmap or the Business Operating Model Layer. Then, we will show how it rolls back up to the Consolidated Architecture Roadmap.
1The Open Group Architecture Framework, Open Group, 2009
This blog is based on the ASUG Enterprise Architecture Roadmap Days. Be sure to attend one of the events coming to a city near you. The next even is in Atlanta on November 4th.
Also, there is a Roadmap Preconference Session at TechEd 2010 in Las Vegas. You will meet with more of the though leaders who have developed the SAP product roadmaps and meet with your colleagues who are developing best in class company architecture roadmaps.