Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Steve Kirby
Principal Enterprise Architect
SAP UK Ltd.
Assumption
p
this audience understands the basics concerning:
g
Objectives:
Explain the major differences and similarities between SAP EAF and TOGAF 9
SAP 2008
Agenda
1.
1
2.
3
3.
4.
SAP 2008
TAFIM 3.0 ownership moved from DoD to The Open Group in 1995, renamed to TOGAF
New versions were originally developed and released approximately each year
Version 8.0 extended into Enterprise Architecture by adding Business Architecture domain
Considered
C
id d a reliable,
li bl proven method
h d ffor d
developing
l i E
Enterprise
i A
Architecture
hi
and
d considered
id d
to be the de facto market leader for Enterprise Architecture frameworks
An open
p standard but with strict license g
guidelines i.e. if yyou are developing
p g Enterprise
p
Architecture for a customer using TOGAF you must have either a commercial license or be
a member of the Open Group Architecture Forum
Vendor neutral,
neutral not industry specific
specific, applicable for enterprises of any size or location
Intended to be tailored with a focus on method (how) rather than deliverables (what)
SAP 2008
SAP Enterprise
p
Architecture team set up
p in August
g
2006
L
Launched
h d simultaneously
i lt
l att S
Sapphire
hi and
dO
Open G
Group conferences
f
A
Aprilil 2007
SAP EAF content made publicly available and released to the Open Group
Over 50 SOA200 training courses have been run globally many hundreds of
people have been trained in SAP EAF and certified as Associate SAP EAs
S
Successful
f l adoption
d ti off SAP EAF by
b major
j SAP customers
t
and
d many successes
SAP 2008
SAP EAF
SAP Specific Tools
SAP Content
Tools
(e.g. Solution Composer, Roadmap
Composer, SAP Service Workplace)
EA Modelling
Tools
(e.g. IDS Scheer)
SAP Implementation
Tools
(e.g. Solution Manager, System
Landscape Directory)
Architecture
Development Method
SAP Business
Reference Models
Content
Metamodel
Usage Guidelines
TOGAF Architecture Development Method
SAP 2008
Resource Base
SAP Technology
Reference Models
Relea
ased to the O
Open Group
Relea
ased to the O
Open Group
SAP-Specific Mappings
Agenda
1.
1
2.
3
3.
4.
SAP 2008
SAP 2008
Part I: Introduction
Core of TOGAF
TOGAF. Step by step guidelines to develop
an enterprise architecture.
Summary
SAP 2008
Parts III, IV and VII are the sections containing the most significant
f
new content
Most of the additional elements in Part II, III and IV were taken directly from SAP EAF
SAP Extensions
Standards
TOGAF 8.1
SAP 2008
2002
EAF
TOGAF 9
2007
2009
Agenda
1.
1
2.
3
3.
4.
SAP 2008
Preliminary Phase
Phase A: Architecture Vision
Phase B: Business Architecture
Phase C: Information System Architecture
Phase D: Technology Architecture
Phase E: Opportunities and Solutions
Phase F: Migration Planning
Phase G: Implementation Governance
Phase H: Architecture Change
Management
Requirements Management
Summary
SAP 2008
The essence of the TOGAF 8.1 ADM (the wheel) is retained in TOGAF 9
New SAP EAF concepts such as Iteration Cycles and Process Styles (As-Is or To-Be
First) have been carried forward directly and without change into TOGAF 9
Architecture
Deployment
Iterations
Transition
Planning
Iterations
SAP 2008
Architecture
Definition
It
Iterations
ti
Initial Iteration
Architecture Definition
Transformation Planning
Iteration 1
Iteration 2
Iteration n
Iteration 1
Iteration n
Architecture Deployment
Iteration 1
Iteration n
Prelim
Core
Informal
Informal
Informal
Vision
Core
Informal
Informal
Informal
Informal
Informal
Light
As-Is
Informal
Core
Light
Core
Informal
Informal
Light
To-Be
Informal
Informal
Core
Core
Informal
Informal
Light
A I
As-Is
I f
Informal
l
C
Core
Li ht
Light
C
Core
I f
Informal
l
I f
Informal
l
Li ht
Light
To-Be
Informal
Informal
Core
Core
Informal
Informal
Light
As-Is
Informal
Core
Light
Core
Informal
Informal
Light
To Be
To-Be
Informal
Informal
Core
Core
Informal
Informal
Light
As-Is
Informal
Core
Light
Core
Informal
Informal
Light
To-Be
Informal
Informal
Core
Core
Informal
Informal
Light
Opportunities
Oppo
tu t es a
and
d So
Solutions
ut o s
Informal
Light
g
Light
g
Light
g
Core
Core
Informal
Informal
Migration Planning
Informal
Light
Light
Light
Core
Core
Informal
Informal
Informal
Informal
Core
Core
Informal
Informal
Core
Core
Light
Business Architecture
Application Architecture
Data Architecture
Technology Architecture
Implementation Governance
Change Management
SAP 2008
Informal
Informal
Informal
Requirements Management
Similar to EAF,
EAF very light in content
SAP 2008
SAP 2008
The basic TOGAF approach to defining the overall approach, inputs, steps to be
carried out, and outputs for each phase has been followed, and more narrative
steps and practical guidance can be found in TOGAF 9 compared with TOGAF 8.1
The concept
p of Catalogs,
g , Matrices and Views ((Diagrams)
g
) introduced in SAP EAF
and their definition and production within the ADM have been carried forward
directly into TOGAF 9
The Catalogs, Matrices and Views (Diagrams) recommended for production during
Phases B, C and D in TOGAF 9 are almost identical to those defined in SAP EAF.
Many of the new concepts, accelerators and templates introduced in SAP EAF
have been carried forward directly into the TOGAF 9 narratives e
e.g.
g
Principles catalog, template and examples (Phase 0 - Preliminary)
Stakeholder map and template (Phase A Architecture Vision)
Business capability assessment (Phase A Architecture Vision)
Types of architecture engagement (Phase A Architecture Vision)
Service contracts (Phase B - Business Architecture)
Classification of changes (Phase H - Architecture Change Management)
Many of the individual narrative steps and descriptions from SAP EAF phases
have been carried forward directly into TOGAF 9 and will be recognisable to SAP
Enterprise Architects and SAP customers trained and certified in SAP EAF
SAP 2008
Consumes
Contains
Contains
Contains
Contains
Is guided
by
Orchestrates,
decomposes
SAP 2008
SAP 2008
TOGAF 9
SAP 2008
The concept of Catalogs, Matrices and Views introduced in SAP EAF has been
carried forward to TOGAF 9 but please note that Views are now called Diagrams
(definition: both are renderings of architecture content in diagrammatic format!)
TOGAF 9 defines Views as a representation
p
of a system
y
from the p
perspective
p
of a
related set of concerns while Viewpoints define the perspective from which a
View is taken. Catalogs, Matrices and Diagrams are used to provide Viewpoints.
Almost all of the set of Catalogs, Matrics and Views (Diagrams) provided with SAP
EAF have been carried forward into TOGAF 9 with some additions:
SAP EAF provides detailed descriptions of the purpose and content from a
metamodel entity perspective of the various Catalogs, Matrices and Diagrams to
be produced. These descriptions have been carried forward to the TOGAF 9
Architecture Content Framework
Framework.
SAP 2008
Metamodel Extensions from SAP EAF to TOGAF 9 one renamed and one new ((that we do not like!))
EAF
TOGAF 9
SAP 2008
Part I: Introduction
Interoperability Requirements
Architecture Partitioning
Architecture Repository
SAP 2008
Architecture Capability
Risk Management
Capability-Based Planning
Summary there are many significant and
useful discussion materials on above topics
delivered in a modular fashion
SAP Mappings
SAP Tooling
SAP Services
SAP Mappings
Mapping of EAF terminology (based on TOGAF) to the
SAP taxonomy used within SAP products and tools
Specific mappings of SAP product and tool content to the
EAF metamodel
Mappings of SAP products and tools to the TOGAF TRM
SAP 2008
SAP Term
TOGAF Term
Methodology
Business Goal
Business Objective
KPI
Driver
Goal
Objective
Value Chain
Motivation
Measure
Solution Composer
Solution Manager
Macro-Level Function
Business Scenario
Business Service
S
Scenario
i Configuration
C fi
ti Variant
V i t
S i Contract
Service
C t
t
Process
Micro-Level Function
Function
Organisation
Location
Business Participant
Actor
Role
Organization
g
/
Actor
Master Data
Process Component
p
Business Object
SDN ES Workplace
Enterprise Service Repository
L i l Information
Logical
I f
ti Component
C
t
Physical Information Component
Data Entity
Process Component
Enterprise Service
Service Marketplace
Product Availability Matrix
System Landscape Directory
Solution Composer (NetWeaver
Solution Map)
Application
pp
Product Version
Logical Technology Component
Product Instance
/ Deployment Unit
Ph i l Technology
Physical
T h l
Component
C
t
Software Component
Platform Service
IT Scenario
Service Marketplace
QuickSizer
SAP 2008
Data
Infrastructure Requirements
Technology
Requirements
Non-Functional Requirements
Agenda
1.
1
2.
3
3.
4.
SAP 2008
The Technical Reference Model is showing its age and is in urgent need of a
refresh. This could quickly be achieved through a fast-track submission, or a small
working group under the auspices of the Architecture Forum comprising the
following:
Split Phase C into two separate Application and Data Architecture phases
Consolidate Phases E and F
Consolidate Phases G and H
SAP 2008
T l (IDS S
Tools
Scheer/ARIS
h /ARIS iintegration
t
ti and
d iimplementation)
l
t ti )
SAP specific mappings (not part of TOGAF 9 but key contributors to the team effort)
SAP-specific
SAP 2008
Questions
steve.kirby@sap.com
+44 7966 975562
Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die
dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten
Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollstndigkeit der Informationen
Informationen, Texte
Texte, Grafiken
Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente
Elemente. Diese Publikation wird ohne jegliche Gewhr
Gewhr, weder
ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck
sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts.
SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit.
Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt
unberhrt. Die Informationen
Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber
Internetseiten Dritter ab.
Alle Rechte vorbehalten.
SAP 2008