Fusion: Enterprise architecture has to build bridges between and integrate

Enterprise architecture (EA) has to build bridges between and integrate each of at least six architectures:
1. Value Architecture - strategies, targets, KPI-models
2. Business Architecture - governance, operational and support domains; Core value chains, business processes, workflows, business rules, products, etc.
3. Organizational Architecture - management models, organizational design, job descriptions, individual performance models
4. Information Architecture - data, information, knowledge requirements, etc.
5. Spatial Architecture - where things are located, location of assets, activities
6. Technology Architecture - enabling it all

Most EA approaches are insufficient in their integration, connectivity and fusion of these architectures to function in a seamless and optimal way.

FUSION

EA What is it?

Enterprise architecture is an integrated combination of Business Strategy + Business Architecture + Business Culture + Technology Architecture.
The “fundamental conflict among the so-called experts” is not about the contents of EA, if anything, it is about the relative significance and contribution of each aspect. Pro vs. Anti IT is about relative significance and contribution of IT (or business strategy, business architecture, etc.) at a particular point in time.

The ‘how to do it’ question is entirely different and is concerned with frameworks, methodologies, techniques, training, etc. There are “coherent, rational, theoretically and empirically sound EA methodologies”.