You are on page 1of 12

ADM Phase Artifacts

Preliminary Principles Catalog

Architecture Vision Stakeholder Map Matrix

Value Chain Diagram

Solution Concept Diagram

Business Architecture Organization/Actor Catalog

Role Catalog

Business Service/Function Catalog

Business Interaction Matrix

Actor/Role Matrix

Business Footprint Diagram

Business Service/Information Diagram

Functional Decomposition Diagram

Product Lifecycle Diagram

Information Systems Data Entity/Data Component Catalog

(Data Architecture) Data Entity/Business Function Matrix

Application/Data Matrix

Conceptual Data Diagram

Logical Data Diagram

Data Dissemination Diagram

Information Systems Application Portfolio Catalog

(Application Architecture) Interface Catalog

Application/Organization Matrix

Role/Application Matrix

Application/Function Matrix

Application Interaction Matrix

Application Communication Diagram

Application and User Location Diagram

Deliverable Output from... Input to...
Architecture Building Blocks F, H A, B, C, D, E

(see 36.2.1 Architecture Building Blocks)

Architecture Contract - -

(see 36.2.2 Architecture Contract)

Architecture Definition Document B, C, D, E, F C, D, E, F, G, H

(see 36.2.3 Architecture Definition Document)

Architecture Principles Preliminary, Preliminary,

(see 36.2.4 Architecture Principles) A, B, C, D A, B, C, D, E, F, G, H

Architecture Repository Preliminary Preliminary,

(see 36.2.5 Architecture Repository) A, B, C, D, E, F, G, H,


Architecture Requirements B, C, D, E, F, C, D,

Specification (see 36.2.6 Architecture Requirements Requirements Requirements

Specification) Management Management

Architecture Roadmap B, C, D, E, F B, C, D, E, F

(see 36.2.7 Architecture Roadmap)

Architecture Vision A, E B, C, D, E, F, G, H,

(see 36.2.8 Architecture Vision) Requirements


Business Principles, Business Goals, and Business Preliminary, A, B A, B


(see 36.2.9 Business Principles, Business Goals,

and Business Drivers)

Capability Assessment A, E B, C, D, E, F

(see 36.2.10 Capability Assessment)

Change Request F, G, H -

(see 36.2.11 Change Request)

Communications Plan A B, C, D, E, F

(see 36.2.12 Communications Plan)

Compliance Assessment G H

(see 36.2.13 Compliance Assessment)

Implementation and Migration Plan E, F F

(see 36.2.14 Implementation and Migration Plan)

Implementation Governance Model F G, H

(see 36.2.15 Implementation Governance Model)

Organizational Model for Enterprise Preliminary Preliminary,

Architecture (see 36.2.16 Organizational Model for A, B, C, D, E, F, G, H,

Enterprise Architecture)


Request for Architecture Work Preliminary, F, H A, G

(see 36.2.17 Request for Architecture Work)

Requirements Impact Assessment Requirements Requirements

Management Management

(see 36.2.18 Requirements Impact Assessment)

Solution Building Blocks G A, B, C, D, E, F, G

(see 36.2.19 Solution Building Blocks)

Statement of Architecture Work A, B, C, D, E, F, G, H B, C, D, E, F, G, H,

(see 36.2.20 Statement of Architecture Work) Requirements


Tailored Architecture Framework Preliminary, A Preliminary,

(see 36.2.21 Tailored Architecture Framework) A, B, C, D, E, F, G, H,

Important Notes
- At present, there are no particularly useful architectural assets related to this
initiative, start with Target Architecture First
- If the question deals with needs or requirements, Business Scenario or Models
should be created first and Views the models to see that the concerns are
- If the question deals with Stakeholders, Use Stakeholder map to understand
the needs of the stakeholders.
- to identify the work packages that will be included in the Transition
o Implementation Factor and Deduction Matrix
o Consolidated Gaps
o Architecture Definition Increments Table
- When defining Architecture Principles, work with Architecture Board not with
the Sponsor, then run reviews with all the relevant stakeholders
- One of the main focus of Phase F: the migration plan should be coordinated
with the business planning, portfolio/project management and operations
management frameworks
- Adopt or Adaptation: Business Transformation Readiness Assessment
- If there is no architecture exists, start with Baseline Architecture Bottom Up
- Using the Consolidated Gaps, Solutions, and Dependencies matrix together
with the Implementation Factor Assessment and Deduction matrix, logically
group the various activities into work packages.
- Start with the Business, Data, application and Technology domains.
o Select the relevant reference models, viewpoints, and tools.
o Develop a Baseline and Target Architecture.
o Perform Gap Analysis, Assess the roadmap impacts and update ADD
- Architecture Contract with
o introduction and background,
o the nature of the agreement,
o scope of the architecture,
o architecture and strategic principles and requirements,
o conformance requirements,
o Target Architecture Measures, (Dont include Baseline Architecture)
o Define phases of deliverables,
o Prioritized joint work plan,
o Time window,
o Architecture delivery and business metrics

Preliminary Phase
- Review organization context for conducting enterprise architecture
- Identify Stakeholders, their requirements, and priorities
- Confirm the commitment of the stakeholders
- Identify and scope the elements of the enterprise organizations affected
- Define an organization's "architecture footprint". (i.e. the people responsible for
performing architecture work, their location, and responsibilities)
- Define the framework and detailed methodologies that are going to be used to
develop the enterprise architecture in the organization; this is typically an
adaptation of the ADM.
- Set up a governance and support framework to provide business process and
Architecture Governance throughout the ADM cycle.
- Select and implement supporting tools to support architecture activity
- Define constraining architecture principles
- Update Security Policy based on regulatory and security policy requirements and
communicate across the organization
- Note: Only Sponsor can Request for Architecture Work

- Other Architecture Frameworks
- Business Principles, Business Goals, and Business Drivers
- Architecture Governance Strategy
- IT Strategy
- Existing Organizational Model for Enterprise Architecture
- Existing Architecture Framework (if any)
- Existing Architecture Principles (if any)
- Existing Architecture Repository (if any)

- Scope the Enterprise Organizations Impacted
- Confirm Governance and Support Frameworks
- Define and Establish the Enterprise Architecture Team and Organization
- Identify and Establish Architecture Principles
- Select and tailor Architecture Framework(s)
- Implement Architecture tools

- TOGAF: Organizational Model for Enterprise Architecture
- Tailored Architecture Framework, including Architecture Principles
- Initial Architecture Repository
- Restatement of, or reference to, Business Principles, Business Goals, Business
- TOGAF: Request for Architecture Work
- A document from sponsors to trigger the start of an Architecture Development
- Governance Framework

Architecture Artifacts may include the following:

- TOGAF: Principles Catalog

Security Adaptations for ADM

- Define and document applicable regulatory and security policy requirements (and
communicate them regularly to employees). Identify a security architect or
security architecture team, and the role within the enterprise architecture
process. If part of larger organization, establish meetings, protocols, interfaces for
the exchange of security information.

Phase A Architecture Vision:

- Obtain management commitment for this cycle of the ADM
- Define and organize an Architecture Development Cycle
- Validate Business principles, goals, drivers and Key Performance Indicators (KPIs)
- Define, scope and prioritize architecture tasks
- Identify stakeholders, their concerns, and objectives
- Define business requirements and constraints
- Articulate an Architecture Vision and value proposition to respond to the
requirements and constraints
- Create a comprehensive plan in line with the project management frameworks
adopted by the enterprise
- Obtain formal approval to proceed
- Understand the impact on, and of, other parallel Architecture Development Cycles
- ensure that there is recognition for the architecture vision project by following any
project management and program management frameworks used within the

- TOGAF: Request for Architecture Work
- Business Principles, business goals, and business drivers
- TOGAF: Organizational Model for Enterprise Architecture
- Tailored Architecture Framework, including Architecture principles
- Populated TOGAF: Architecture Repository that is; existing architecture
documentation (framework descriptions, architecture descriptions, existing
baseline descriptions etc...)

- Establish the Architecture Project
- Identify Stakeholders, Concerns, and Business Requirements
- Confirm and Elaborate Business Goals, Business Drivers, and Constraints
- Evaluate Business Capabilities
- Assess Readiness for Business Transformation
- Define Scope
- Confirm and Elaborate Architecture Principles, including Business Principles
- Develop Architecture Vision
- Define the Target Architecture Value Propositions and KPIs
- Identify the Business Transformation Risks and Mitigation Activities
- Develop Enterprise Architecture Plans and Statement of Architecture Work.
Secure Approval

- Architecture Deliverable outputs of Architecture Vision are:
- TOGAF: Statement of Architecture Work
- Refined statement of business principles, business goals, and business drivers
- TOGAF: Architecture Principles
- TOGAF: Capability Assessment
o TOGAF: Business Transformation Readiness Assessment
- Tailored Architecture Framework
- TOGAF: Architecture Vision
o Refined key high-level stakeholder requirements
o Baseline Business Architecture (Vision)
- TOGAF: Architecture Definition Document
o TOGAF: Baseline Data Architecture (Vision)
o TOGAF: Baseline Application Architecture (Vision)
o TOGAF: Baseline Technology Architecture (Vision)
o TOGAF: Target Business Architecture (Vision)
o TOGAF: Target Data Architecture (Vision)
o TOGAF: Target Application Architecture (Vision)
o TOGAF: Target Technology Architecture (Vision)
- TOGAF: Communications Plan
- Population of TOGAF: Architecture Repository

Architecture Artifacts may include the following:

- Stakeholder Map matrix
- Value Chain diagram
- Solution Concept diagram

Security Adaptations for ADM

- Define the security-related management sign-off milestones
- Determine the applicable disaster recovery or business continuity requirements
- Identify the anticipated physical/business and regulatory environments in which
the systems will be deployed.
- Determine the criticality of the system: safety-critical, mission-critical, and non-

Phase E: Opportunities and Solutions

- Review target business objectives and capabilities, consolidate the gaps from
Phases B to D, and organize groups of building blocks to address these
- To confirm the enterprise capability for undergoing change
- To derive a series of Transition Architectures that deliver continuous business
value (e.g. capability increments) through the exploitation of opportunities to
realize the building blocks.
- To generate and gain consensus on an outline Implementation and Migration
- In other words,
o look at the corporate culture and attitude to change,
o Understand the constraints such as cost and the required time horizons.
o Look at the architecture work to ensure it is complete and seek to address
any gaps and review the functional requirements and
o Ensure there are complete interoperability requirements.
o Validate any dependencies and risks
o formulate an implementation and migration strategy
o Identifies major work packages and the transition architecture required.

- Determine/confirm key corporate change attributes
- Determine business constraints for implementation (Enterprise Arch Maturity
- Review and consolidate Gap Analysis results from Phases B to D
- Review IT requirements from a functional perspective
- Consolidate and reconcile interoperability requirements
- Refine and validate dependencies
- Confirm readiness and risk for business transformation
o Identify, Classify and Mitigate Risks and document risks in Consolidated
- Formulate high-level Implementation and Migration strategy
- Identify and group major work packages
- Identify Transition Architectures
- Create portfolio and project charters and update the architectures

- TOGAF: Statement of Architecture Work
- TOGAF: Architecture Vision (updated as needed)
- Draft TOGAF: Architecture Definition Document (updates)
o Identification of increments (Architecture Definition Increments Table)
o Interoperability and co-existence requirements
o Implementation and Migration Strategy
o Inclusion of project list and project charters
- Draft TOGAF: Architecture Requirements Specification (updated as needed)
- TOGAF: Capability Assessment
o Enterprise Architecture Maturity Profile
o Transformation Readiness Report
- Transition Architectures
o Consolidated Gaps, Solutions, and Dependencies assessments
o Risk Register
o Implementation Factor Assessment & Deduction Matrix
o Transition Architecture State Evolution Table using TRM
o Impact Analysis - project list
o Dependency Analysis Report
o Implementation Factor Assessment and Deduction matrix
- Business Value Assessment (using BVA Technique)
- Implementation and Migration Plan (outline)

Architecture Artifacts may include the following:

- TOGAF: Project Context Diagram
- TOGAF: Benefits Diagram

Security Adaptations for ADM

- Evaluate tested and re-usable security software and resources.
- Identify new code/resources/assets appropriate for re-use
- Determine what can go wrong

Phase F: Migration Planning

- Finalize the Architecture Roadmap and the supporting Implementation and
Migration Plan
- Ensure that the Implementation and Migration Plan is coordinated with the
enterprise's approach to managing and implementing change in the enterprise's
overall change portfolio
- Ensure that the business value and cost of work packages and Transition
Architectures is understood by key stakeholders

- The focus of Phase F is the creation of an Implementation and Migration Plan in
co-operation with the portfolio and project managers.
- Phase E provides an incomplete Architecture Roadmap and Implementation and
Migration Plan that address the Request for Architecture Work. In Phase F this
Roadmap and the Implementation and Migration Plan are integrated with the
enterprise's other change activity.
- Activities include assessing the dependencies, costs, and benefits of the various
migration projects within the context of the enterprise's other activity. The
Architecture Roadmap, Version 0.1 and Implementation and Migration Plan,
Version 0.1 from Phase E will form the basis of the final Implementation and
Migration Plan that will include portfolio and project-level detail.
- The architecture development cycle should then be completed and lessons
learned documented to enable continuous process improvement.

- TOGAF: Request for Architecture Work
- TOGAF: Capability Assessment
- TOGAF: Communications Plan
- TOGAF: Organizational Model for Enterprise Architecture
- Tailored Architecture Framework
- TOGAF: Statement of Architecture Work
- TOGAF: Architecture Vision
- TOGAF: Architecture Repository
- TOGAF: Architecture Definition Document
- TOGAF: Architecture Requirements Specification
- TOGAF: Change Request
- TOGAF: Architecture Roadmap
- TOGAF: Transition Architecture
- TOGAF: Implementation and Migration Plan

- Confirm Management framework interactions with the Implementation and
Migration Plan
- The 4 management frameworks are:
o Business planning that conceives, directs, and provides the resources for
all of the activities required to achieve concrete business
o Enterprise Architecture that structures and gives context to all enterprise
activities delivering concrete business outcomes primarily but not
exclusively in the IT domain.
o Portfolio/Project Management that co-ordinates, designs, and builds the
business systems that deliver the concrete business outcomes.
o Operations Management that integrates, operates, and maintains the
deliverables that deliver the concrete business outcomes.
- Assign a business value to each project
o Performance Evaluation Criteria are used by portfolio and capability
managers to approve and monitor the progress of the architecture
o Return-on-Investment Criteria have to be detailed and signed off by the
various executive stakeholders.
o Business Value has to be defined as well as techniques, such as the value
chain, which are to be used to illustrate the role in achieving tangible
business outcomes. Business value will be used by portfolio and capability
managers to allocate resources and, in cases where there are cutbacks,
business value in conjunction with return on investment can be used to
determine whether an endeavor proceeds, is delayed, or is canceled.
o Critical Success Factors (CSFs) should be established to define success for
a project and/or project increment. These will provide managers and
implementers with a gauge as to what constitutes a successful
o Measures of Effectiveness (MOE) are often performance criteria and many
corporations include them in the CSFs. Where they are treated discretely,
it should be clear as to how these criteria are to be grouped.
o Strategic Fit based upon the overall enterprise architecture (all tiers) will
be the critical factor for allowing the approval of any new project or
initiative and for determining the value of any deliverable.
- Estimate resource requirements, project timings, and availability/delivery vehicle
- Prioritize the migration projects through the conduct of a cost/benefit assessment
and risk validation
- Confirm Transition Architecture increments/phases and update Architecture
Definition Document
- Generate the Architecture Implementation Roadmap (time-lined) and Migration
- Establish the architecture evolution cycle and document lessons learned.

- Implementation and Migration Plan (detailed)
- Finalized Architecture Definition Document
- Finalized Architecture Requirements Specification
- Finalized Architecture Roadmap
- Transition Architecture
- Re-Usable Architecture Building Blocks (ABBs)
- Requests for Architecture Work (for sub-projects)
- Architecture Contracts for implementation projects
- Implementation Governance Model
- Change Request arising from lessons learned

Phase G: Implementation Governance

- Formulate recommendations for each implementation project
- Govern and manage an Architecture Contract covering the overall
implementation and deployment process
- Perform governance functions while the systems is being implemented and
- Ensure conformance with defined architecture by implementation projects and
other projects
- Ensure that the program of solutions is deployed successfully as a planned
program of work
- Ensure that conformance of the deployed solution with the Target Architecture
- Mobilize supporting operations that will underpin the future working lifetime of
the deployed solution.
- Internal Development projects, utilize a Memorandum of Understanding (MOU)
- Architecture Board should review all deviations from Architecture contract and
considers whether or not to grant a dispensation.

- Confirm scope and priorities for deployment with development management
- Identify deployment resources and skills
- Guide development of solutions deployment
- Perform enterprise Architecture Compliance Reviews
- Implement business and IT operations
- Perform post-implementation review and close the implementation

- TOGAF: Architecture Contract (signed)
- TOGAF: Compliance Assessments
- TOGAF: Change Requests
- Impact Analysis
- Architecture-compliant solutions deployed
o The architecture-compliant deployed system
o Populated Architecture Repository
o Architecture compliance recommendations and dispensations
o Recommendations on service delivery requirements
o Recommendations on performance metrics
o SLAs
o TOGAF: Architecture Vision (updated with post-implementation info)
o TOGAF: Architecture Definition Document (updated with post-
implementation info)