Index

PF2

Head

Introduction

Introduction

Companies

Overview
Pragmatic EC
Licensing

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

Frameworks

Frameworks

Overview

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>Architect-Engineer ◄◄◄           .           ►►► PF2>Frameworks>Comparisons>Zachman>How-When-What-Where-Who

Firstly, at a general level, POET recognises that Why and How actually exist from level to level rather than just as a column. For each level, How that level is achieved is defined by the level below it and Why that level is the way it is, is defined by the level above it.

 ...to read more, please Login or Register

PF2>Frameworks>Comparisons>Zachman>Architect-Engineer ◄◄◄         Enroll to Self Study Now!         ►►► PF2>Frameworks>Comparisons>Zachman>How-When-What-Where-Who

Keypoint

Adopt this component by...

Zachman’s Why and How columns, only equate to the Motivation and Actions of MAGMA.

Why and How are also questions answered by moving up and down the rows, not columns.

Enterprise Architect: Be aware that Zachman’s Why column contains Means (How) and Ends (Why), and the How column relates to the Methods of the thing in question, not the How of Transformation.

Questions to ponder...

Do you agree that Zachman’s Why and How columns are a little strange?

If not, how would you map these things?



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