FEAC and Zachman Video Library

How to create a DFD -Data Flow Diagrams, Visualizing Information Flow

• A data-flow diagram (DFD) is a visual representation of the flow of data through a process or a system (usually an information system). The DFD also provides information about the outputs and inputs of each entity and the process itself. This instructional video addresses the notation and how to create a DFD and the different categories of DFDs.

Leavitt's Diamond: Understanding the factors involved in change

• Using Leavitt's Diamond to explore the impact of change in an organization.Leavitt’s Diamond or the Leavitt Business Diamond is a model that can be applied to and used for change management. It gives insight into a company’s critical success factors and was developed in the early 1970s by the American professor and organizational psychologist Harold Leavitt. According to the Leavitt Diamond Model, the success factors required to accomplish change are Structure, Tasks, People, and Technology. In the model, these four factors are placed in a square shape and interconnected, thus creating a diamond shape. This is what the model owes its name to. There are other comparable business models shaped like a diamond, the best known of which are those by Michael Porter and Edward Lawler III.

Business Transformation energy to change

• Transformation does not happen overnight. This presentation explores the idea of the Energy-to-Change concept as presented by the Roland Berger consulting firm. The Energy-to-Change is a vital part of change management and helping to build support behind transformation efforts.

What it is like to be an Enterprise Architect_Building Planes in the Air (some humor)

• Building Planes in the Air is an iconic commercial that talks about the complexity of organizational change "in-flight". Now defunct, EDS presented some very iconic commercials addressing the challenges of complexity and change management in an operational setting. This commercial and the other EDS-related commercials are still every bit as relevant today.

7 Reasons EA projects fail

• In this video, we look at seven common reasons why Enterprise Architecture projects fail. Enterprise Architecture (EA) delivers value by providing decision insight. However, architecture models that do not address specific concerns, missing or absent architecture governance, and other challenges become a source of failure within many EA programs. This video examines seven common failures and suggests one or more approaches for avoiding them.

4 Levers of organizational control

• Robert Simmons developed the 4 levers of organizational control to help balance risk with empowering employees. This approach looks at how each of the levers encourages innovation and initiative while balance risk and organizational well-being. The potential contributions of enterprise architects are identified in developing each of the four levers.

Managing Remote Teams

• Six practices to consider when managing remote teams and team members. Factors such as time zones, cultural diversity must all be a part of the lead architects planning and management considerations..

Eliciting Stakeholder feedback on architecture alternatives

• A simple two-step process for helping elicit feedback from your stakeholders on architecture alternatives. This video shows and details the steps for helping to make your stakeholders feel more comfortable and provide more open and value-added feedback to your architecture alternatives or help you identify new ones.

Enterprise Architecture Services Introduction

• Enterprise Architecture Services introduction a customer-focused approach to architecture. Introduces EA service candidates and the use of plays to help ensure consistency in service delivery. Explains the difference between EA services and EA management program and where value delivery is provided.

The importance of Emotional Intelligence for Enterprise Architects

• Overview of the concept of what is emotional intelligence and why it is important. Identifies the five dimension model of emotional intelligence along with three use cases about why enterprise architects must develop their emotional intelligence dimensions.

Benefits of Enterprise Architecture by John Zachman

• A Short video by John Zachman talking about the benefits of Enterprise Architecture and the use of the Zachman Framework. John talks about the need to engineer the enterprise. John talks to the challenges of extreme complexity and extreme rates of change being faced by today's businesses.

Book Review: SysML Distilled

• Review of SysML Distilled: A brief guide to the systems modeling language. We review books on the basis of usefulness, content, and freshness. This quick review provides excerpts from the book and highlights both the high and sometimes low spots of various publications of interest to enterprise architects, system architects, business architects and more.

Data Sites of Interest to Enterprise Architects

• This video provides a short summary of five sites of interest to people wanting to learn more about data modeling. Sites include web-based data modeling tools, detailed data governance information as well as information for establishing Information Exchanges and more.

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.

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.

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.

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.

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.

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.

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."

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.

FEAC Institute Live Stream

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

John Zachman: The value of an Ontology

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

John Zachman: Professional service cycle

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

FEAC Institute Live Stream-18 July

• John Zachman talks to EA and managing complexity and change during his four day workshop.

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

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.

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.

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 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 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 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 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 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 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 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 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 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 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 06 of 22: Can BPMN Models be classified in the Zachman Framework Column 2, Row 2?

• Can BPMN Models be classified in the Zachman Framework Column 2, Row 2? In this 22 part Enterprise Architecture conversation, John Zachman and Sunil Dutt Jha discuss how current EA Tool Vendors incorrectly map their metamodels into the Zachman Framework. Multiple-variable Composite Models like, for example, BPMN Models, cannot be classified in the Zachman Framework. A tool vendor that classifies Composite Models in the Zachman Framework Ontology would never be certified by John Zachman as supporting the Zachman Framework.

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 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 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 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.

DoDAF 2.0 Benefits and Strategies 1: For Defense & Non-Defense Communities - Part 3 (of 3)

• Prakash Rao, Faculty, FEAC Institute

DoDAF 2.0 Benefits and Strategies 1: For Defense & Non-Defense Communities - Part 1 (of 3)

• Prakash Rao, Faculty, FEAC Institute

DoDAF 2.0 Benefits and Strategies 2: For Defense & Non-Defense Communities - Part 2 (of 2)

• Charles Chivis, Systems Engineer, Capabilities Assessment Engineering, SAIC

DoDAF 2.0 Benefits and Strategies 2: For Defense & Non-Defense Communities - Part 1 (of 2)

• Charles Chivis, Systems Engineer, Capabilities Assessment Engineering, SAIC

Deriving Business Value with EA: Lessons from the Public and Private Sectors

• Dr. Steve Hudock, Chief Architect, Northrop Grumman

Deriving Business Value with EA: Panel Discussion - Part 1 (of 2)

• Hudock, Greer, and Thomas discuss topics with audience

Progress Report on the Architect's Competency Framework - Part 3 (of 3)

• Walt Okon, Senior Architecture Engineer, Architecture and Interoperability, DoD

Progress Report on the Architect's Competency Framework - Part 1 (of 3)

• Walt Okon, Senior Architecture Engineer, Architecture and Interoperability, DoD

Perspectives on the Value of Planning Versus Firefighting - Audience Q&A

• Audience Q&A Session

Perspectives on the Value of Planning Versus Firefighting - Part 2 (of 2)

• Ronald Vandiver, Director, Architecture Integration and Management, Army Capabilities Integration Center, U.S. Army Training and Doctrine Command (TRADOC)

Perspectives on the Value of Planning Versus Firefighting - Part 3 (of 3)

• Bob Stauffer, CEO, Information Dynamics

Perspectives on the Value of Planning Versus Firefighting - Part 2 (of 3)

• Bob Stauffer, CEO, Information Dynamics

Perspectives on the Value of Planning Versus Firefighting - Part 1 (of 3)

• Ronald Vandiver, Director, Architecture Integration and Management, Army Capabilities Integration Center, U.S. Army Training and Doctrine Command (TRADOC)

Deriving Business Value with EA: Lessons from the Public and Private Sectors - Part 2 (of 2)

• Melvin Greer, Senior Fellow, Lockheed Martin

Deriving Business Value with EA: Lessons from the Public and Private Sectors - Part 1 (of 2)

• Melvin Greer, Senior Fellow, Lockheed Martin

Deriving Business Value with EA: Lessons from the Public and Private Sectors - Part 3 (of 3)

• Rob Thomas, Enterprise Transformation Strategy Executive, Accenture and FEAC Institute Faculty Member

Deriving Business Value with EA: Lessons from the Public and Private Sectors - Part 1 (of 3)

• Rob Thomas, Enterprise Transformation Strategy Executive, Accenture and FEAC Institute Faculty Member

FEAC Institute 2010 Practicum Awards Presentations - Part 2 (of 2)

FEAC Institute 2010 Practicum Awards Presentations - Part 1 (of 2)