Joni Turunen

TOGAF

7 Core concepts

  1. Enterprise continuum ⏲

Way to clasify items in Architectural repository

Architecture continuum

ABBs are here

Solutions continuum

SBBs are here

Types for classification

Foundation architectures (most generic)

Industry architectures (quite specific)

Common systems architectures (quite generic)

Organization-Specific architecture (most specific)

  1. Architecture repository

Some central storage for architectural outputs

Versioned filesys like Git

Knowledge management tool

Well organized file server

💾 Repository contains..

Standards Information Base (SIB)

GDPR, Healthcare, etc

Architecture Landscape

All of the deployed assets (process, systems)

Architecture Capability

All the rules around governance of the architecture

Reference Library

References just like in thesis

Architecture Requirements Repository (new in 9.2)

Approved documents

Architecture Metamodel

Tailored version for the corporate needs of TOGAF model

Solutions Landscape (new in 9.2)

SBBs taht support Architecture Landscape

Governance Log

Record of governance activity, meetings, change approved or not etc.

  1. Architecture development method, ADM 🏗

Beating ❤ of TOGAF

Tested and repeatable

Phases

Preliminary Phase

Basic principles

Architecture capability

Establish the goal of architecture capability (check 7. core concept)

ADM cycle ♻

Requirements Management ⭐

Phase A: Vision

Phase B, C, D: BDAT

Phase H: Change management

Phase E, F: Planning

..or workplan and series of transitions to where you wanna be ✏

Define process for laying out roadmap..

Phase G: Implementation

  1. Deliverables, artifacts and building blocks

Artifacts 🔹

List

Diagrams

Matrices

Work Products created in ADM phases

Deliverable

Work product -Document 📰

"contractually specified and in turn formally review, agreed, and signed off by the stakeholders"

Building Blocks ⬛

Architecture Building Blocks (ABBs) 🔲

Business process that can be reused between architecture diagrams

Named concepts that can be reused in other places

example: Need to do Customer lookups

Solution Building blocks (SBBs) 🔳

Implementations of ABBs

example: CRM search module to full fill the need ain ABB

Technical solutions reusable between architecture diagrams

  1. Defining architecture capability 🏋🏻

Evaluation of doing enterprise architecture work 0-10

Capablity Goal needs to be agreed upon and resourced for

Work, budget, timelines, milestones and status reports

Governance board

Accessible repository

Capability has a relationship to governance and repository (like in sandwhich capablity sits in between of the other two)

...that goes into the repository... 💾

...Above is the governance model that sits on top establishin that the process runs according to the way you've defined it now. ✅

People and process estabilish the architecture... 👥

What is capability?

..within organization. 🏛

Capability is within team.. 👥

...capablity in individuals.. 👤

Capability to do contract between implementation and architecture team (Phase G of ADM)

Monitor

Measure

Hold accountable

  1. Definition of Enterprise 👾

Highest level of description for an organization

Could be collection of organizations

Enterprise might be Scoped - Define what the scope is before starting..

  1. Architecture domains, BDAT

Data Domain ℹ

Data strategy (sources, types)

Physical data assets

Application Domain 📱

..deployed..

and how they relate to core business process

How applications are developed..

Business Domain 🕴

Why business exists?

What we hope to achieve?

Business strategy

Technology Domain 💻

Support system of the business

How the tech domain servers the needs of the business

Computers, middleware, 3rd party apps