Preliminary Phase : Preparation and initiation activities
Define and Establish the "Organizational Model" for Enterprise Architecture
Objectives Input
Determine the Architecture Reference Materials External to the Enterprise
Capability desired by the - TOGAF Library
organization - Other Architecture frameworks, if any
Establish the Architecture Non-Architectural Inputs
Capability - Board strategies
- Major frameworks - e.g. Project Management
- Governance and Legal frameworks
- Partnership and Contract agreements
Architectural Inputs
"Pre-existing" models like
- Organizational Model for Enterprise Architecture
- Existing Architecture Framework
Phase A: Architecture Vision : Defining the scope, identifying the stakeholders, creating the Architecture Vision, and
Establish the scope, constraints and expectations for an Enterprise Architecture
Objectives Input
Develop a high-level aspirational Reference Materials External to the Enterprise
vision of the capabilities and
business value Non-Architectural Inputs
Request for Architecture Work
Obtain approval for a Statement Business principles, business goals, and business drivers
of Architecture Work
Architectural Inputs
Organizational Model for Enterprise Architecture
Tailored Architecture Framework
Populated Architecture Repository
Phase B: Business Architecture : Development of a Business Architecture to support an agreed Architecture Vision.
Develop the Baseline and Target business architecture
Objectives Input
Develop the Target Business Reference Materials External to the Enterprise
Architecture
Non-Architectural Inputs
Identify candidate Architecture Request for Architecture Work
Roadmap components based Business principles, business goals, and business drivers
upon gaps between the Baseline Capability Assessment
and Target Business Architectures Communications Plan
Architectural Inputs
Organizational Model for Enterprise Architecture
Tailored Architecture Framework
Architecture Principles
Enterprise Continuum
Architecture Repository
Approved Statement of Architecture Work
Architecture Vision
Draft Architecture Definition Document
Phase C: Data and Application Architecture : Information Systems Architectures for an architecture project, includin
Develop the Baseline and Target - Data and Application architecture
Objectives Input
Develop the Target Data and Reference Materials External to the Enterprise
Application Architecture
Non-Architectural Inputs
Identify candidate Architecture Request for Architecture Work
Roadmap components based Capability Assessment
upon gaps between the Baseline Communications Plan
and Target Data and Application
Architectures Architectural Inputs
<Same as Phase B, PLUS>..
Data Principles
Draft Architecture Requirements Specification
Business Architecture components of an Architecture
Roadmap
Phase D: Technology Architecture : Information Systems Architectures for an architecture project, including the dev
Develop the Baseline and Target - Technology architecture
Objectives Input
Develop the Target Technology Reference Materials External to the Enterprise
Architecture
Non-Architectural Inputs
Identify candidate Architecture Request for Architecture Work
Roadmap components based Capability Assessment
upon gaps between the Baseline Communications Plan
and Target Technology
Architectures Architectural Inputs
<Same as Phase B, PLUS>..
Technology Principles
Draft Architecture Requirements Specification
Business Architecture components of an Architecture
Roadmap
Phase E: Opportunities & Solutions : Identifying delivery vehicles (projects, programs, or portfolios) that effectively
Identify major implementation projects as work packages and group them
Objectives Input
Generate the initial complete Reference Materials External to the Enterprise
version of the Architecture Product information
Roadmap
Non-Architectural Inputs
Determine whether an Request for Architecture Work
incremental approach is required, Capability Assessment
and if so identify Transition Communications Plan
Architectures Planning methodologies
Define the overall solution Architectural Inputs
<Same as Phase D, PLUS>..
building blocks Change Requests for existing business programs and
projects
Candidate Architecture Roadmap components from
Phases B, C, and D
Phase F: Migration Planning : How to move from the Baseline to the Target Architectures by finalizing a detailed Imp
Complete the Implementation and Migration plan
Objectives Input
Finalize the Architecture Roadmap Reference Materials External to the Enterprise
and the supporting
Implementation and Migration Non-Architectural Inputs
Plan Request for Architecture Work
Capability Assessment
Ensure that the Implementation Communications Plan
and Migration Plan is co-ordinated
with the enterprise's approach to Architectural Inputs
managing and implementing <Same as Phase D, PLUS>..
change Architecture Roadmap, Version 0.1
Implementation and Migration Plan, Version 0.1
Ensure that the business value
and cost of work packages and
Transition Architectures is
understood by key stakeholders
Phase G: Implementation Governance : Architectural oversight of the implementation
Prepare and issue architecture contracts. Ensure that the implementation is as
Objectives Input
Ensure conformance with the Reference Materials External to the Enterprise
Target Architecture by
implementation projects Non-Architectural Inputs
Request for Architecture Work
Perform appropriate Architecture Capability Assessment
Governance functions
Architectural Inputs
<Same as Phase D, PLUS>..
Implementation Governance Model
Architecture Contract
Request for Architecture Work
Implementation and Migration Plan
Phase H: Architecture Change Management : Establishing procedures for managing change to the new architecture
Provide continual monitoring
Objectives Input
Ensure that the architecture Implementation Governance Model
lifecycle is maintained Architecture Contract
Implementation and Migration Plan
Ensure that the Architecture Architecture Roadmap
Governance Framework is Change Request - Technology changes
Change Request - Business changes
executed Change Request - from lessons learnt
Compliance Assessments
Ensure that the Enterprise
Architecture Capability meets
current requirements
ADM Architecture Requirements Management : Managing architecture requirements throughout the ADM
Objectives Input
Ensure that the Requirements A populated Architecture Repository
Management process is sustained Requirements Impact Assessment
and operates for all relevant ADM
phases
Manage architecture
requirements identified during
any execution of the ADM cycle or
a phase
Ensure that relevant architecture
requirements are available for use
by each phase as the phase is
executed
Requirements Management Steps
Step 1
Step 2
Step 3
Step 4
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Enterprise Architecture
Steps
1. Scope the Enterprise Organizations Impacted
2. Confirm Governance and Support Frameworks
3. Define and Establish Enterprise Architecture Team and Organization
4. Identify and Establish Architecture Principles
5. Tailor the TOGAF Framework and, if any, Other Selected Architecture
Framework(s)
6. Develop a Strategy and Implementation Plan for Tools and Techniques
holders, creating the Architecture Vision, and obtaining approvals
tations for an Enterprise Architecture
Steps
1. Establish the Architecture Project
2. Identify Stakeholders, Concerns, and Business Requirements
3. Confirm and Elaborate Business Goals, Business Drivers, and Constraints
4. Evaluate Capabilities
5. Assess Readiness for Business Transformation
6. Define Scope
7. Confirm and Elaborate Architecture Principles, including Business Principles
8. Develop Architecture Vision
9. Define the Target Architecture Value Propositions and KPIs
10. Identify the Business Transformation Risks and Mitigation Activities
11. Develop Statement of Architecture Work; Secure Approval
ure to support an agreed Architecture Vision.
ss architecture
Steps
1. Select Reference Models, Viewpoints, and Tools
2. Develop Baseline Business Architecture Description
3. Develop Target Business Architecture Description
4. Perform Gap Analysis
5. Define Candidate Roadmap Components
6. Resolve Impacts Across the Architecture Landscape
7. Conduct Formal Stakeholder Review
8. Finalize the Business Architecture
9. Create the Architecture Definition Document
hitectures for an architecture project, including the development of Data and Application Architectures.
arget - Data and Application architecture
Steps
Same as Phase B, Replacing "Business" with "Data" and "Application"..
for an architecture project, including the development of Data and Application Architectures.
chnology architecture
Steps
Same as Phase B, Replacing "Business" with "Technology"..
ects, programs, or portfolios) that effectively deliver the Target Architecture
ects as work packages and group them
Steps
1. Determine/Confirm Key Corporate Change Attributes
2. Determine Business Constraints for Implementation
3. Review and Consolidate Gap Analysis Results from Phases B to D
4. Review Consolidated Requirements Across Related Business Functions
5. Consolidate and Reconcile Interoperability Requirements
6. Refine and Validate Dependencies
7. Confirm Readiness and Risk for Business Transformation
8. Formulate Implementation and Migration Strategy
9. Identify and Group Major Work Packages
10. Identify Transition Architectures
11. Create the Architecture Roadmap & Implementation and Migration Plan
arget Architectures by finalizing a detailed Implementation and Migration Plan
on plan
Steps
1. Confirm Management Framework Interactions for the Implementation and
Migration Plan
2. Assign a Business Value to Each Work Package
3. Estimate Resource Requirements, Project Timings, and Availability/Delivery
Vehicle
4. Prioritize the Migration Projects through the Conduct of a Cost/Benefit
Assessment and Risk Validation
5. Confirm Architecture Roadmap and Update Architecture Definition
Document
6. Complete the Implementation and Migration Plan
7. Complete the Architecture Development Cycle and Document Lessons
Learned
mplementation
ntracts. Ensure that the implementation is as per plan
Steps
1. Confirm Scope and Priorities for Deployment with Development
Management
2. Identify Deployment Resources and Skills
3. Guide Development of Solutions Deployment
4. Perform Enterprise Architecture Compliance Reviews
5. Implement Business and IT Operations
6. Perform Post-Implementation Review and Close the Implementation
for managing change to the new architecture
g
Steps
1. Establish Value Realization Process
2. Deploy Monitoring Tools
3. Manage Risks
4. Provide Analysis for Architecture Change Management
5. Develop Change Requirements to Meet Performance Targets
6. Manage Governance Process
7. Activate the Process to Implement Change
e requirements throughout the ADM
Steps
<Also refer below table..>
1. Identify/document requirements - use business scenarios, or an analogous
technique
2. Baseline requirements
3. Monitor baseline requirements
4. Identify changed requirements
5. Identify changed requirements and record priorities
6. Assess Impact
7. Implement requirements arising from Phase H
8. Update the Architecture Requirements Repository
9. Implement change in the current phase
10. Assess and revise gap analysis for past phases
ADM Phase Steps
Baseline requirements:
a. Determine priorities arising from current phase of ADM
b. Confirm stakeholder buy-in to resultant priorities
c. Record requirements priorities and place in Architecture Requirements Repository
Monitor baseline requirements.
Identify changed requirements and record priorities:
a. Identify changed requirements and ensure the requirements are prioritized by the
architect(s) responsible for the current phase, and by the relevant stakeholders
b. Record new priorities
c. Ensure that any conflicts are identified and managed through the phases to a
successful conclusion and prioritization
d. Generate Requirements Impact Statement (see 32.2.18 Requirements Impact Assessment) for steering the architecture te
Notes
Changed requirements can come in through any route
To ensure that the requirements are properly assessed and prioritized, this process
needs to direct the ADM phases and record the decisions related to the requirements.
The Requirements Management phase needs to determine stakeholder satisfaction
with the decisions
Where there is dissatisfaction, the phase remains accountable to ensure the resolution
of the issues and determine next steps.
Update the Architecture Requirements Repository with information relating to the
changes requested, including stakeholder views affected.
Output
New:
• Organizational Model for Enterprise Architecture
- Scope of organizations impacted
- Maturity assessment
- R&R of architecture team
- Constrainsts on Architecture work
- Budgetory requirements
- Governance and Support strategy
• Tailored Architecture Framework
- Tailored architecture method
- Tailored architecture content
- Architecture principles
- Configured and deployed tools
• Initial Architecture Repository, populated with framework
content
• Restatement of, or reference to, business principles,
business goals, and business drivers
• Request for Architecture Work (optional)
• Architecture Governance Framework
Output
New:
• Approved Statement of Architecture Work
• Architecture Vision
• Draft Architecture Definition Document
- Baseline/Target BDAT Architectures, Version 0.1
• Communications Plan
• Capability Assessment
Updated:
• Refined statements of business principles, business goals,
and business drivers
• Architecture Principles
• Tailored Architecture Framework
• Additional content populating the Architecture Repository
Output
New:
• Draft Architecture Requirements Specification
- Gap analysis results
- Updated business requirements
• Business Architecture components of an Architecture
Roadmap
Updated:
• Refined and updated versions of the Architecture Vision
phase deliverables
• Draft Architecture Definition Document
- Baseline/Target Business Architecture V1.0
and Application Architectures.
Output
New:
• Data Architecture components of an Architecture Roadmap
• Application Architecture components of an Architecture
Roadmap
Updated:
• Refined and updated versions of the Architecture Vision
phase deliverables
• Draft Architecture Definition Document
- Baseline/Target Data and Application Architecture V1.0
• Draft Architecture Requirements Specification
- Architecture requirements, success measures, service contracts,
guidelines, specifications, standards, constraints, assumptions
(General entities in content metamodel - All these would be
updated over the period)
cation Architectures.
Output
New:
• Technology Architecture components of an Architecture
Roadmap
Updated:
• Refined and updated versions of the Architecture Vision
phase deliverables
• Draft Architecture Definition Document
- Baseline/Target Technology Architecture V1.0
• Draft Architecture Requirements Specification
ure
Output
New:
• Architecture Roadmap,
- Work package
- Transition Architectures
- Implementation recommendations
• Implementation and Migration Plan, Version 0.1
Updated:
• Refined and updated versions of the Architecture Vision
phase deliverables
• Draft Architecture Definition Document
- Baseline/Target BDAT Architectures, Version 1.0
• Draft Architecture Requirements Specification
- Consolidated Gaps, Solutions, and Dependencies Assessment
• Capability Assessments
- Business and IT capabilities assessment
Plan
Output
New:
• Re-Usable Architecture Building Blocks
• Requests for Architecture Work for a new iteration of the
ADM cycle (if any)
• Implementation Governance Model
• Change Requests for the Architecture Capability arising
from lessons learned
Updated:
• Implementation and Migration Plan, Version 1.0
• Finalized Architecture Definition Document
• Finalized Architecture Requirements Specification
• Finalized Architecture Roadmap, Version 1.0
Output
New:
• Architecture Contract (signed)
• Compliance Assessments
• Solution Building Blocks (not mentioned in 9.2)
• Change Requests
• Architecture-compliant solutions deployed
Output
Updated:
• Architecture updates (for maintenance changes)
• Changes to architecture framework and principles (for
maintenance changes)
• New Request for Architecture Work, to move to another
cycle (for major changes)
• Statement of Architecture Work, updated if necessory
• Architecture Contract, updated if necessory
• Compliance Assessments, updated if necessory
Output
New:
Requirements Impact Assessment
Updated:
Updated Architecture Requirements Specification, if
necessory
Identify/document requirements - use business scenarios, or an
analogous technique.
Identify changed requirements:
a. Remove or re-assess priorities
b. Add requirements and re-assess priorities
c. Modify existing requirements
a. Assess impact of changed requirements on current (active)
phase
b. Assess impact of changed requirements on previous phases
c. Determine whether to implement change, or defer to later ADM
cycle; if decision is to implement, assess timescale for change
management implementation
d. Issue Requirements Impact Statement, Version n+1
Implement requirements arising from Phase H.
The architecture can be changed through its lifecycle by the
Architecture Change Management phase (Phase H). The
Requirements Management process ensures that new or changing
requirements that are derived from Phase H are managed
accordingly.
Implement change in the current phase.
Assess and revise gap analysis for past phases.
The gap analysis in the ADM Phases B through D identifies the gaps
between Baseline and Target Architectures. Certain types of gap can
give rise to gap requirements.
The ADM describes two kinds of gap:
Something that is present in the baseline, but not in the target
(i.e., eliminated - by accident or design)
Something not in the baseline, but present in the target (i.e., new)
A "gap requirement" is anything that has been eliminated by accident,
and therefore requires a change to the Target Architecture.
If the gap analysis generates gap requirements, then this step will
ensure that they are addressed, documented, and recorded in the
Architecture Requirements Repository, and that the Target
Architecture is revised accordingly.
Approach
Defining the enterprise
Identifying key drivers and elements in the organizational
context
Defining the requirements for architecture work
Defining the Architecture Principles that will inform any
architecture work
Defining the framework to be used
Defining the relationships between management frameworks
Evaluating the Enterprise Architecture maturity
Techniques
Architecture Principles
Stakeholder Management
Edureka Udemy Notes
ADM Phases AN
A
B
C
D
E Y Y Pass
F Y Y Pass
G Y Y Pass
H Y Y Pass
RM Y Y Pass
