How was Training?


It was an interesting course however I believe that the focus on selling 'EA' was too much. The first 2 days should be condensed and an explanation of what EA is should preceed selling EA otherwise you have no idea what you are selling!!! I found this ver - Enterprise Architect, EBRD, UK, Feb 2012

Recommend PEAF?


Yes - PEAF offers a practical and no-nonsense approach to help EA adoption - Principal Applications Designer, Dubai Municipality, UAE, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

Although Enterprise Architecture is only a part of the entire Transformation domain, we mention Zachman here because whilst the Zachman Ontology is known as an Enterprise Architecture Ontology, and whilst John A. Zachman is deemed to be "The Father of Enterprise Architecture", it does in fact cover the whole Transformation domain (from Strategy to Deployment).

It is, in fact, an Enterprise Transformation Ontology where the top half covers Enterprise Architecture and the bottom half covers Enterprise Engineering.

John A. Zachman is therefore "The Father of Enterprise Architecture" and "The Father of Enterprise Engineering"

The basic message contained in Zachman is that "You cannot change what you cannot see" and therefore is one of modelling and models - Architectural Models and Engineering Models.

POET and PEAF are built on the following conceptual ideas from the Zachman 6x6 grid:

1)    Vertically - There are phases of Transformation that we need to consider - from the highest view of Enterprise Strategy to the physical deployment of change - and these phases must cover ALL the transformations we need to do to bridge that gap.

2)    Horizontally - There are data used by each phase of transformation - that should be categorised - and these categorisations must cover ALL of the data we need for that phase.


2008-2016 Pragmatic EA Ltd