TOGAF 9 and Archimate 2.0 For Aligning SOA With Business Strategies and Capabilities

How to align IT/SOA on the basis of
Changing Strategies and Capabilities ?

TOGAF 9 and ArchiMate 2 on a short Case Study to drive SOA
Excerpts from the Goal-Driven and Capability-Based Development using ArchiMate 2 and )
(UML
Extended Version of the Enterprise Architect User Group Presentation Nuremberg Oct 8, 2014
Birol Berkem (Ph.D)

Open Group Certified Enterprise Architect (TOGAF 9, ArchiMate 2)
This presentation aims at showing how toGooBiz.com
use ArchiMate 2 and UML Models throughout
TOGAF 9 ADM phases in order to align IT with changing business strategies and
capabilities
It will also be presented soon as a webinar in the context of our partnership with iCMG :
http://live.icmgworld.com/
Note : TOGAF 9 )The Open Group Architecture Framework( and ArchiMate 2 are trademarks of the Open Group
This work by Birol Berkem )GooBiz.com( is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
Permissions beyond the scope of this license may be available by e-mail to info@goobiz.com
Structure of this Presentation

Business Agility Definitions
Enterprise Architecture : Goals and Roles
Balanced ScoreCards / Strategy Map techniques to
specify Governance Aspects of the EA Operating
Model
Business & IT Alignment using TOGAF 9.1 and
ArchiMate 2
Phases in TOGAFs ADM A Summary

TOGAF for SOA - Initial Content Meta-Model
TOGAFs Capability-Based Planning and ArchiMate 2 Layers
Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases
Structuring Capabilities to track risk mitigation by function, adapt
them to changing requirements and align related SOA process
components
Updating the Architecture Repository
Performing Impact Analysis of Business Capabilities upon the
Application and Technology layers
2
Modeling the Roadmap, Transition Architectures and Work Packages
Modeling Implementation Projects Planning
Business Agility : Definitions

Business agilityis the ability of a business to
adapt rapidly and cost efficiently in response to
changes in the business environment.
Business agility can be maintained by adapting
goods and services to meet customer demands,
adjusting to the changes in a business
environment and taking advantage of assets
(organization, person, process, technology).
Adapted from "On the Measurement of Enterprise Agility".Journal of Intelligent

and Robotic Systems33(3): 329342.DOI:10.1023/A:1015096909316 Nikos C.
Tsourveloudi , Kimon P. Valavanis (2002)
Business Agility : The needs !

The alignment of organizations with the changing
needs of their customers and environment requires:
Architecting business and IT resources of the
extended enterprise to ensure a value-driven
solution to these needs and capitalize on these
structures in face of changes,
Communicating key requirements, principles and
models of the future state of the enterprise (vision,
goals, strategies, ) until the IT level to ensure a
coherent evolution,
Such an alignment makes necessary building an
architecture framework that includes :
What methodologies, architectures and

specification languages to ensure a business
agility ?
What are the roles of the EA in capitalizing on the business knowledge and
aligning IT with the changing strategies ?
Enterprise Architectures : Goals and

Roles
!
Enterprise Architecture enables effective

execution of the enterprise strategy to achieve
change of an organization !
Enterprise Architecture is usualy done to identify

gaps between current and target architecture
state of an organisation.
It provides roadmap to achieve goals and deliver
objectives to guide current and future projects of
the organisation.
TOGAF 9 : An Enterprise Architecture Framework

proposed by the Open Group to align Enterprise
What are the phases of TOGAFs Architecture Development Method (ADM) to
Ressources, IT Systems and Technologies with the changing
ensure these goals and roles ?
Business Strategies and Business Capabilities.

Governance of implementation
and Architecture Change
Management
Architecture Planning :
Business Drivers and Goals
Concerns of Stakeholders,
Principles, Requirements,
Capability Assesment, Business
Transformation Readiness Factors,
Development of the
Enterprise Architecture,
Views of the Architecture
across domains,
Risk Mitigation ,
Detailed Implementation and

Migration Plan
Work Packages and Transition
Architectures
Consolidating architecture descriptions

Definition of the Roadmap
Identifying opportunities for re-use and
potential solution components
What sources to provide business inputs for the Governance Aspects of an EA ?
techniques to specify
Governance Perspectives for the EA Operating Model
What we do
have to
improve"
Shareholder
requests
Branding
displayed to
customers
Tactical and
process level
KPIs
to specify
here
What we have
to do to
enhance value
creation
How to implement such governance perspectives along the phases of TOGAF 9 ?
Birol Berkem
GooBiz 2012/2014
throughout
Business, IS and Technology Capabilities using ADM
Business agility is
the ability of a
business to adapt
rapidly and cost
efficiently in response
to changes in the
business
environment.
How to implement
actions that are part
of the BSC
Perspectives and
monitor risks ?
How to ensure
integration and
coherence of the B, C, D
phase outcomes and
find solutions during
transformation
programs ?
Drivers and
Goals to support
the BSCs
Financial &
Customer
Perspectives ?
Activities and
processes to support
the BSCs Business
Process and Resource
Perspectives ?
What systems will allow

efficient execution of these
processes in order to
support related
Perspectives ?
What technical
infrastructures will
allow availability and
security of the IT
systems ?
How to adapt business, IS and Technology Architecture Capabilities using such governance
perspectives to increase business agility ?
Use ArchiMate 2 for the Business & IT Alignment

ArchiMate is a modeling language for describing
enterprise architectures
Broader scope than UML (essentially designed for
software engineering)
Supports EA frameworks like TOGAF 9 & Zachman
ArchiMate 2 adds value to TOGAF 9.1 by bringing
consistency, traceability, completeness !
ArchiMate viewpoints are more detailed than
TOGAFs architecture artifacts TOGAF does not
provide a specification language for descriptions
10
Driving IT/SOA on the basis of Changing

Strategies and Capabilities Part I
Business Agility & Enterprise Architecture : Goals and
Roles
specify Governance Aspects of the EA Operating Model
ArchiMate 2

TOGAF for SOA - Initial Content Meta-Model &
Structuring Capabilities to track risk mitigation by function, adapt them
to changing requirements and align related SOA process components
Coordinate Implementation Projects Planning on the basis of
Architecture constraints
Structuring the Goal-Driven and Capability Based SOA Backbone at the
11
Implementation Governance Phase
Business & IT Alignment using TOGAF

9 / SOA
Capabilities are abilities of the Organization that require a
combination of Organization, People, Processes and
Technology to achieve (TOGAF 9.1 Definition)
Capabilities are delivered by

Functions that are accessed
thru governed Interfaces
provided by Business Services
Drivers and Goals

drive Capabilities
Parameters are considered to
control execution of processes that
orchestrate functions to deliver
Capabilities
Application, Data and

Technology layer components
support Business
Services that allow access to
Business functions to deliver
Capabilities
Q : So, how to link such concepts to increase business agility ?

A1 : Need a Goal driven and Capability-Based methodology to adapt SOA implementation components to changes
A2 : Need also a language to ensure coherence, completeness and traceability to support this continuous adaptation
12
The Content MetaModel from the Open Groups TOGAF 9.1
Use the TOGAFs Capability-Based Planning

with ArchiMate 2
Goals and Objectives are initially fixed in the
Preliminary and Architecture Vision Phases
Capabilities are structured to mitigate
Risks upon their internal functions,
also to make impact analysis
throughout IS and Technology layers
Incremental RoadMap to reach the Target

Architecture by reusing existing capabilities
Work Packages of Actions to implement these

Increments as well as to coordinate
Implementation Projects
Capability Based Planning from the Open Groups
TOGAF 9.1
ArchiMate 2 adds value to

TOGAF 9.1 by bringing
consistency, completeness
and traceability to support
this Goal-Driven and
Capability-Based
continuous adaptation!
Capability-Based SOA Backbone where solution components plugged

into the architecture ones are orchestrated to realize related functions
(also by guiding application

projects upon the enterprise
architecture decisions)
How can this Goal & Capability-Driven Approach be realized by the Open
Groups ArchiMate 2 Concepts
From theand
OpenRelationships
Groups ArchiMate?2 Specifications
13
Basic ArchiMate Concepts (Simplified !)
ArchiMate 2 brings
BIZ.FUNCTION
consistency
(well established
notation with
unambiguous
relationship types),
completeness
)explicit modelling of
requirements,
principles,
constraints,work
packages, transition
architectures(,
traceability
)relationships to
architecture
components using
views across multipledomains(.
14
Simplified ArchiMate Elements adapted from
EA Modeling with ArchiMate & Sparx - A.
Sikandar Cap Gemini Canada
ArchiMate 2 Some Important Viewpoints useful

for the Concern of IT / Business Alignment
Introductory Viewpoint
Application Usage Viewpoint
Organization Viewpoint
Infrastructure Viewpoint
Actor Co-Operation Viewpoint
Infrastructure Usage Viewpoint
Stakeholder Viewpoint
Implementation and
Deployment Viewpoint
Goal Realization Viewpoint
Information Structure Viewpoint
Goal-Contribution Viewpoint
Project Viewpoint
Principle Viewpoint
Service Realization
Requirement Realization
Viewpoint
Viewpoint
Layered Viewpoint
Motivation Viewpoint
Landscape Map Viewpoint
Business Function Viewpoint
Migration Viewpoint
Business Process Viewpoint
Implementation and
Business Process Co-operation
Migration Viewpoint
Viewpoint
A viewpoint in ArchiMate is a selection of a relevant
Product Viewpoint
subset of the ArchiMate concepts and the representation of that part
of an architecture
Application Behavior
Viewpoint
15
On the
basis of the previous Balanced Score Card example input data,
Application
Co-operation
let us use some of these viewpoints within EA
Viewpoint
Driving SOA on the basis of Changing

Strategies and Capabilities Part II
Business Agility & Enterprise Architecture : Goals
and Roles
Model
ArchiMate 2

components
Modeling the Roadmap, Transition Architectures and Work
Packages
16
Reminder : The Balanced ScoreCards (BSC)

Governance Perspectives for the EA Operating Model
What we do
have to
improve"
Shareholder
requests
Branding
displayed to
customers
Tactical and process level

KPIs
to specify here
(cf. the Content of the
Architecture Repository
in Part III)
What we have
to do to
enhance value
creation
Birol Berkem
GooBiz 2014
How to implement such governance perspectives along the phases of TOGAF
1
7
In the Preliminary Phase of TOGAF 9 : We start

by modeling Baseline Architecture Capabilities
of the Web Sale Company
How to adapt and structure these capabilities using a Capability-Based Planning ?
18
Reminder : TOGAFs ADM Phase Objectives and the

Capability-Based Planning to align EA with Business
Goals and Capabilities
Architecture Planning :
Governance of implementation
and Architecture Change
Management
Detailed Implementation and

Migration Plan
Work Packages and Transition
Architectures
Business Drivers and Goals

Concerns of the Stakeholders
Principles, Requirements,
Capability Assesment,
Readiness Factors,
Development of the
Enterprise Architecture,
Views of the Architecture
across domains,
Risk Mitigation ,

Lets start by considering Goals and

Objectives Initially provided as part of
the BSC Financial and Customer
perspectives within the ADM
Preliminary & the Architecture Vision
Phases
19
From the Open Groups TOGAF 9.1 Specifications
Birol Berkem
GooBiz 2014
In the Preliminary Phase : Drivers, Assessments and Initial

Goals of the EA may be modeled using the ArchiMate
Stakeholder Viewpoint
Business Drivers, Goals

Principles, initial Requirements,
How to discover Requirements on the basis of Stakeholders, Drivers and Goals ?
20
20
In Phase A : Requirements can be discovered by decomposing Goals

using the ArchiMate Goal Realization and Motivation Viewpoints
(1/2)
How to initiate Capability Assessment on the basis of Changing Strategies ?
2
1
Capability Assessment may be initiated here by

assigning appropriate responsibilities to Baseline
Capabilities on the basis of Changing Goals
Baseline State
assessment and
Future State
aspiration of the
performance level of
each capability,
as well as impacts to
the business
organization
resulting from the
successful
deployment of the
Target Architecture
may be modeled on
the basis of these
assignments
within target
capabilities
(to beViewpoints
continued)
Business functions to deliver Target Capabilities can also be discovered using ArchiMate
(cf.
next slide)
2
2
In Phase A : Business Functions can also be discovered by

applying the ArchiMate Goal Realization and Motivation
Viewpoints (2/2)
How to structure these Capabilities until the Technology Layer to mitigate risks, adapt them to changing
requirements and align related SOA process components ?

Strategies and Capabilities Part III
Roles
specify Governance Aspects of the EA Operating Model
ArchiMate 2

Structuring Capabilities to track risk mitigation by function, adapt them
to changing requirements and align related SOA process components
Structuring the Goal-Driven and Capability Based SOA Backbone at the
Implementation Governance Phase
24
Plug-in solution building-blocks (components) to achieve service
Structure capabilities until the Technology Layer

on the basis of requirements and risks & align

related SOA Processes

Balanced ScoreCards / Strategy Map techniques to specify Governance Aspects of the EA
Operating Model
Business & IT Alignment using TOGAF 9.1 and ArchiMate 2

Basic Concepts, Layers and Viewpoints in ArchiMate 2
Structuring Capabilities to mitigate risks, adapt them to changing requirements and align related
SOA components
Performing Impact Analysis of Business Capabilities upon the Application and Technology layers
Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation
Governance Phase
Plug-in solution building-blocks (components) to achieve service behaviors with expected levels
Conclusion
Lets continue by structuring Capabilities to

mitigate risks upon functions that compose
them and also to analyze impacts of their
evolution throughout Application and
Technology layers
25
In the Business Architecture Phase (Phase B) :

Capabilities are structured to mitigate risks and to be
easily adapted to changes
BUSINESS CAPABILITY
ORCHESTRATOR
How to guide corresponding functional service level expectations in order to align SOA process
26
components then describe related process orchestration ?
On the basis of the previous capability structure, assign expectations

to Service Points that are controled by the Capability Orchestrator
(Phases B and C)
Service points allow business capability components to interact with their environment
(cf. Phase G - Implementation Governance focusing on the SOA Backbone)
CAPABILITY
ORCHESTRATOR
Then to describe the orchestration of service point activities we will use a process model27
(cf. next slide)
The Orchestration of Service Points activities may be

precisely described using UML or BPMN Process
Descriptions
Changes may be expressed using
{constraints} applied to
Business Capabilities
BUSINESS CAPABILITY
ORCHESTRATOR
Process Actions are to be

reconfigured by considering
new contraints to apply
Actions of the orchestrator service makes call to its service point behaviors to realize
the Register Visitor Capability
28
The EA Repository is continously enriched since definition of the

Goals, Strategies, etc from the Business Plan and BSC Perspectives
throughout Processes
BUSINESS
GOAL
STRATEGY
Some Actions of BSC Business

Process Perspectives Identified
as Tactics
Tactic level KPIs

from
BSC Business
Process
Perspectives
BUSINESS FUNCTION
TO DELIVER THE
PORTFOLIO
MANAGEMENT
CAPABILITY
BUSINESS
FUNCTION
TO DELIVER THE
PORTFOLIO
MANAGEMENT
CAPABILITY
BUSINESS
FUNCTION
TO DELIVER THE
EXTENDED CRM
CAPABILITY SYSTEM REQUIREMENTS
(based on process level KPIs
captured on the BSC

Business Process
Perspectives)
Now, we need to perform an impact analysis for implementing each required business capability
29
until the Technology Layer using ArchiMate (cf. for Register Visitor function presented next)
Birol Berkem
GooBiz 2014
29
In Phases B and C : The Layered Viewpoint supports the Impact

Analysis for Implementing the Managing Visitor Registration
Capability
Development of the
Architecture Views across
Business and IS domains
Birol Berkem
GooBiz 2014
The impact analysis should continue to be performed until the Technical layer (cf. next
30
30
slide)
In Phases C, D : The Layered Viewpoint supports the Technical

Impact Analysis for Implementing the Managing Visitor
Registration Capability
Development of the
Architecture Views across
IS and Technical domains
How to consolidate the gap on the basis of this impact analysis and
design the roadmap (cf. Part IV)
31
Birol Berkem
GooBiz 2014
Driving SOA on the basis of Changing

Strategies and Capabilities Part IV
Business Agility & Enterprise Architecture : Goals
and Roles
Model
ArchiMate 2

components
Modeling the Roadmap, Transition Architectures and Work
Packages
32
Modeling the Roadmap, Transition Architectures

and Work Packages to coordinate
Implementation Projects

Operating Model

Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and
align related SOA process components
Coordinating Implementation Projects Planning on the basis of Architecture constraints
Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance
Phase
In this third
we consider
the building-blocks
consolidated
step,
Plug-in
solution
(components) to achieve service behaviors with expected levels
RoadMap
to reach the Target Architecture.
Conclusion
Capability Increments for Transition Architectures will

extend the existing business capabilities (initially
starting by the Baseline ones)
Work Packages of Actions to realize them as well
as the Planning of the Implementation Projects
will be coordinated on the capability basis
Lets start by drawing the Roadmap and its underlying capabilities for transition architectures
33
In Phase E : The Roadmap and underlying capabilities for

Transition and Target Architectures are consolidated from
phases B,C,D

Lets continue by determining deliverables and work package actions to deliver the
capability increments of the transition architecture
Deliverables and Work Package Actions are determined

for the Transition Architecture (1/2)

35
35
And finally determined for the target architecture (next slide)
Birol Berkem
GooBiz 2014
Deliverables and Work Package Actions are finally

determined for the Target Architecture (2/2)
Traceability links that are automatically

displayed for the selected deliverable
are useful for Consolidating architecture
descriptions
How to use these capability-driven deliverables to coordinate

Organizational and IT Projects ?
36
Birol Berkem
GooBiz 2014
Phase F : Coordinate the Implementation

Projects
B.C. MODEL FRAGMENT
BUSINESS CAPABILITY
ORCHESTRATOR
Implementation Projects will be realized in Phase G on the basis of business, IS and

technologic constraints imposed to the Architecture from phases B to E
37
Birol Berkem
GooBiz 2014

Strategies and Capabilities Part V
Roles
Model
ArchiMate 2

components
38
Structuring the Goal-Driven and Capability

Based
SOA Backbone
Operating Model

Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and
align related SOA process components
Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance
Phase
Plug-in solution building-blocks (components) to achieve service behaviors with expected levels
Conclusion
In this last step (Phase G), we focus on the

Goal-Driven and Capability-Based SOA
Backbone (of Architecture Building Blocks)
where solution components (building-blocks) are to
be plugged within Service Ports whose behaviors
are to be orchestrated by Capability Orchestrators
to realize related functions
39
In Phase G : The SOA Backbone of the system is specified being

aligned on the business functions, requirements and expected service
levels to deliver Capabilities
BUSINESS CAPABILITY
ORCHESTRATOR
USE
CASE
)UC(
Service/Request
Point )UC Comp(
Service/Request
Point )SRV Comp(
Business Capability
Component
BUSINESS CAPABILITY
ORCHESTRATOR
BUSINESS CAPABILITY
ORCHESTRATOR
B.C.O
B.C.O
40
Internal Structures of the SOA Business Capability Component are kept conform to the published Capability Model
Birol Berkem
Fragments (Phases B to F) - Thus, we just have to describe SBBs to plug-in into these ABBs (UC and servicepoints
above )
specified using
a service choreography
BUSINESS LAYER
I_Entry
<<SRV-P>> GOAL-DRIVEN
Visitor
[Entry]
<<UC-Comp>>
Visitor [Entry]
<<REALIZE>>
Visitor
<<SRV-P>>
Visitor
[Notification]
[Registration]
FUNCTIONAL LAYER
UI
B.C.O
SERVICE
VISITOR
[REGISTRATION]
BUSINESS & DATA LAYER

<<REALIZE>>
<<ENTITY>>
Visitor
<<ENTITY>>
<<ENTITY>>
Question
naire
DATA
SERVICES
Form
UNCTIONAL LAYER
UC-Comp and SRV-Comp

interactions for the User Story
Enter Visitor may be implemented
by a couple of web service port
components
To fill-in use case and service ABBs of the Architecture Backbone by the corresponding solution behaviors, we will4
transform actions of UC-Comp and SRV-Comp partitions into methods before plugging them as SBBs (cf. next)
1
In Phase G : Solution Components (SBBs) are plugged into the

Service Points (ABBs) of the Architecture backbone to implement
business functions
BUSINESS CAPABILITY
ORCHESTRATOR
Service/Request
Point )UC Comp(
Service/Request
Point )SRV Comp(
Business Capability
Component
BUSINESS CAPABILITY
ORCHESTRATOR
BUSINESS CAPABILITY
ORCHESTRATOR
<<Trace>>
<<Trace>>
SRV-Cmp
UC-Cmp
GdS_Comp
Visitor_Registration::
Visitor_Entry
UC_Comp
Visitor_Registration::
Visitor_Entry
complete_fields: boolean
form_incomplete: boolean
visitor_entered: boolean
+ enter_visitor)( : void
complete_fields)( : void
fill_form)( : void
{pre : form_found}
42
thanks_for_entry)( : void
entry_processed: boolean
entry_requested: boolean
form_registered: boolean
form_validated: boolean
+ enter_visitor)( : void
- process_entry)( : void
{pre: entry_requested}
- register_form)( : void
- validate_form)( : void
B.C.O
B.C.O
Summary - Driving SOA through TOGAFs ADM Phases using ArchiMate and UML
In Phases G & H : Capability Driven
SOA Backbone Components are
Implemented to realize expected
functions and Changes are Managed
In Phases Prelim. & A :

Capabilities are assessed
on the basis of Goals,
Principles,Requirements,
In Phase B : Capabilities are

first structured depending
on the risks
and requirement basis
In Phases E & F :
Implementation Projects are
planned to realize Capabilities
In Phases B & C : SOA

Architecture Constraints are
also considered within
Capability Structures
In Phase E : The Roadmap and

capabilities
are consolidated from phases B,C,D
In Phase B,C,D : Impact Analysis of

new Capabilities is performed across
Architecture Layers
43
Conclusion
The alignment of organizations with their changing environment requires a
Goal and Capability Driven Development that allows :
Communication of key requirements of the future state of the enterprise (strategies,
principles, vision ) on Goal and Capability basis to ensure a coherent evolution,
Propagation of the changes to ensure a coherent reactivity until the Technology layer
SOA solution building-blocks (components)
EA ensures this alignment by its support to the Business Motivation Model

(BMM), Balanced Score Cards, Strategy Map, TOGAF 9, ArchiMate 2 and
SoaML standards
It also permits organizations to capitalize on their business knowledge by
the means of Business Capabilities
Complementary information to this presentation about the Agile Enterprise Modeling, IT and System Specifications can
be found on our website : www.goobiz.com
Its complementary presentation as a webinar entitled How to increase business agility using TOGAF and ArchiMate
will be organized soon in the context of our partnership with iCMG : http://live.icmgworld.com/
44

TOGAF 9 and Archimate 2.0 For Aligning SOA With Business Strategies and Capabilities

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TOGAF 9 and Archimate 2.0 For Aligning SOA With Business Strategies and Capabilities

Uploaded by

Copyright:

Available Formats

How to align IT/SOA on the basis of

Changing Strategies and Capabilities ?

Birol Berkem (Ph.D)

Structure of this Presentation

Phases in TOGAFs ADM A Summary

Business Agility : Definitions

Adapted from "On the Measurement of Enterprise Agility".Journal of Intelligent

Tsourveloudi , Kimon P. Valavanis (2002)

Business Agility : The needs !

What methodologies, architectures and

Enterprise Architectures : Goals and

Enterprise Architecture enables effective

Enterprise Architecture is usualy done to identify

TOGAF 9 : An Enterprise Architecture Framework

Phases in TOGAFs ADM A Summary

Detailed Implementation and

Consolidating architecture descriptions

What sources to provide business inputs for the Governance Aspects of an EA ?

How to implement such governance perspectives along the phases of TOGAF 9 ?

What systems will allow

Use ArchiMate 2 for the Business & IT Alignment

Driving IT/SOA on the basis of Changing

Phases in TOGAFs ADM A Summary

Business & IT Alignment using TOGAF

Capabilities are delivered by

Drivers and Goals

Application, Data and

Q : So, how to link such concepts to increase business agility ?

The Content MetaModel from the Open Groups TOGAF 9.1

Use the TOGAFs Capability-Based Planning

Incremental RoadMap to reach the Target

Work Packages of Actions to implement these

ArchiMate 2 adds value to

Capability-Based SOA Backbone where solution components plugged

(also by guiding application

Basic ArchiMate Concepts (Simplified !)

ArchiMate 2 Some Important Viewpoints useful

Driving SOA on the basis of Changing

Phases in TOGAFs ADM A Summary

Reminder : The Balanced ScoreCards (BSC)

Tactical and process level

How to implement such governance perspectives along the phases of TOGAF

In the Preliminary Phase of TOGAF 9 : We start

How to adapt and structure these capabilities using a Capability-Based Planning ?

Reminder : TOGAFs ADM Phase Objectives and the

Detailed Implementation and

Business Drivers and Goals

Consolidating architecture descriptions

Lets start by considering Goals and

In the Preliminary Phase : Drivers, Assessments and Initial

Business Drivers, Goals

How to discover Requirements on the basis of Stakeholders, Drivers and Goals ?

In Phase A : Requirements can be discovered by decomposing Goals

How to initiate Capability Assessment on the basis of Changing Strategies ?

Capability Assessment may be initiated here by

In Phase A : Business Functions can also be discovered by

Driving IT/SOA on the basis of Changing

Phases in TOGAFs ADM A Summary

Structure capabilities until the Technology Layer

Business Agility Definitions

Enterprise Architecture : Goals and Roles

Business & IT Alignment using TOGAF 9.1 and ArchiMate 2

Phases in TOGAFs ADM A Summary