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>Meta-models>Structural ◄◄◄           .           ►►► PEAF>Items>Tools>Vendors

To carry out the work of the EA Capability (Roadmapping) effectively and efficiency, tools are mandatory.

There are two fundamental domains (types) of information that any tool needs to be able to work with (Structural and Transformational) and this information is consumed and produced by various Disciplines.

In general (because of their history and initial focus) tools operating primarily on Structural information have tended to be called EA Modelling tools and tools operating primarily on Transformational information have tended to be called EA Planning Tools. This is not a hard and fast rule though as many tools describe themselves using various adjectives - it’s not what they call themselves, it’s what information they manipulate.

 ...to read more, please Login or Register

PEAF>Artefacts>Meta-models>Structural ◄◄◄         Enroll to Self Study Now!         ►►► PEAF>Items>Tools>Vendors

Keypoint

Adopt this component by...

Any EA Tool must integrate with other tools.

EA Project Team: Make sure your EA Tool can deal with Structural (MACE) and Transformational (MAGMA) information and that it integrates with other related tools.

Questions to ponder...

Which tools do you currently use for Enterprise Architecture?

What domains (Structural/Transformational) do they cover?

Are they adequate?

If not, does this present any issues or problems?

What will you do to alleviate or solve them?



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