Index

PF2

Head

Frameworks

Frameworks

Overview

Coverage
Applicability
Context

PEFF

Head

Ontologies

Ontologies

Structural

MAGIC
Relationships

Transformational

MAGMA
Relationships

Enterprise

DOTS
Relationships

Adoption

Adoption

Overview

Measures

PTMC

Levels

Step 0

Measures PTMC

Level 0

Step 1

Measures PTMC

Level 1

Step 2

Measures PTMC

Level 2

Step 3

Measures PTMC

Level 3

POET

Head

Methods

Methods

Phases

Overview
Architectures
Resource Utilisation
Models

Disciplines

Overview

Orchestration

Artefacts

Artefacts

Overview

Overview
Architectures

Ontology

Basics

Detail

Structural and Transformational Zachman
Models

Items

Items

The Architecture Paradigm

What is Architecture

Purpose

Transformational Complexity

Architecture and Engineering

Yin and Yang
Architect Horizontally Engineer Vertically

Culture

Organisation Structure

Management
Workers

Slaves to Psychology

Cognitive Dissonance
The Prisons of Two Ideas

PEAF

Head

Adoption

Adoption
Guidance

What Is EA

Bridging the Gap

Where to Start

Can I start with one Department
Vision

Tools

Fundamentals

Methods

Methods

Phases

Overview

Strategising

Capability Modelling

With DOTS
With MAGIC

Roadmapping

Create update Portfolio Model

Governance and Lobbying

Transformation Debt

Artefacts

Artefacts

Ontology

Structural and Transformational
Models
Relationships

Guidance

Guidance

Principles

Types
WHAT We Produce
HOW We Do Transformation

Items

Items

Tools

Coverage

Culture

Culture

Organisation Structure

Traditional vs Pragmatic
       
Click a Thumbnail to read the component. Hold down Ctrl while clicking to expand the image

 

Structures - Fundamentals and Composites


























PEAF>Artefacts>Ontology>Structural-and-Transformational ◄◄◄           .           ►►► PEAF>Artefacts>Ontology>Models>Relationships

Here we show the common names for the various domains in the EA Ontology.

Many people use these terms (and others) but what they are exactly, and more importantly how they relate to each other, tends not to be clear. This is very worrying since they are all interrelated and depend on each other in complex ways. Not knowing or realising these relationships exist, causes Enterprises to try to create one or more of them without the required input information to do so. Or, if that information exists, to not relate one to the other and hence mistakes of monumental importance can remain hidden until much later when their impact is great, which tends to drive people to minimise or ignore them until something catastrophic happens. Not a good way to manage anything.

 ...to read more, please Login or Register

PEAF>Artefacts>Ontology>Structural-and-Transformational ◄◄◄         Enroll to Self Study Now!         ►►► PEAF>Artefacts>Ontology>Models>Relationships

Keypoint

Adopt this component by...

Enterprise Strategy is the Business Motivation and Capability models, set in the context of the Business Model.

Transformation Strategy is the Roadmap and Operating models, set in the context of the Capability and Business Motivation models.

Enterprise Architect: Support the creation of the Enterprise Strategy, by modelling the Business Model, Business Motivation Model and Enterprise Capability Mode.

Enterprise Architect: Create the Transformation Strategy, by creating the Roadmap Model and Operating Model.

Questions to ponder...

Do people in your Enterprise understand what these terms are?

Do they understand how they relate?

Do you have any of these things defined despite the input information for their creation was not available?

Do you have any of these things defined and not related to each other?

What do you need to do to improve this situation?







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