Session 3

Architecture Context:

How to setup the

business context &
architecture vision?

TOGAF Training
Session Agenda
• Applying Iteration to ADM
• Preliminary Phase
• Phase A – Architecture Vision
Applying Iteration to the ADM
The Architecture Development Method (ADM) is a
flexible process that can be used to support the
development of architecture as a stand-alone
process, or as an extension to other solution
development or project management methods.

Two process styles can be adopted within the

ADM for the definition of architectures:

❑ Baseline First

❑ Target First
Activity by Iteration for Baseline First Architecture Definition
Activity by Iteration for Target First Architecture Definition
Iteration Iteration Purpose Description
Cycle
Achitecture Initial Establish the approach, This iteration comprises a pass through the
Context Iteration principles, scope, and vision Preliminary and Architecture Vision phases of the
for the engagement. ADM.
Architecture Iteration 1 Define the Baseline This iteration comprises a pass through the Business
Definition Architecture. Architecture, Information Systems Architecture, and
(Baseline Technology Architecture phases of the ADM, focusing
First) on definition of the baseline.
Opportunities, solutions, and migration plans are also
considered to drive out the focus for change and test
feasibility.
Iteration 2 Define the Target This iteration comprises a pass through the Business
Architecture and gaps. Architecture, Information Systems Architecture, and
Technology Architecture phases of the ADM, focusing
on definition of the target and analyzing gaps against
the baseline.
Opportunities, solutions, and migration plans are also
considered to test viability.
Iteration n Refine baseline, target, and Subsequent Architecture Definitions attempt to
gaps. correct and refine the target to achieve an outcome
that is beneficial, feasible, and viable.
Iteration Iteration Purpose Description
Cycle
Architecture Iteration 1 Define the Target This iteration comprises a pass through the
Definition Architecture Business Architecture, Information Systems
(Target First) Architecture, and Technology Architecture phases
of the ADM, focusing on definition of the target.
Opportunities, solutions, and migration plans are
also considered to drive out the focus for change
and test feasibility.
Iteration 2 Define the Baseline This iteration comprises a pass through the
Architecture and gaps Business Architecture, Information Systems
Architecture, and Technology Architecture phases
of the ADM, focusing on definition of the baseline
and analyzing gaps against the target.
Opportunities, solutions, and migration plans are
also considered to test viability.
Iteration n Refine baseline, target, Subsequent Architecture Definitions attempt to
and gaps. correct and refine the target to achieve an
outcome that is beneficial, feasible, and viable.
Iteration Iteration Purpose Description
Cycle
Transition Iteration 1 Define and agree a set of The initial iteration of transition planning seeks to
Planning improvement gain buy-in to a portfolio of solution opportunities
opportunities, aligned in the Opportunities & Solutions phase of ADM.
against a provisional This iteration also delivers a provisional Migration
Transition Architecture. Plan.
Iteration n Agree the Transition Subsequent iterations of Transition Planning seek
Architecture, refining the to refine the migration plan, feeding back issues
identified improvement into the Opportunities & Solutions phase for
opportunities to fit. refinement.
Architecture Iteration 1 Mobilize architecture The initial Architecture Governance iteration
Governance governance and change establishes a process for governance of change and
management processes. also puts in place the appropriate people,
processes, and technology to support managed
access to and change of the defined architecture.
Iteration n Carry out architecture Subsequent iterations of the Architecture
governance and change Governance cycle focus on period reviews of
control. change initiatives to resolve issues and ensure
compliance.
Preliminary Phase
• This phase prepares the organization for
undertaking successful enterprise architecture
projects
• Understand business environment
• High level management
commitment
• Agreement on scope
• Establish principles
• Establish governance structure
• Agree method to be adopted
 Preliminary Phase
OBJECTIVES STEPS INPUT OUTPUT
To review the organizational context Scope the enterprise Reference Material Organizational model for
organizations impacted External: TOGAF & other Enterprise Architecture
To identify the sponsor stakeholder(s) architecture frameworks
Confirm governance and Tailored Architecture
To ensure that everyone who will be involved in, or support frameworks Non-Architectural inputs: Framework
benefit from, this approach is committed Business Strategy & Plan,
Define & establish EA Team Business Framework, Initial Architecture
To enable the architecture sponsor to create & Organization Governance & Legal Repository
requirements Framework, Budget ,
Identify and Establish Partnership Agreement, IT Architecture Principles
To identify and scope the elements of the Architecture Principles Strategy
enterprise organizations Restatement of Business
Select & Tailor Architecture Architectural Inputs: Principles, Goals & Drivers
To define the "architecture footprint" for the Frameworks Organizational model for
organization Request for Architecture
EA, Existing Architecture
Implement Architecture Work
To define the framework and detailed Framework, Existing
Tools
methodologies Architecture Principles,
Existing Architecture
To confirm a governance and support framework Repository

To select and implement supporting tools and

other infrastructure

To define the architecture principles

 Preliminary Phase: Approach
1
Defining the enterprise
scoping
7 2
Identifying key drivers
Evaluating the enterprise
and elements in the
architecture maturity
organizational context
where, what, why,
who, and how we do
6 architecture? 3
Defining the relationships Defining the
between management requirements for
frameworks architecture work

5 4
Defining the architecture
Defining the framework
principles that will inform
to be used
any architecture work
 Enterprise Scoping

the scope will determine those stakeholders who will

derive most benefit from the new or enhanced
enterprise architecture.

Which units that will be impacted?

Who are the stakeholders?

Enterprise Scoping
Architecture Principles
Define the underlying general rules and guidelines for the use and deployment of all
IT resources and assets across the enterprise.

Enterprise mission and plans Understandable

Enterprise strategic initiatives Robust

External constraints Complete

Current systems and technology Consistent

Computer industry trends Stable

Influenced By Qualities & Principles

 Architecture Principles
Business Principles Data Principles Application Principles Technology Principles

1. Primacy of 1. Data is an asset 1. Technology 1. Requirement-based

principles 2. Data is shared independence change
2. Maximize benefits 3. Data is accessible 2. Easy-of-use 2. Responsive change
to enterprise 4. Data trustee management
3. Information 5. Common 3. Control technical
management is vocabulary and data diversity
everybody’s definition 4. Interoperability
business 6. Data security
4. Business continuity
5. Common use
application Each principle is documented
6. Service orientation
in the recommended format:
7. Compliance with
law Name, Statement, Rationale,
8. IT Responsibility Implications
9. Protection of
intellectual property
 Management Frameworks to Co-ordinate with TOGAF
TOGAF has to co-exist with and
enhance the operational capabilities
of other management frameworks
that are present within any
organization either formally or
informally.

In addition to these frameworks,

most organizations have a method
for the development of solutions,
most of which have an IT
component. The significance of
systems is that it brings together the
various domains (also known as
People, Processes, and
Material/Technology) to deliver a
business capability
Interoperability and relationships
between Management Frameworks
 Planning for EA/Business Change Maturity Evaluation
As a part of Organizational Model for EA, EA maturity level provide a strategic measure of the
organization's ability to change, as well as a series of sequential steps to improve that ability

The criterias:
1. Administration
2. Planning
3. Framework
4. Blueprint
5. Communication
6. Compliance
7. Program
8. Involvement
No Program

Program
Informal

Program
Repeatable

Program
Well-Defined

Program
Managed
Program
t Vital
Improvemen
Continuous
 Planning for EA/Business Change Maturity Evaluation

The cryterias:
1. Architecture Process
2. Architecture Development
3. Business Linkage
4. Senior management involvement
5. Operating unit participation
6. Architecture communication
7. IT Security
8. Architecture Governance
9. IT Investment & Acquisition
Strategy
None

Initial

Development
Under

Defined

Managed

Measured
EA Tools
 Preliminary Phase – Deliverables

Organizational Model for EA Tailored Architecture Restatement of, or

Framework reference to,
Scope of Organizational Impacted
Tailored architecture method Business Principles,
Maturity assessment, gaps and
resolution approach Tailored architecture content
Business Goals, and
(deliverables and artifacts) Business Drivers
Roles & responsibilities f or
architecture team(s) Architecture Principles

Constraints on architecture work Configured and deployed tools, Request for

including evaluation report if
Re-use requirements conducted Architecture Work
Budget requirements

Requests for change

Initial Architecture Governance
Governance and support strategy Framework
Repository
Next week
Phase A – Architecture Vision

• Initiates one iteration of the architecture

process
• Sets scope, constraints, expectations
• Required at the start of every
architecture cycle
• Create the Architecture Vision
• Validates business context
• Creates Statement of Architecture work
 Phase A – Architecture Vision
OBJECTIVES STEPS INPUT OUTPUT
To ensure that this evolution of the Establish the architecture project Architecture reference Approved statement of
architecture development cycle has proper Identify stakeholders, concerns, and material Architecture Work
recognition and endorsement from the business requirements Non-Architectural Refined statements of
corporate management of the enterprise, and inputs: Request for Business Principles,
the support and commitment of the necessary Confirm & elaborate business goal,
Architecture Work Business Goals and
line management business drivers and constraints
Business Drivers
Architectural Inputs:
To validate the business principles, business Evaluate business capabilities
Organizational model Architecture Principles
goals, and strategic business drivers of the Assess readiness for business for EA, Tailored
organization and the enterprise KPIs Capability assessment
transformation Architecture
To define the scope of, and to identify and Define scope Framework, Populated Tailored Architecture
prioritize the components of, the Baseline Architecture Repository Framework
Architecture effort Confirm and elaborate architecture
Architecture Vision
principles, including Business
To define the relevant stakeholders, and their Principles Communication Plans
concerns and objectives
Develop architecture vision Additional content
To define the key business requirements populating the
Define the Target Architecture Value
To articulate an Architecture Vision and Architecture Repository
Propositions and KPIs
formalize the value proposition
Identify the Business Transformation
To create a comprehensive plan Risks and Mitigation Activities
To secure formal approval to proceed Develop EA Plans and Statement of
To understand the impact on, and of, other Architecture Work
enterprise architecture development cycles
ongoing in parallel
Scoping the architecture
The Reason:

▪ The organizational authority

▪ The objectives and stakeholder
concerns
▪ The availability of people, finance,
and other resources

The Approach:

▪ Enterprise Scope or Focus

▪ Architecture Domains
▪ Vertical Scope of Level of Detail
▪ Time Period
 Phase A – Architecture Vision (Deliverables)
Statement of Architecture Architecture Principles Architecture Vision
Work
Refined key high-level stakeholder
Scope and constraints Capability Assessment
requirements
Plan for the architectural
work Tailored Architecture Baseline Business Architecture, V0.1
Framework (for
Roles and responsibilities Engagement) Baseline Technology Architecture, V0.1
Risks and mitigating activity Tailored architecture Baseline Data Architecture, V0.1
Work product performance method
assessments Baseline Application Architecture, V0.1
Tailored architecture
Business case and KPI content (deliverables & Target Business Architecture, V0.1
metrics artifact)
Target Technology Architecture, V0.1
Configured and
deployed tools
Refined statements of Target Data Architecture, V0.1
Business Principles, Business Target Application Architecture, V0.1
Goals, and Business Drivers Communication Plan
Architecture Vision – Typical Content
TOGAF ADM Artifact & Deliverables : Architecture Vision
Catalogs, Matrix, Diagrams
stakeholder map matrix
 Stakeholder Management
Stakeholder Management is an important discipline that successful
architecture practitioners can use to win support from others. It helps
them ensure that their projects succeed where others fail.
The benefits of successful Stakeholder Management are that:
• The most powerful stakeholders can be identified early and their input can then be used to
shape the architecture; this ensures their support and improves the quality of the models
produced.
• Support from the more powerful stakeholders will help the engagement win more resource,
thus making the architecture engagement more likely to succeed.
• By communicating with stakeholders early and frequently, the architecture team can ensure
that they fully understand the architecture process, and the benefits of enterprise architecture;
this means they can support the architecture team more actively when necessary.
• The architecture engagement team can more effectively anticipate likely reactions to the
architecture models and reports, and can build into the plan the actions that will be needed to
capitalize on positive reaction whilst avoiding or addressing any negative reactions.
 Steps in the Stakeholder Management Process
1. Identify Stakeholders
• Identify the key stakeholders of the enterprise architecture.
• all the people who are affected by it, who have influence or power over it,
or have an interest in its successful or unsuccessful conclusion.
• It might include senior executives, project organization roles, client
organization roles, system developers, alliance partners, suppliers, IT
operations, customers, etc.
2. Classify Stakeholder Positions
• Develop a good understanding of the most important stakeholders and
record this analysis for reference and refresh during the project.
• assess the readiness of each stakeholder to behave in a supportive manner
3. Determine Stakeholder Management Approach
• Work out stakeholder power, influence, and interest, so as to focus the
enterprise architecture engagement on the key individuals.
Categories of Stakeholder
 Stakeholder Analysis
• Example

Stakeholder Power Grid

Catalogs, Matrix, Diagrams
VALUE CHAINS DIAGRAM
 Business Capabilities
A capability is defined as “an ability to do something”. A business capability
represents the ability for a business to do something.
A business capability is a particular ability or capacity that a business may possess or
exchange to achieve a specific purpose or outcome.

Approach :
- Top Down
- Bottom Up
Business Capabilities
 Business Capabilities : Heat map
Heat maps can show a range of different perspectives. These include maturity,
effectiveness, performance, and the value or cost contribution of each capability to the
business

Market Planning, Government Relations Management, and HR Management are in

need of immediate attention. Partner Management, Customer Management, and
Training Management have some issues but are of lower priority. Agent
Management is a new business capability that the business wishes to develop
Catalogs, Matrix, Diagrams
 Conclusion
• Two process styles can be adopted within the ADM
for the definition of architectures: Baseline First &
Target First
• Preliminary Phase prepares the organization for
undertaking successful enterprise architecture
projects
• The Architecture Vision provides the sponsor with a
key tool to sell the benefits of the proposed
capability to stakeholders and decision-makers
within the enterprise. Architecture Vision describes
how the new capability will meet the business goals
and strategic objectives and address the stakeholder
concerns when implemented.