Index

PF2

Head

Introduction

Introduction

Companies

Overview
Pragmatic EC
Licensing

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

PEFF

Language

Language

Basics

I Didnt Mean What You Heard
What is a System
What is an Enterprise
What is Transformation
What is a Framework
Theory or Practice
Colours
What is Business Architecture Enterprise Architecture Solution Architecture

POET

Methods

Methods

Disciplines

Overview
Capability Model
Artefacts
Modelling
Decision Making

Artefacts

Artefacts

Ontology

Basics
Mapping to Phases
Volume Volatility and Focus
Impact and Costs
Population
Transitions

Detail

Structural and Transformational Zachman
Models

Meta models

Hybrid

Items

Items

The Architecture Paradigm

Abstraction and Elaboration
Relationships
The Value is in the Lines not the Boxes
Patterns
Models Meta Models and Semantics

Tools

Number and Growth
How POET Helps
Coverage
Integration

PEAF

Adoption

Adoption

Step 5

Actions

Select an EA Modelling Tool

Step 6

Actions

Rollout EA Modelling Tool
Guidance

Tools

Types

Issues

Ability to Use Information
Effort to Maintain Information
Fundamentals
Can I use my CMDB
Content
Entities
Attributes

Methods

Disciplines

Modelling
Populate The Model

Artefacts

Ontology

Structural and Transformational
Models
Meta models

Models

Relationships

Meta models

Overview
Transformational
Principles
Debt Agreement
Structural

Items

Tools

Coverage
Vendors

Evaluation

Requirements
Process
Raw Scores
Weighted Scores
X Requirements

PF2

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

 

Enterprise Architecture Tools

A Pragmatic Approach to Selection and Adoption

Buy Paperback
or Kindle









POET>Artefacts>Ontology>Basics>Transitions ◄◄◄           .           ►►► POET>Artefacts>Ontology>Detail>Models

Here we see how the three fundamental ontologies from POET are woven together.

On the right we show the Structural ontology - MAGIC. On the left the Transformational ontology - MAGMA. Down the middle the Ontology for the fundamental parts of all Enterprises - DOTS.

Looking at the centre, it is the Transformation Capability we are interested in but we set that Capability in the context of the Direction Capability above which drives it and the Operations Capability below which it “delivers” into. (It should be noted however, that the Transformation Capability could also “deliver” into the Direction, Support or Transformation Capabilities, but only the Operation Capability is shown for clarity)

 ...to read more, please Login or Register

POET>Artefacts>Ontology>Basics>Transitions ◄◄◄         Enroll to Self Study Now!         ►►► POET>Artefacts>Ontology>Detail>Models

Keypoint

Adopt this component by...

This is the complete map of information required for Transformation to be executed in an Effective, Efficient, Agile and Durable way.

Management: Map the Artefacts of Transformation to MAGIC and MAGMA over the seven layers of Transformation, to determine where the gaps and overlaps are.

Questions to ponder...

In what way does your Enterprise consider Transformational as well as Structural models at all levels?

What ontologies and meta-models are you using?

How do they map to, and fit into, the POET Ontology?

Are they any gaps or overlaps?

If there are gaps and or overlaps, is it useful to know that?

What will you do to fill the gaps and remove the overlaps?

Do you agree this ontology is like Zachman on steroids?







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