Index

PF2

Head

Introduction

Introduction

Companies

Overview
Pragmatic EC
Licensing

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

Frameworks

Frameworks

Overview

Prominent EA Frameworks Strengths and Weaknesses
Reading Approach
Connecting the DOTS
Coverage
X Frameworks
Applicability
Context
Influences
Versions

Available Now

PEFF Enterprise Fundamentals
Why Use It
POET Enterprise Transformation
Overview
Why Use It
Operating Model
PEAF Enterprise Architecture
Overview
Why Use It
Logical Model
PTMC Transformation Maturity
Overview
Why Use It
Logical Model

Coming Soon

POED Direction
Overview
POEO Operation
Overview
POES Support
Overview
PEEF Enterprise Engineering
Overview

Comparisons

TOGAF and Zachman
Misunderstanding
Criteria
Raw Scores
Overall
Example Weightings 1
Example Weightings 2

TOGAF

Now What
Content vs Benefits
Overall
ADM
Other Frameworks
Other Detail
Guidance vs Detail
Trends

Zachman

Basic Message
Missing Perspective and Model
Overall
Architect Engineer
Why How
How When What Where Who
Perspectives and Models

Adoption

Overview
Mapping

Appendix

Appendix
Background
The Author
Keypoints
Sources and Resources
Tail
       
Click a Thumbnail to read the component. Hold down Ctrl while clicking to expand the image

 

Pragmatic Frameworks

A Pragmatic Introduction to PF2

Buy Paperback
or Kindle





PF2>Frameworks>Comparisons>Zachman>Missing-Perspective-and-Model ◄◄◄           .           ►►► PF2>Frameworks>Comparisons>Zachman>Architect-Engineer

Here we see how the important seeds that John A. Zachman planted have been extended and built upon by POET and PEAF. Without Johns important work it is debatable whether POET and PEAF would even exist.

The height of each box is proportional to the quantity of material in each section.

The core of Zachman is an Enterprise Ontology which defines Artefacts hence the larger overlap with the Artefacts section of POET. However, it is only shown just over half width because Zachman is 5/6 Structural (What, How, Where, Who, When) and 1/6 Transformational (Why) which means it only covers just over half of the full Enterprise Transformation Capability.

 ...to read more, please Login or Register

PF2>Frameworks>Comparisons>Zachman>Missing-Perspective-and-Model ◄◄◄         Enroll to Self Study Now!         ►►► PF2>Frameworks>Comparisons>Zachman>Architect-Engineer

Keypoint

Adopt this component by...

POET and PEAF greatly extends what Zachman provides.

Enterprise Architect: Use POET and PEAF to greatly extend what Zachman provides.

Questions to ponder...

Do you agree that POET and PEAF greatly extends Zachman?

If not, how would you map these things?

What things do you think are in Zachman that do not exist in POET or PEAF?

What things would you add to Zachman?



© 2008-2021 Pragmatic 365 Ltd         A Non-Profit dedicated to improving Transformation, and the lives of people that work in Transformation.