Customer Reviews

IT Architecture Toolkit

5 star:		(13)
4 star:		(0)
3 star:		(1)
2 star:		(1)
1 star:		(1)

 

 

I've used a number of approaches to architecture, including the Zachman Framework, the RUP 4+1, SEI's ATAM, and a plethora of others. I was skeptical that this book was going to add anything of value to the art and practice of architecture. I was wrong. This book gives a realistic approach to architecture. Better, with minor tailoring it can be applied to any of the more mainstream methodologies, and does so because it is a toolkit of methods more than a formal methodology. Of course, if you are not using one of the plethora of architecture methodologies, this book's approach will also serve nicely as a standalone methodology as well.

The approach is based on "Infomajic Enterprise Architecture Toolkit", which was developed by the author's company (Infomajic). In some ways the approach is a scaled down version of the Zachman Framework - indeed, there is a fairly detailed comparison between the two starting on page 11.

There are three main stages to the architecture toolkit, (1) connecting the architecture to business, (2) developing the architecture itself, and (3) implementation strategies. The latter is what sets this book apart from many which focus on 'fun' stuff and gloss over the gory details associated with implementation. Each step within these three stages are thoroughly discussed in great detail, yet the author's brisk writing style makes even the most mundane aspects highly readable.

Key aspects of this book that I particularly like include copious real world examples, width and depth of the content, and outstanding use of charts and tables to convey information. In addition to the detailed approach in the body of the book, the nine appendices are invaluable aids, ranging from interview outlines, to estimating work effort guidelines, to sample job descriptions and architecture assessment workshop outlines.

Regardless of which architecture methodology you are using (or are committed to using), you'll gain many useful ideas from this book. If you are searching for a viable methodology, this one is complete and has been proven in the real world.

This is a great book with a ton of practical advice, examples and exercises. I think the test with any IT book is can you apply the information easily to what it is you do, and the answer here is certianly "yes". Thr infomation is presented in the context of an imaginary project, and leads the reader through each step in an easy to follow format. A well done book that is well worth a sunday afternoon.

Carbone takes the role of the enterprise architect and lays out a step-by-step approach for success. She breaks down Zachman's theoretical framework into a practical how-to manual. Zachman taught you what data to collect; Carbone teaches you how to use that data. By using examples and exercises, Carbone guides you through the sometimes overwhelming process of identifying the business problems; then helps you develop key actionable items in order to solve these problems and meet business objectives. I strongly recommend this book as well as her training course that covers the same subject matter.

Jane Carbone provides a practical guide to implementing Enterprise Architecture. The book is drawn from Jane's extensive experience of developing enterprise and data architectures.

It defines a best practice Enterprise Architecture approach using the Zachman Framework. The book is organised to describe:

1. A business framework for collecting and analysing key enterprise business information. This entails defining current and target business states and, identifying gaps and opportunities.

2. An IT framework for translating business opportunities into plans. This entails defining principles, models, listing key IT resources and standards.

3. An implementation framework for delivering Enterprise Architecture projects. This entails identifying, selecting and prioritising projects.

4. Key implementation activities including defining and establishing metrics, gaining buy-in from executives and IT staff and, detailing governance processes for enabling compliance.

5. Key architecture processes, roles and human resource policies.

6. Enterprise Architecture deliverables. This includes: the IT plan (updated at least annually); an annual financial plan for IT; a project architecture assessment; a quarterly update and presentations.

This book is an asset to anyone who is grappling with the implementation of an Enterprise Architecture capability within a large organisation. It provides a holistic view of information governance centred around data. It is particularly relevant for people engaging in regulatory and compliance initiatives such as Sarbannes Oxley and Basel II.

Lastly, Jane has written a handbook for practitioners, it is written in a clear and concise manner. It exudes the experience of someone who has learnt Enterprise Architecture the hard way!

My first impression of this book was poor due to its aesthetic problems: although it's a hardcover, it appears to have been "printed" on poor quality paper by a photocopier low on toner. Certain diagrams are rendered unreadable by the lack of color, and gray backgrounds are uneven and splotchy.

Aesthetics aside, the content of this book does deliver on its promises. It presents a reasonable architecture development framework. Each aspect of the framework is explained and justified with examples from the author's personal experience. It covers the people management roles of an architect too, and includes some useful advice on how to "sell" architecture changes throughout an organization, and how and when to involve the client's IT staff.

The book details a step-by-step approach, best read start-to-finish. I imagine most architects who read this already have their own frameworks, and won't want to swallow Carbone's methodology whole. But nearly anyone will find bits and pieces useful.

What this book doesn't include is much technical detail. There is no discussion of architecture or integration design patterns, and little advice for conducting vendor evaluations for architectural components. But if the framework / methodology angle is what you're seeking, this book delivers.

This book is rather thin, but very dense. I can't remember reading a book that had so many bullet points and lists. While many books on the subject of Enterprise Architecture focus primarily on discussions, this book omits wordy definitions and usual fluff and "cuts to the chase" on how to analyze company's baseline, synthesize its target state using business drivers, and deliver a roadmap for transitioning to it.

Unlike with many books listed on Amazon.com, it's not currently possible to search inside this book or view its Table of Contents. Therefore, I have decided to list some of the chapter titles below:

Connecting Architecture to the Business
Analyzing the Business Current State
Constructing the Business target State
Analyzing the Target State--Identifying Gaps and Opportunities
Architecture Models
Standards
Establishing Metrics
Presenting the Plan for Buy-in
Compliance and Other Key Processes

The entire book is a template on how to approach an overwhelming task of restructuring a company into a better entity that will enable it to achieve its business goals. Thus I would recommend it to someone who is fairly familiar with the theoretical underpinnings of the subject and is ready to try it in practice. I am sure it will be as helpful to you as it has been helpful to me.

Jane's book is highly recommended to everyone working with enterprise architecture. Experienced architects should check the toolkit out, and will probably find at least a few good hints from a fellow practitioner, but also students and learners in the EA field should consider the book. I personally use it as the mandatory textbook at the EA course I teach at the Danish IT University, and the students love it.

Jane should write more books!

Finally - a book about Enterprise Architecture that steers clear of theoretical discourse and provides a practical, useable and clearly achievable approach! The components of the Toolkit are formidable and pragmatic - the guidelines and advice on Architecture Models (chapter 7) and Project Implementation (chapter 10) alone are worth the price of the book. And I was delighted to see data given equal time with functions and platform - this is an area that so many IT architecture plans either totally miss or grossly underestimate. But it's the lessons learned (provided throughout the book) that really drive the points home.

Ms Carbone's conversational style makes the approach seem more credible and the examples more resonant - it's the literary equivalent of standing around the water cooler and discussing the latest IT strategy, warts and all! This is ultimately a good thing, because it's presented in a constructive fashion - it makes the reader assess not only how they approach IT architecture, but also the pre-conceived notions they have about it, and provides realistic solutions to typical roadblocks. Ultimately, this book should be required reading for both IT architects and their business clients, because it provides a common understanding of IT Architecture's purpose and the important role that each group plays.

This book is the first that succinctly get to the heart of enterprise architecture, the benefits, the reason to take the time to plan. This book is perfect for both the business side of the house and the IT community to come together and realize the benefits of doing it right the first time. This book will never leave your desk and will serve as the model for everyone to use and follow.

This book had the benefit of not only being educational, but a fun read (written, I'm sure, in a style similat to that in which Ms. Carbone speaks). Taking the perspective of a self-professed "charred" Architect, Ms. Carbone carefully takes you through a description of not only what Enterprise Architecture is, but what the deliverables should look like and, most valuably, how to develop them. If you're famailar with Zachman or the Zachman Framework, Ms. Carbone clearly explains where she "overlaps" with the Framework, and where she doesn't. The value added to this book is in its almost cook-book style approach (while indicating where a thoughtful chef might "flavor to taste" - my words). My only complaint is that an Amazon search on Enterprise Architecture doesn't identify this book (I had to find it through other searches).