Videos

FEAC and Zachman Video Library

9 things you need to know as an EA

  • The practice of enterprise architecture has become a recognized and valued practice at many private and public organizations. Effective enterprise architects need a broad range of knowledge and skills to address the scope and range of today's modern enterprise. So, if you are new to the practice or perhaps you have been in the role for a while and want to access your own knowledge base this video might be useful to you.

Book Review: Enterprise Architecture at Work

  • In this review we take a look at the book by Lankhorst et al titled Enterprise Architecture at Work. Terrific resource for any practicing enterprise architect from beginners to experienced practitioners.

Book Review: Learning BPMN 2.0

  • Book Review of the multimedia book Learning BPMN 2.0 by Dr. Joshua Fuehrer & Joseph Butchko. The review is based upon the criteria of Usefulness; Content; and Freshness. Anyone using BPMN should find this review of value. Target audiences are Enterprise Architects; Business Architectures; Business Analysis and Process Engineering professionals.

Enterprise Architecture Short Talk with Dr. Peter Aiken

  • This session we talk with Dr. Peter Aiken. Peter is an acknowledged Data Management (DM) authority, published author, researcher, and consultant. Peter shares his views on the value and importance of enterprise architecture in managing the complexity faced by organizations.

Enterprise Architecture Short Talks: John Zachman

  • Here at the FEAC Institute always value the diversity of thought. So, We are working to bring people across the spectrum with interesting insight and share their thoughts as it relates to enterprise architecture. We hope you enjoy this EA short talk.

FEAC Institute Live Stream

  • John Zachman is introducing modeling as a part of the Zachman Framework.

Five More Sites of Interest to Enterprise Architects

  • Here are five more sites of interest to enterprise architects. In this session, we look across other disciplines as well as practitioner sites that are candidates for the EA reference library.

Five Sites of interest to Enterprise Architects

  • In this video we look at five useful sites for enterprise architects looking to build out their electronic reference library.

How to complete your FEAC Institute EADU Worksheet

  • In this video we cover the basics of the capturing your EADU in the worksheet. This include setting up your information and using the built in EADU guidelines.

John Zachman on Enterprise Architecture: Profession vs. Trade

  • John Zachman talks about Enterprise Architecture and whether it is a profession or a trade. Throughout history, what determines a profession in a particular industry, is the ability to do diagnosis- otherwise that discipline is just a trade based on labor and practitioner experience. The Professional Service Cycle states that an ontology (the Zachman Framework), allows practitioners in a discipline to repeat and predict, giving them the ability to diagnose and provide solutions. This is the difference between a Doctor and an X-ray technician. The Zachman Framework - Enterprise Ontology gives EA professionals the ability to diagnose and become "Enterprise Doctors" as opposed to "Enterprise Technicians."

Modeling for Enterprise Change

  • This introductory video highlights factors that can be considered when looking at the development of AS-IS (Current State) and TO-BE (Future State) architecture models. The rationale for architecture development is discussed as well as factors around when to use AS-IS and/or TO-BE views.

Part 01 of 22: Why is the Zachman Framework so misunderstood?

  • Why is the Zachman Framework so misunderstood? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss why so many people misunderstand the Zachman Framework™. The Framework looks simple ... but it is somewhat paradoxical. It is an Ontology and as such, it is the foundation of a discipline for creating very complex objects, specifically, Enterprises. The Periodic Table is used as a metaphor. It looks simple but it requires 4 years of university study to become competent to function in the discipline of Chemical Engineering. Similarly, it takes study to become competent as an Enterprise Architect. The Framework Ontology is fundamental to this competency and simply glancing at the Framework graphic is not sufficient to become an expert.

Part 02 of 22: When did you realize the Zachman Framework was an ontology?

  • When did you realize that the Zachman Framework™ was an ontology? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss the definition of "Ontology" as foundational to a discipline, a science, that is different from a practice, or someone's experience and why this is important for differentiating the Zachman Framework from other Frameworks.

Part 03 of 22: What makes you confident that the Zachman Framework is the Enterprise Ontology?

  • What makes you confident that the Zachman Framework is the Enterprise Ontology? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss why there are two compelling reasons that the Zachman Framework is the Enterprise Ontology. First, the logic of the classification structure itself and second, inability to find implementation examples that are not accommodated by the structure.

Part 04 of 22: Are Business Strategies Primitives or Composites?

  • Are Business Strategies Primitives or Composites? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss "Composites" versus "Primitives". Any implementation, by definition, is a Composite because like chemical compounds, Composites are what exist as instantiations. John takes a strategy statement by illustration and shows how to parse out the Primitive components and makes the observation that any Composite that does not have representation of all six Primitives may be useful, but is likely incomplete and probably a source of Enterprise defects.

Part 05 of 22: Do you mean "granular" when you say "primitive?"

  • Do you mean "granular" when you say "primitive?" In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss the common misunderstanding about the word "Primitive". When John says "primitive," he does NOT mean "granular" - or make into smaller pieces. He defines Primitive in the context of his Framework as a single-variable, unique characteristic of the Enterprise. He works through the components of a computer program and shows why that is a Composite, Manufacturing concept and not an Engineering Concept.

Part 07 of 22: How does the Zachman Framework™ compare with other frameworks?

  • How does the Zachman Framework™ compare with other frameworks? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss the fact that there is no comparison because the popular frameworks are trying to help deliver some results ... and results, implementations, by definition, are composite in nature. The Zachman Framework classifies Primitives, "elements". Primitives don't do anything. The Zachman Framework doesn't do anything. However, if an Enterprise actually had Primitives defined by the Zachman Framework in a Repository, they could very quickly create a literally INFINITE number of different composites. Therefore, by definition, any Framework that creates composite representations by definition is creating a very small sub-set of the total infinite possibilities. John Zachman is quick to observe he never said to "stop the music" for 20 years and build Primitive Models. He said, someday, SOME DAY, the Enterprise is going to wish they had a critical mass of the Primitive Models.

Part 08 of 22: Can people download your Framework and call themselves Enterprise Architects?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss how John Zachman has been giving his Framework away for 40 years. The Zachman Framework IS Enterprise Architecture. Architecture is Architecture is Architecture. The Zachman Framework is the same as the Frameworks for Architecture of buildings, airplanes, computers, locomotives,etc., etc. with Enterprise names on the artifacts. You don't need Architecture to do Manufacturing, Manufacturing produces implementations. However, if you want integration, reusability, flexibility, interoperability, alignment and so on, those characteristics are derived from Engineering, not Manufacturing. If you cannot show the single-variable, Zachman Framework Primitive Models, you might be able to show an implementation but it is not going to be integrated, reusable, flexible, interoperable, aligned and so on because those characteristics are derived from Engineering and the implementation has not been engineered because there are no Zachman Framework Primitive Models.

Part 09 of 22: What is the Role of the Enterprise Architect?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discus a medical metaphor as the basis for defining the Role of the Enterprise Architect. The Doctor goes to school to learn about the Human Body (the Body Architecture), how to diagnose problems and prescribe solutions. The X-ray technician takes a picture, a snap-shot, a Model that is good at a point in time, fixed. The Doctor reads the X-Ray, diagnoses the problem, prescribes a solution. The Diagnosis and Prescription are dependent on the understanding of the Human Body, the Architecture "Primitives", the Ontology which is timeless. The X-Ray is a snap-shot, a Model, a Composite, created by a technician at a point in time. The Role of the Enterprise Architect should be one like a Doctor, understanding the Human Body, the Architecture Primitives, diagnosing problems, prescribing solutions, not simply the X-Ray Technician building Models, composites, snap-shots. The real value lies in diagnosing the Enterprise problems and prescribing solutions, not simply building Composite, implementation Models.

Part 10 of 22: What is preventing Enterprise Architects from doing Enterprise diagnosis?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha continue their discussion about helping Enterprise Architects diagnose Enterprise problems instead of spending all their time building models. It is quicker building the inventory of Primitive components than it is to build a Composite of multiple variables as required to build a system. Also, once you bind together all the variables for a system, you only have one system. You cannot prescribe other alternatives. Better spending time creating the inventory of Primitives from which you can create many Composite alternatives.

Part 11 of 22: Have some industries or regions adopted the Zachman Framework more than others?

  • Have some industries or regions adopted the Zachman Framework more than others? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha draw some conclusions, based on client environments, who have adopted the Zachman Framework as the ontology. The Framework is universal. It doesn't matter large - Enterprise or small; Private sector or Public. The world is in a major transition, the Information Revolution commensurate with the Industrial Revolution several hundred years ago. No Enterprise is exempt and it is becoming clear that the customer (Private or Public) wants a "custom" response to their demands and they want it NOW. If the Enterprise cannot provide that response, the customer will get another supplier ... it is too easy. Therefore, every Enterprise is going to have to accommodate extreme complexity (custom responses to every customer) and extreme change (zero time to market) for for every order. Complexity and change are the reasons you have to have Architecture for ANYTHING.

Part 12 of 22: Isn't writing code a better short term strategy than Architecture?

  • Part 12 of 22: Isn't writing code a better short term strategy than Architecture? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha talk about time to market for Enterprise Architecture. A common misconception is, writing code is a good short term strategy. That is incorrect. Writing code gets you to implementation quickly but it does not reduce your time to market for future implementations. You get more of what you have now. To reduce time to market you have to have something in inventory before you get the order ... but what you have in inventory has to be engineered to be reused in any implementation. Building up an inventory of Primitive, reusable, single-variable components enables you to change your implementation strategy to "Assemble-to-order" (in manufacturing, "Mass-Customization") to reduce your time to market to virtually ZERO. And, you need single-variable components (Primitive) models to solve General Management problems. So solve General Management problems one at a time building up your inventory of Architectural, Primitive Models iteratively and incrementally.

Part 13 of 22: Can a CEO expect EA to produce solutions in a 30 day cycle?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss how doing Enterprise Architecture in the context of the Zachman Framework significantly decreases the time to generate architectural, reusable assets thus offering solutions to Enterprise problems to the CEO much more quickly than the time it takes (often 12-14 months) building models by traditional methods.

Part 14 of 22: Why isn't Enterprise Architecture universal and generally accepted?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha talk about the current state of Enterprise Architecture. Until you actually believe that there is an Ontology, a natural classification of Enterprise components and exploit them in addressing Enterprise issues, you can say the words, "Enterprise Architecture" but you are going to get more of what you have ... systems. This is a paradigm shift. It is different. Engineering Enterprises is different than building systems. You can't just glance at my Framework and say, oh, I know that. You have to change what you believe ... and that changes your behavior.

Part 15 of 22: Do you see EA evolving into an actual discipline like Engineering or Mathematics?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha talk about how Enterprise Architecture must become a discipline like Aerospace Engineering, Mathematics, etc. John Quotes Jay Forrester who said "if airplanes were designed by committee and intuition like Enterprises are designed, it would result in an airplane which no pilot could fly." The way Enterprises are designed is going to have to change. It has to become a discipline, science. An airplane designer is different from an airplane pilot just like an Enterprise Designer is different from an Enterprise Manager. Jay Forrester thinks that future Universities will have courses in Enterprise Design.

Part 16 of 22: What can an Enterprise do to achieve success with Enterprise Architecture?

  • What can an Enterprise do to achieve success with Enterprise Architecture? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha continue the discussion on Enterprise Architecture - the Enterprise must create the Inventory of Primitives from which thousands of Composites can be created "on the fly", reusable assets are useful in the short term, Enterprise Architects must diagnose Enterprise problems, not simply build models - so what should the Enterprise do? Redoubling their efforts doing what they are already doing is only going to produce more of the same ... systems. They must understand that until an ontology exists, nothing is repeatable and nothing is predictable. There is no science. There are a lot of opportunities to learn about the Enterprise Ontology.

Part 17 of 22: What made you stop using the overhead projector?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha, on the lighter side, discuss John's transition from the overhead projector to the iPad several years ago. (Editorial note: The only thing I regret is that I can no longer use the pointer that made me famous!!)

Part 18 of 22: How do you split time between Zachman International and the FEAC Institute?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss Zachman International's acquisition of the FEAC Institute and what are John's plans are for the future of the two companies. John discusses the Zachman research and its integration into Enterprise Architecture training.

Part 19 of 22: How do people who take the Zachman training change their minds about EA?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha talk about how Zachman students are often surprised how Enterprise Architecture is much different from the Zachman perspective than they thought. Most download the picture of the Zachman Framework, but few understand the theoretical underpinnings of the Ontology and don't know how to apply concepts. It takes some hands-on experience to get the point. The old Chinese proverb, to hear is to know, to see is to believe and to do is to understand has some substantial validity.

Part 20 of 22: How do we convince upper management that Enterprise Architecture is not I.T.?

  •  In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha talk about how Enterprise Architecture today is often thought of as an IT issue. General Management does not connect up Enterprise Architecture with the Enterprise, let alone with the issues of General management. A CEO survey of 108 high visibility CEO's to a person said "the biggest problem facing the Enterprise is change." If that is the biggest problem, where is the Executive Vice President in charge of Change?! If you do a survey of 7,000 years of history of humanity it will quickly reveal that Architecture is the only mechanism that humanity has discovered for managing change in anything. And, the Ontological Primitive Models ARE Architecture. If we could get enough Primitive Models into inventory to solve a General Management problem, we would not have any problem getting the resources and time to do Enterprise Architecture and accommodate orders of magnitude increases in the rate of change.

Part 21 of 22: What does the Enterprise Architecture tool environment look like right now?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss a common question in the Zachman courses which is "what tools support the Zachman Framework?" John discusses his tool certification criteria that is published on his website and says that he hopes every tool in the universe embeds the metamodel of the Framework in their tool. There is ONE Ontology ... and "n" methodologies. There is a lot of room for creativity. Similarly, there are many tools that support Chemical Engineering but there is ONE Periodic Table, one Ontology. The Chemical Engineering tool vendors are not inventing their own Periodic Table. There are four tool vendors who have allocated resources to become Zachman Certified. The tool question however, is somewhat irrelevant because if the tool metamodel is extensible, anyone could embed the metamodel of my Framework in the tool and at least, begin building their inventory of Primitive Models.

Part 22 of 22: What are your thoughts for an Enterprise that wants EA?

  • In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha talk about how John's only website is http://www.zachman.com. While his company is called Zachman International®, he has nothing to do with, and does not own, zachmaninternational.com. John discusses an article he wrote, "Enterprise Architecture: The Issue of the Century" and points out that there is nothing keeping an Enterprise from doing Enterprise Architecture short of actually doing it. Like everything else, it takes practice to become skilled at Enterprise Architecture just like it takes practice to become skilled at anything and anytime this afternoon is not too soon to start practicing.

Preparing for Enterprise Architecture project review meeting

  • Meeting preparation is essential to successful meeting outcomes. This video look at several techniques that enterprise architects should consider when preparing for an Enterprise Architecture project meeting. We look at stakeholder analysis, stakeholder prewiring and meeting logistics and much more.

Professional service cycle

  • John Zachman shares his thoughts on the role of the enterprise architect and talks about the professional service cycle

Retrieving, Storing and Submitting your EADU worksheet

  • Retrieving, storing and submitting your EADU worksheet is quick and easy! This short tutorial shows you how quickly and easily.

The value of an Ontology

  • We asked John Zachman about why an ontology matters. Here are his thoughts.

Why you need architecture!

  • John Zachman talks to the rationale for EA as a means of addressing complexity and change. Enterprises are not log cabins!

Zachman Certified™ - Enterprise Architect Program Promo

  • This is John A. Zachman talking about the Zachman Certified™ - Enterprise Architect, 4-day Workshop. For more information about the program and to register, visit http://www.zachman.com

Zachman Video Series: Reification (The Rows)

  • In this video, Cort Coghill looks at the concept of reification as a part of the Zachman Framework. Viewers are provided an introductory explanation of reification and how it pertains to the concept of transformation for audience perspectives in framework V3.0. A discussion on project collaboration helps to relate practical application of the framework as a part of collaboration and coordination.

Stay Connected