Major Content Descriptions
|The Zachman eBook|
At over 500 pages, color jpegs and 140mgs of video, this ebook defines The Zachman Framework™ for Enterprise Architecture like no other source. Authored by John A. Zachman himself, it takes the issues of Enterprise Architecture, and the industry-standard Zachman Framework™ from mystical to practical, from methodology to ontology. If you are looking to actually "do" Enterprise Architecture, then there is no other place to start than "The Zachman Framework for Enterprise Architecture™: A Primer for Enterprise Engineering and Manufacturing."
This book shows how to define the enterprise as it's exists, breaking it down into manageable components inside The Zachman Framework™. This is so that you can actually "architect" your organization rather than sit around and talk about the latest methodology masking itself as "Enterprise Architecture."
This ebook is the single most authoritative work on The Zachman Framework™ for Enterprise Architecture as it is authored by the originator of The Framework himself, John A. Zachman.
This book is being written from the perspective of someone who already understands the value of and is already committed to the concept on Enterprise Architecture. I am not trying to convince someone that they should do Enterprise Architecture. I am defining the logic of a Framework, a Framework for Enterprise Architecture, which is an analytical tool to help one think about an extremely complex object, the modern Enterprise. Enterprises are so complex and are changing so rapidly, it would be impossible to think about them holistically without a classification scheme that enabled analysis of one variable at a time without losing sense of the Enterprise as a whole.
These are some of the key points that are made in the body of the text. I put them here as an Executive Summary so no one would overlook them.
1. Seven thousand years of human history would establish that the key to complexity and change is Architecture. If it (whatever it is) gets so complex that you can't remember everything all at the same time, you have to write it down (Architecture). Then, if you want to change it (whatever it is), you start with what you wrote down (Architecture), the baseline for managing change. The reasons for doing Enterprise Architecture are, in the Information Age, it is the Enterprise that is getting complex and the Enterprise that is changing. (In the Industrial Age, it was the Product that got complex and the Product that had to change.)
2. The Framework for Enterprise Architecture (The Zachman Framework™) is a normalized schema, one (meta) fact in one place. That is what makes it a good analytical tool. Don't add or change the Rows or Columns or you will denormalize it and it will cease to be a good analytical tool. The Framework is a semantic structure. It implies nothing about implementation processes (methodologies) or tools whether they are top-down, bottom-up, left-to-right, right-to-left, or where to start.
General Managers – for understanding and devising realistic, pragmatic, strategies to address complexity and high rates of change
Enterprise Architects – for establishing authoritative logical Architectural constructs and Enterprise Engineering Design Principles and a basis for methodology and tool decisions
Technology Management – for establishing a context for making Enterprise asset/expense trade-off decisions and reducing time to market for major systems implementations
Technology Implementers – for establishing a rationale for design and implementation decisions and a basis for negotiating technical trade-offs
Although Enterprise Architecture has all kinds of technical implications, this is not a technical book. It is a book to describe the logic for building an Enterprise. Anyone who wants to understand the subject of Enterprise Architecture and the associated issues can read the book. It could be argued that within the next decade or so, everyone in the Enterprise from the General Manager to the Programmer is going to have to understand conceptually, Enterprise Architecture… the General Manager, from the perspective of managing complexity and high rates of change… Technology Management from the perspective of making the trade-off decisions and appropriate architecture investments and the Programmer, from the perspective of understanding the context and rationale for his or her work. The Information Revolution will force the issue and in a revolution, it is always best to be on the winning side! Having said all of that, initially at least, the audience will likely be those who are attempting to do actual architecture work, with those who have management responsibility for the Enterprise Technologies and their deployment a close second. Finally, the book is valuable for General Management to understand the nature of the Enterprise architectural issues and how Complexity and Change Management can be practically effected in their Enterprise.