Index

PF2

Head

Introduction

Introduction

Companies

Overview
Pragmatic EC
Licensing

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

Frameworks

Frameworks

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

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

Ontologies

Ontologies

Structural

MAGIC

Transformational

MAGMA

Enterprise

DOTS

POET

Methods

Methods

Phases

Overview
Architectures
Resource Utilisation
Pattern
Models

Artefacts

Artefacts

Overview

Overview
Architectures

Ontology

Detail

Structural and Transformational Zachman
Models

Meta models

Hybrid

Items

Items

The Architecture Paradigm

What is Architecture

Purpose

Its Not What You Think
Structural Complexity
Transformational Volatility
Transformational Complexity
Contextual Volatility and Complexity

Justification

Applicability
Cost and Ability
Investment
Procrastination
Abstraction and Elaboration
Relationships
The Value is in the Lines not the Boxes
Patterns
Models Meta Models and Semantics

Architecture and Engineering

Why and How
Yin and Yang
Architect Horizontally Engineer Vertically
Overlap
Inter Phase

Culture

Culture

Organisation Structure

Workers

Architects and Engineers

Fundamentals
Comparison
Architects and Engineers Who Are You

The Architect

Secrets
An Impossible Job
What Does An Architect Do
Architect or Charlatan
The Pragmatic Architect Creed

PEAF

Adoption

Adoption
Guidance

What Is EA

Bridging the Gap
You Decide
Solution Architecture

160 Char Challenge

Question
Raw Word Cloud
Analysis
Analysed Word Cloud
Description
Simplified Description

Frameworks

Why use a PM Framework
Why use an EA Framework

Where to Start

Can I start with one Department
EA Catalysts
Vision
Goals
Strategies
Tactics
Objectives

Methods

Phases

Roadmapping

Process
Intermediate Journey
Create update Intermediate Models
Create update Portfolio Model
Enterprise Transformation Strategy

Artefacts

Ontology

Structural and Transformational
Models
Meta models

Models

Relationships

Items

Tools

Coverage

Culture

Organisation Structure

Traditional vs Pragmatic

Enterprise Architect

Two Types

Type 1

Requirements
Duties

Type 2

Requirements
Duties

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

 

What is Enterprise Architecture

A Pragmatic Explanation

Buy Paperback
or Kindle















POET>Items>Architecture-and-Engineering>Architect-Horizontally-Engineer-Vertically ◄◄◄           .           ►►► POET>Items>Architecture-and-Engineering>Inter-Phase

In practice, there is of course an overlap between Architecture and Engineering. The overlap may be small or may be large depending on the problem in hand. This tends to decide whether one person is required to perform both roles or if two people who specialise in each are required.

In this day and age, thinking about things seems to be viewed as a very bad thing as no discernible progress is being made. It should be noted that all the major advancements since time began have come from people thinking about things rather than doing - at least initially. This is not to say that everyone should sit around thinking about things and not doing anything. Doing things informs thinking and thinking informs doing. This is the yin and yang where balance must be achieved for best results and progress. No one ever suggested that people should stop doing things, but it is common for people to suggest that people should stop thinking about things “Just do it!” - not explicitly because when you say it explicitly, as I have just done, it sounds ludicrous in the extreme, but in practice, in life, in the day to day run of things, thinking is routinely put on the back burner as the next urgent (but probably unimportant) thing becomes the focus.

 ...to read more, please Login or Register

POET>Items>Architecture-and-Engineering>Architect-Horizontally-Engineer-Vertically ◄◄◄         Enroll to Self Study Now!         ►►► POET>Items>Architecture-and-Engineering>Inter-Phase

Keypoint

Adopt this component by...

The line between Architecture and Engineering is a blurred one.

C-Suite: Instigate training so that people recognise that Architecture and Engineering overlap.

Questions to ponder...

Do you agree that Architecture is more about Why, while engineering is more about How?

What do other people in your Enterprise believe?

If there is not a common understanding, does this create problems?

If so, what is the impact of those problems?







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