Clash of the Illuminati! (Part 1) January 15, 2010Posted by Michael Miller in Enterprise Architecture.
add a comment
Enterprise Architecture and System Development groups act as Illuminati [Illuminati: groups claiming to have received special enlightenment] and believe that their particular approach to systems development is the only correct one. Often, these groups clash because their views toward development are polar opposites.
Enterprise Architecture takes a long-term view towards software development, concentrating on operations stability and insuring that software development adheres to enterprise architectures and standards. Software Development project groups take a short-term view with a focus on speedy software completion and implementation.
These groups clash with gates placed at the end of software development steps in order to curtail their variance from existing architectures and standards. But a better approach to software can be applied that benefits both parties.
Rather than gates at the end of each development step, perhaps a ‘accelerator’ can be placed at the beginning of each step by reviewing the system development efforts with existing enterprise architectures to accelerate development through reuse of existing architecture components, such as existing process and data models, or entity definitions and data formats. With this approach, software development avoids “reinventing the wheel” through the development process and enterprise architecture enters at the beginning of each step rather than at the end. This “enlightened approach” puts enterprise architecture in the position to act as a ‘swim coach’ providing techniques to speed development efforts, rather that acting as a ‘border guards’ that inhibit development efforts from moving to the next step. This approach provides a “win-win” for both architects and developers, and ultimately, the end-customer by reducing costs, speeding development and enhancing the quality of final deliverables that are more efficiently and effectively aligned to existing enterprise architectures.
W. Edwards Deming in his book, ‘Out of the Crisis’ states we should: “Cease dependence on inspection to achieve quality. Eliminate the need for inspection on a mass basis by building quality into the product in the first place.” We can build quality into the systems development process by introducing Enterprise Architecture to the start of each step rather than at the end.
This approach provides a
- better way to manage the relationship between enterprise architects & software developers
- pain reliever to development step walkthroughs and gates, speeding passage to the next development step
- “win-win” approach to accelerate deliverables through each software development life cycle step and enhance overall system quality.
Say tuned for my next post with further details on this subject.
Hello world! January 15, 2010Posted by Michael Miller in Enterprise Architecture.
Tags: John A. Zachman, Zachman Framework for Enterprise Architecture
add a comment
Day1 – A Brave New World
Welcome to 1EnterpriseArchitect!
Enterprise Architecture essentially began in 1987 with the publication of John Zachman’s seminal work “A Framework for Information Systems Architecture,” and the subsequent article in 1992, “Extending and Formalizing the Framework for Information Systems Architecture.” This work was later officially named the Zachman Framework for Enterprise Architecture or simply the Zachman Framework. In these two articles, John presents a framework for understanding enterprise. He proposes looking at the entire enterprise as one entity or one system, a holistic look at the enterprise and all its components. This Zachman Framework answers all the questions one can ask about an enterprise – the six interrogatives’ who, what, when, where, why and how. These two articles are the cornerstone of our profession as enterprise architects.
This blog, 1EnterpriseArchitect, is dedicated to promoting the collective holistic understanding of the enterprise through Enterprise Architecture.
I have been blessed with knowing John Zachman since 1985, when he ventured into the Chicago Board Options Exchange (CBOE), where I worked, espousing the idea of IBM’s Business Systems Planning – work that pre-dates and led to enterprise architecture. I have been a disciple of John ever since. Enterprise Architecture is not just my profession, but my passion.
I hope, through this Enterprise Architecture Blog, to share what I, one enterprise architect, have learned and continue to learn, and encourage you to share with the world to promote enterprise architecture to an exact science successful by all, rather than a popular art form crafted by a few illuminati.
1. “A framework for information systems architecture” by John A. Zachman
Source: IBM Systems Journal. Volume 26, Issue 3 Pages: 276 – 292 (1987) ISSN: 0018-8670.
2. “Extending and formalizing the framework for information systems architecture” by J. F. Sowa and J. A. Zachman, Source: IBM Systems Journal. Volume 31, Issue 3 pages 590 – 616. (1992) ISSN: 0018-8670.