IT Architecture Toolkit (Hardcover)

There were two factors that motivated me to write this book. One was that, while those of us who were data geeks were always passionate about business information, our opinions were not always popular. Today, meaningful, accurate information is the lifeblood of most organizations. In fact, in many cases, information is not just critical to the business-it is the business. Therefore, the need to plan how data is collected, flows through the organization, and is transformed into information the business can access, is vital. That need is increasingly recognized, not only by CIOs, but also by CEOs and even by the non-IT world at large. I was pleasantly surprised to read the following in an unlikely source:

Halfway through the last century, information became a thing. It became a commodity, a force-a quantity to be measured and analyzed. It's what our world runs on. Information is the gold and the fuel. (James Glieck, "Bit Player," The New York Times Magazine, December 30, 2001)

The second factor that motivated me to write this book was that, just as a converted smoker becomes overly eager about the smoking habits of those around him, I have had my own religious experience. Having been honed (some would say charred) on the altar of architecture, I am eager to share both my suffering and my successes. Having learned many lessons the hard way, I am anxious to help you benefit from those lessons.

This book, therefore, is a very practical guide to enterprise architecture. Many fine minds have addressed architecture theory from the podium and the bookshelf. The purpose of this book is to help architects, IT planners, and analysts find ways to implement those theories, and to spare you as much pain as possible in the process.

1. Q. Is this just more theory?

A. No. The Toolkit is very practical-it is based on our learnings as chief architects and consultants (and in both cases, compensation was determined by success).

2. Q. How can you ensure that business needs are addressed in the architecture?

A. Having wrestled with this problem, we developed a business framework and methods for translating business needs to architecture outputs. The Toolkit also addresses financial considerations and measurement development to tightly link architecture with the business.

3. Q. How does this approach relate to the Zachman Framework for Enterprise Architecture?

A. The Toolkit architecture framework produced by our company, infomajic, is consistent with, but simpler than, the Zachman Framework. It focuses on the upper left-hand rows and provides methods for filling in the cells. It also addresses strategies for implementing target architecture. The Toolkit is very practical-it's based on experience. We'll do a more complete comparison with the Zachman Framework a little later.

4. Q. How do you create architecture outputs?

A. We discuss what the critical outputs are-principles, models, inventory, and standards-and include specific methods for developing them. Examples and exercises allow you to practice using them.

A. Yes. The Toolkit includes an implementation framework, which addresses strategies and practices for successfully gaining business and IT buy-in, and includes descriptions of key architecture processes and roles.

6. Q. How can you translate conceptual architecture into reality?

A. The Toolkit includes a step-by-step approach to translating architecture into manageable projects-how to identify, select, and downsize architecture projects.

A. The Toolkit includes descriptions of key architecture roles.

8. Q. How can you measure/cost justify architecture?

A. The Toolkit addresses financial considerations and measurement development.