RW - Navigation

RW - Recent

Last 10 entries [comments]:


Last 10 posts [threads/views]:


Last 10 pages updated:

There are 487 wiki pages in total.

RSS logoRSS Feed

The Residual World::Tag = 'Keynote'

Entries that have been tagged with 'Keynote'.-

Integrated EA 2010 - Keynote Presentation - John Zachman

by Nic Plum on Wednesday 10 March, 2010 - 16:36 GMT

Posted in Architecture Modelling

Tags: integrated eakeynotelondonwhitehallzachman

John Zachman making the keynote presentation at Integrated EA 2010

Notes taken on the hoof from the Integrated EA 2010 conference at Whitehall in London. 

Enterprise Architecture (EA) isn’t the IT. The IT people might recognise the problem first and have the drafting skills to do EA, but ... 


  • bills of materials (why)
  • functional specs (how)
  • drawings (where)
  • operating instructions (who)
  • timing diagrams (when)
  • design objectives (why)

With primitives.You need to separate the independent variables - increases flexibility. Increased granularity doesn’t produce flexibility only smaller pieces.


  • scope boundaries (strategists)
  • requirement concepts ( owners)
  • design logic (designers)
  • plan physics (builders)
  • part configurations (implementers)
  • product instances ( operators)

Reification involves:

  • Identification
  • Definition
  • Representation
  • Specification
  • Configuration
  • Instantiation

Important to be able to see patterns. Architecture is the set of descriptive representations of a complex objects such that it can be created and forms a baseline for change. Descriptions includes all of the intersections between the abstractions. EA does the same for the enterprise.

Abstractions include

  • inventory models
  • process models
  • geographic models
  • work flow models
  • cyclical models
  • objective models

and the perspectives

  • scope boundaries
  • business models
  • system models
  • technology models
  • tooling configurations


  • Inventory models = bills of materials
  • Entity models, data models


  • Price models = functional specs
  • Transformation models


  • Network models = drawings
  • Geographic models, distribution models, geometry


  • Organisation models = operating instructions
  • Work flow models


  • Timing models = timing diagrams
  • Control structures, cyclical models, dynamics models

System models are platform independent - they are logical models and do not contain technology.  Business models are computation independent. Technology models are platform specific - they contain technologies. Tooling configurations are vendor product specific.

“The Zachman Framework is not a methodology.”

“Why would anyone think that the descriptions of an enterprise are going to be different from the descriptions of anything else that humanity has devised? Architecture is architecture. EA is not arbitrary and it is not negotiable.”

“The framework schema is technically an ontology. A framework is a structure.  A structure defines something. (The periodic table is a structure.) It is a closed set. The periodic table provides a definition. A process transforms something. A process based on a ontological structure is repeatable and predictable - a science.”

“more variables means less reuse”. i.e. use relationships to provide context not title/name etc. “architecture is the factoring out of primitive components ... we live in the composite / complex views”

Is there a technical solution to the problems? The enterprise problem is an engineering problem not a technical problem.


Comment on this article

Related Articles

      Sharing tags:

      External Links

      1.2.004 adl admin advice applescript application architecture architecture description architecture description language architecture framework artefact artisan studio award berlow blog boundary browser bug c3 capability capability configuration colaboration collaboration committee compare compliance concept concert conference configuration control conformance consistency content contrast css cv01 def stan defence definition demonstration denmark department for transport develop discovery dndaf document dod dodaf drawing enterprise enterprise architect ertms event evolve exchange exploit forum fun geneology gfdl gnu graph group handbook hazard head-model history humour ibm rhapsody iec ieee ieee1471 iet ietf implement implementation incose innovation institute integrated ea interoperability introduction ipad iso iso42010 isse keynote knowledge language linkedin lockheed martin london london underground m3 mac management mdg meaning meeting metamodel mil std modaf model modelling style naf nato natural language needline news nist no magic magicdraw noun omg omnigraffle ontology open source opensource operational organisation oxfordshire perspective plan platform playlist portability presentation procurement profile project public publication publish purpose rail relationship release repository research resource rfc4677 risk role rssb rule safety sea search security sentence service singapore site softeam modelio software solution song sos sourceforge sparx systems sparx systems enterprise architect specification spreadsheet stakeholder concern standard steering group stencil stereotype store strategy structure support sysml system system authority system of systems systems engineering team template test threat

      All articles/posts © of the respective authors

      Site design and architecture © 2010 - 2019 Eclectica Systems Ltd.