Good e-Learning Resources :: www.goodelearning.

com/downloads

TOGAF Poster Series #50

Architectural Artifacts
by Roger Evernden

Artifacts (or artefacts) are objects made by people. Architectural artifacts are the outputs created by architects
during the course of their work. Our poster explores what TOGAF has to say about architectural artifacts.

ARTIFACT OR ARTEFACT

WHY PRODUCE ARTIFACTS?

Artefact is the British spelling, and artifact the

American spelling. Both words mean the same
thing, but TOGAF uses the American spelling.

Architectural artifacts are created whenever we describe something

relevant to an enterprise architecture. An architectural artifact might
describe a system, a solution, or state of the enterprise.

BASIC CONCEPTS

TOGAF reuses the ISO 42010 metamodel for architecture description.

Mission

An architecture
description is a collection
of artifacts that document
an architecture.

Fulfils 1..*
Influences
Inhabits

Environment

Has an

System

Described
by1
Identifies
1..*

Has 1..*
Is important
to1..*

Stakeholder

Is addressed
to1..*

An architecture
description is a
collection of artifacts
that document an
architecture.

Has 1..*

Identifies
1..*

Concern

Used to
cover 1..*

View Point

Architecture

Architecture

Organized
by

Selects 1..*
Conforms
to

Library
Viewpoint

Architecture

Participates
in

View

Participates
in 1..*

Has source 0.1..*

Provides

Consists
of 1..*

Establishes
methods for 0.1..*

Aggregates 1..*

Model

TOGAF RECOMMENDED ARTIFACTS

Figure 35-3 in the TOGAF documentation shows the artifacts associated with the core content metamodel and each of its extensions
Preliminary

There are 3
Classes
of Artifact:
Catalogs are lists of
building blocks
Matrices show
relationships
between building
blocks
Diagrams present
building blocks,
relationships &
interconnections
graphically
for effective
stakeholder
communication

Architecture Vision

Preliminary
Principles Catalog

Matrices
Stakeholder Map Matrix

Business Architecture

Data Architecture

Application Architecture

Technology Architecture

Catalogs
Organization/Actor Catalog
Driver/Goal/Objective Catalogue
Role Catalogue
Business Service/Function Catalog
Location Catalog
Process/Event/Control Product Catalog
Contract/Measure Catalogue

Catalogs
Data Entity/Data Component Catalog

Catalogs
Application Portfolio Catalog
Interface Catalog

Catalogs
Technology Standards Catalog
Technology Portfolio Catalog

Matrices
Data Entity/Business Function Matrix
Application/Data Matrix

Catalogs
Application/Organization Matrix
Role/Application Matrix
Application/Function Matrix
Application/Interaction Matrix

Catalogs
Application/Technology Matrix

Catalogs

Core Diagrams
Application Communication Diagram
Application and User Location Diagram
Application Use-Case Diagram

Core Diagrams
Appliction Communication Diagram
Application and User Location Diagram
Application Use-Case Diagram

Core Diagrams
Environement and Location Diagram
Platform Decomposition Diagram

Extension Diagrams
Data Security Diagram
Data Migration Diagram
Data Lifecycle Diagram

Extension Diagrams
Enterprise Manageability Diagram
Process/Application Realization Diagram
Software Engineering Diagram
Application Migration Diagram
Software Distribution Diagram

Extension Diagrams
Processing Diagram
Networked Computing Hardware Diagram
Communication Engineering Diagram

Business Interaction Matrix

Actor/Role Matrix
Business Footprint Diagram
Business Service/Information Diagram
Functional Decomposition Diagram
Product Lifecycle Diagram

Part III, 24.

Stakeholder Management
describes major stakeholder
groups , their likely concerns,
& relevant artifacts. As with
everything in TOGAF these
are suggestions, & should be
tailored to your exact needs.

Catalogs
Goal/Objective/Service Diagram
Business Use-Case Diagram
Organization Decomposition Diagram
Process Flow Diagram
Event Diagram
Infrastructure
Consolidation
Extension

Value Chain Diagram

Catalogs
Requirements Catalog
Governance
Extension

Stakeholder

Solution Concept Diagram

Opportunities and Solutions

Requirement Management

Motivation
Extension

Core Diagrams

Core Diagrams

Project Context Diagram

Benefits Diagram

Data
Modeling
Extension

Services
Extension

Process
Modeling
Extension

Key Concerns

Class

Core
Content

Artifacts
are grouped
by the
Phases of
the ADM.

SEE: TOGAF
CHAPTERS:
35:
Architectural
Artifacts
24:
Stakeholder
Management

Catalogs, Matrices and Diagrams

CxO
(Corporate Functions);
e.g., CEO, CFO,CIO, COO

The high-level drivers, goals, and objectives of the orKEEP

ganization, and how these are translated into an effecSATISFIED
tive process and IT architecture to advance the business.

Business Footprint diagram

Goal/Objective/ Service diagram
Organization Decomposition diagram

Program
Management Office
(Corporate Functions);
e.g., Project Portfolio
Managers

Prioritizing, funding, and aligning change activity.

An understanding of project content and technical
dependencies between projects supports portfolio
management decision-making.

KEEP
SATISFIED

Requirements catalog
Project Context diagram
Benefits diagram
Business Footprint diagram
Application Communication diagram
Functional Decomposition diagram

...

...

...

...

@goodelearning

/goodelearning

/company/good-e-learning

Free Resource Library

www.goodelearning.com

Good e-Learning 2015. ArchiMate, The Open Group and TOGAF are registered trademarks of the Open Group in the United States and other countries
Source: The eight fundamental factors in EA Information First, Roger & Elaine Evernden, Butterworth Heinemann, 2003