Archive for March, 2011

Building blocks of an IT architecture roadmap

Thursday, March 17th, 2011

After describing how to build an IT architecture roadmap I focus on the building blocks of an IT architecture roadmap in this blog and a series of subsequent blogs.

Below you find an overview of the building blocks of an IT architecture roadmap

IT Architecture Components

The colouring indicates that there are four types of building blocks

  • Readiness
  • Preparation
  • Core
  • Execution

IT architecture readiness

There is only one building block in the IT architecture readiness area. It is an assessment on how mature your organization is in regards of IT architecture in comparison to where you would like it to be. For each assessed perspective of IT architecture the result looks similar to the one below

IT Architecture Readiness

The perspectives usually assessed are

  • Business
  • IT-Skills
  • IT-Technology
  • IT-Processes

IT architecture preparation

There are two building blocks in the IT architecture preparation area

  • IT architecture vision
  • IT architecture strategy

They are separated from the core IT architecture building blocks because they are on a higher level in the IT architecture pyramid and often a given to the IT architecture roadmap project. If not provided they are derived from the respective business vision and strategy.

IT architecture core

The core building blocks of any IT architecture roadmap are

Logical IT architecture

The logical IT architecture is about business and technology solutions in comparison to the physical IT architecture that is about systems. To start with this building block the logical as-is IT architecture is assessed and gap-fit analysed. Building on the IT architecture principles and IT architecture patterns the to-be logical IT architecture is then designed.

Physical IT architecture

The physical IT architecture building block turns the logical architecture into a system landscape. Typically evaluations help decisions on instance distribution, EIM hierarchies and physical integration.

IT architecture timeline

This last core building block combines the physical to-be IT architecture with on-going projects and other constraints, defines IT initiatives and places them on a timeline.

IT architecture execution

This IT architecture area with only one building block is separated from the core building blocks because IT architecture plays only a supporting role within it. IT architecture execution happens within the projects that implement the IT initiatives defined in the IT architecture timeline building block. There IT architects ensure that the IT architecture principles are understood and applied as well as the IT architecture patterns. Most important however is the IT architecture exception process that allows for deviations from the IT architecture principles and IT architecture patterns and thereby indicates necessary improvements of the IT architecture roadmap.

How to build an IT architecture roadmap

Tuesday, March 8th, 2011

In my blog about the business case for IT architecture I did not describe in detail how to build such a roadmap. Therefore this is the topic of this blog. As you can see from the flow chart below, building an IT architecture could be a laborious task if you had to start from scratch

IT Architecture Roadmap

Fortunately some of the yellow deliverables are usually already present so not all of the red roadmap process steps would necessarily have to be performed.

The necessary starting point of an IT architecture roadmap according to the IT architecture pyramid below are your company’s business and IT vision

IT architecture pyramid

More often than not these have been developed prior to the IT architecture roadmap endeavour and therefore serve as the starting point. If not or if they needed updating both visions would have to be formulated for which there is no easy or straightforward process since they lay the foundation for your company’s future success.

From the business and IT vision you will then develop your IT strategy if it does not exist yet or needs updating. A best practise way to come up with a sound IT strategy is a strategy workshop with the IT leadership team. You could do that on your own or with the help of an external moderator.

To support your IT strategy you would then formulate your IT architecture principles. Those will be derived from your IT strategy and should cover the following areas according to TOGAF Version 9

  • Business Principles
  • Data Principles
  • Application Principles
  • Technology Principles

From there you develop your IT architecture patterns which are designed to help your organization adhering to the IT architecture principles in that they give guidance what to do in a certain situation, i.e. when a certain pattern occurs.

With these guard rails in place you start the development of your logical IT architecture. Good starting points for this are heat maps that map your existing logical applications to the businesses processes they support. That will give you insight into white spots and areas of possible consolidation leading to your to-be logical IT architecture applying your IT architecture patterns and therefore in accordance with your IT architecture principles.

From there you are able to create your physical IT architecture taking into account non-functional requirements and technical considerations as well.

Placing all the changes that need implementation from your to-be physical IT architecture onto a time line while considering all possible dependencies leads to your final IT architecture roadmap which you can then start executing on.