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













PEAF>Artefacts>Ontology>Models>Relationships ◄◄◄           .           ►►► PEAF>Artefacts>Meta-models>Transformational

¨      Plate A illustrates the “normal” but flawed mental model, that many Enterprises have. It takes the view that the Business Strategy is written and then thrown over a wall to those IT bods to figure out the IT strategy, and out of that there then comes projects - Generally IT projects, because most transformation is all or mostly, about changing IT. Effectively the proper Roadmapping phase (the core of EA) is lost or, if not lost, is limited to and conflated with IT Strategy.

 ...to read more, please Login or Register

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

Keypoint

Adopt this component by...

The Business Strategy and IT Strategy are inherently linked and cannot be thought of separately.

Enterprise Architect: Develop the IT Strategy at the same time as the Business Strategy in an integrated way, not after the Business Strategy is thrown over the wall.

Questions to ponder...

Do you agree with the definition of a “Strategy” above? If not, how would you define a “Strategy”?

Does your Enterprise define an integrated Enterprise Strategy (Business and IT)?

Does your Enterprise define an integrated Transformation Strategy (Business and IT)?

If not, does this cause any issues or problems?

If so what do you need to do to alleviate them?

What Meta-models do you currently use?

Do they have limitations?

How do you integrate them?



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