Angry Architect

Typically the EA books I review are a summary of the author’s heuristic experiences; they provide viewpoints, models and tools for managing the challenges of EA. Fewer authors opt for an holistic approach; perhaps these books are best described as being about “approaches to EA” rather than methodological detail.

Zoom Effect is unique in the way it places the reader at the centre of a discussion about developing the Platonic (in the philosophical sense of ideal form) master architect. While the book could have  slipped every easily into being just another light weight methodology book the author has successfully fused perspectives, personalized the topic and sharpened our focus by engaging our self interest, a clever twist. The Zoom Effect is an EA book dedicated to developing you and accelerating your career and that’s different!

The book is divided into five sections: Set Your Foundation, The Process Driven Architect, Realize Your Soft Skills, Propel Your Perspective and Achieving Architectural Altitude. As you might gather from the titles this book’s aim is to apply an Architecture Development Methodology to your career. The five sections containing twenty one chapters with around ninety topics are covered in a little over 320 thematically organized pages supported by checklists and self assessments to keep you focused and on track.

As one might imagine with only three or so pages to each topic there’s very little actual method in this book. But that’s not the point; there is a lot of clear thinking and straight talking delivered in a very matter of fact and easy to read style. Where the book goes a little too methodological it can be disappointing; the Gap Analysis topic for example isn’t going to set the world on fire. But, it really doesn’t matter. It doesn’t detract from the book’s value, which is in its promotion of the ethos and ethics of architecture rather than the mechanics of method.

The book succinctly; and in my opinion rather refreshingly, calls out the shortcomings of TOGAF and perhaps, all formal methodologies for that matter; without disrupting the narrative that being a good architect is the sum of many tacit skills and it does this without becoming limp. The Zoom Effect is kind of Zen meets the Zachman Framework.

Anyone who spends time on architectural forums and has noticed that there’s always questions about education on them will instantly know that there’s a place for this book. This is a book that’s time has come. Even if you are a well established architect it’s well worth reading.

This is a book that you can start your library with, but it would be unfair to label it as an introduction or an architectural text book, it’s so much more than that. If you are looking specific advice on how to progress your career I don’t think that you’ll do better than this, highly recommended.

Evans, Sharon E. 2010, Zoom Factor for the Enterprise Architect, Firefli Media, Winnipeg

ISBN: 978-0-9812609-0-7

I’ve wanted to get my hands on a copy of this book for a numbers of years and it didn’t disappoint me. Written by one of the doges of EA this 500 page tomb will have no doubt attracted more than its fair share of detractors.

In this world of short attention spans almost anybody who pays more than a passing nod to Zachman seems to be immediately labeled as either too academic or simply too methodologically heavy.  If you’re of this ilk then this is not the book for you. However, if completeness and rigor are the heart of your philosophy then this is a book for you.

The book opens with the obligatory evolution of EA chapter, trotting out the usual stuff you’d expect. And then it shifts focus to Finkelstein’s real passion in a chapter entitled Using Enterprise Architecture for Enterprise Integration. It is in his treatment of data and meta data in particular that this book makes its contribution. Data as the fine grain of integration is its underlying theme. Perhaps not surprising for Finkelstein.

Part one literally covers off the business end of EA with chapters on Strategy Maps and Balanced Score Cards and business planning.

Part two discusses methodologies, SDLC, EA and Governance are all covered. It also takes a look at DoDAF, Modelling, Alignment and Business Normalization and even screen design. But its real contribution for me is the “Business Driven Data Mapping for Integrated Data” chapter.

Part three is a reasonable, but perhaps half hearted technology overview, but by now the book has made its point. But, there is an interesting after thought about the semantics of messaging that is worth your consideration.

On the casual to rigorous scale this book is definitely off towards the rigorous end and this will not make it popular with those who have yet to suffer sufficient pain to realise that there is no substitute for rigor.

A book for the technicians, highly recommended.

Finkelstein, Clive 2006, Enterprise Architecture for Integration, Artech House, Boston.

ISBN 1-58053-713-8

This book consists of a little theory which is a touch on the light weight side and a good 300 pages (out of about 420) on ten cases studies. The theory is concise and pithy asking the right sorts of questions to set the context for a transformation project. Given the nature of such projects and their often unique circumstances I don’t think it’s fair to expect much more in this department. The sheer diversity of transformation projects makes it difficult to develop any theory or even  generalize patterns.

The real strength of this work is its case studies they cover a very wide gambit. There are air traffic control systems, higher education systems, military systems and a bit of good old COBOL re engineering.  The case studies include MUMPS, COTS and a 4GL project, in all they’re a pretty eclectic collection which highlight the complexity of this problem space.

If you are involved in a transformation project I’d suggest that you read this book as part of your preparation, you are unlikely to find a perfect fit. However, the depth and variety of these case studies will undoubtedly provoke  some thoughts and prime you with some good questions.

This is a book for the architect leading the transformation. He’ll have to extract the relevant lessons for the planned transformation from the case studies; there’s no cookie cutter here and there are many things to consider.

This is a good book, whose time is now. While it perhaps has only a limited audience it is undoubtedly a useful tomb. It’s surprising how little good literature there is on transformation.

Ulrich, William M., Newcomb, Philp H. 2010, Information Systems Transformation,Morgan Kaufman, Burlington.

ISBN 978-0-12-374913-0

I’ve noticed that over time the importance that architectural methods ascribe to data seems to shift. For some authors data is  just the stuff that gets processed for others it is the center of the universe.  Needless to say both approaches have consequences.

This is a methodology book, but with a twist. What it proposes is a complete architectural methodology specifically developed with Enterprise Information Management in mind. One I think that could be adopted without compromising for example your integration architecture.

It blends elements of SDLC and architectural concepts like maturity models, frameworks, principles and road maps into a cohesive whole.  It includes sections that are typically thought of as being in the realm of the data architect like Enterprise Taxonomy and topics that one would usually consider enterprise issues like governance.

The book is little over 500 pages in 30 chapters . The first few chapters introduce the usual issues around data, is it an asset? Is it fuel? And sets some definitions. Then if moves on to explore the challenges of EIM. These chapters are effective without being too academic and would serve as a good primer for anyone trying to come to grips with the topic from a management or strategy perspective. Only chapter eight is a  bit of a disappointment at three and half pages “The Economic Conundrum of Information” does its best, but does manage one little gem “Remember there is is not a single CEO who will tell you information is NOT a critical asset …”

These chapters are followed by a ten or so chapters some 300 pages of detailed methodology with numerous examples and loads of good questions that you will have to ask your clients. It will take some time to internalize this methodology and the author acknowledges this by devoting chapters to sustaining and aligning EIM.

While this book might be criticized by the hard core data architect as not technical enough there is no escaping its usefulness as both a pragmatic methodology and a means of educating and aligning the business in particular. This is a book for Chief Architects, Data Architects, C level executives and any well read architect. Recommended!

Ladley, John  2010,  Making EIM Work for Business, Mogan Kaufmann, Burlington.

ISBN 978-0-12-375695-4