ABV - Architecture Business Value

Enterprise architects can add tremendous value to their organization's selection of a packaged application solution by analyzing each candidate's Architectural Business Value (ABV). Forrester Research's Randy Heffner explains how.
Read more here

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 - Zachman or TOGAF?

Enterprise Architecture - Which methodology do you find most effective for long term strategy, Zachman or TOGAF?



Depends upon whether the organisation is new to the concept of enterprise architecture or not. For organisations with little experience I believe TOGAF provides a more comprehensive set of guidelines which can help get things on the road. I do believe however that TOGAF lacks the level of detail to continue this within it's enterprise continuum, which is where Zachman comes into his own.

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