togaf 9.1 adm summary

Preliminary Phase

Inputs:

Reference Materials External to the Enterprise:- TOGAF- Other architecture framework(s), if required

Non-Architectural Inputs- Board strategies and board business plans, business

strategy, IT strategy, business principles, business goals, and business drivers, when pre-existing

- Major frameworks operating in the business; e.g., portfolio/project management

- Governance and legal frameworks, including architecture governance strategy, when preexisting

- Architecture capability- Partnership and contract agreements

Architectural Inputs- Organizational Model for Enterprise Architecture:

- Scope of organizations impacted- Maturity assessment, gaps, and resolution

approach- Roles and responsibilities for architecture

team(s)- Budget requirements- Governance and support strategy

- Existing Architecture Framework, if any, including:- Architecture method- Architecture content- Configured and deployed tools- Architecture Principles- Architecture Repository

Steps:

Scope the Enterprise Organizations Impacted:- Identify core enterprise (units)- Identify soft enterprise (units)- Identify extended enterprise (units)- Identify communities involved (enterprises)- Identify governance involved

Confirm Governance and Support FrameworksDefine and Establish Enterprise Architecture Team and Organization:

- Deter mine existing enterpr ise and business capability- Conduct an enterpr ise architecture/business change

maturity assessment, if required- Identify gaps in existing wor k areas- Allocate key roles and responsibilities for enterprise

Architecture Capability management and governance- Define requests for change to existing business programs

and projects::- Infor m existing enterpr ise architecture and IT

architecture work of stakeholder requirements- Request assessment of impact on their plans

and work- Identify common areas of interest- Identify any critical differences and conflicts of

interest- Produce requests for change to stakeholder

activities- Determine constraints on enterprise architecture work- Review and agree with sponsors and board- Assess budget requirements

Identify and Establish Architecture PrinciplesTailor TOGAF and other Architecture Framework(s)

- Terms and ProcessImplement Architecture Tools

Objectives: 1. Determine the Architecture Capability desired by the organization2. Establish the Architecture Capability:

Outputs:

Organizational Model for Enterpr ise Architecture- Scope of organizations impacted- Matur ity assessment, gaps, and resolution approach- Roles and responsibilities for architecture team(s)- Constraints on architecture work- Budget requirements- Governance and support strategy

Tailored Architecture Framework- Tailored architecture method- Tailored architecture content (deliverables and artifacts)- Architecture Principles- Configured and deployed tools

Initial Architecture RepositoryRestatement of, or reference to, business principles, business goals, and business driversRequest for Architecture Work (optional)Architecture Governance Framework

Artifacts:Principles Catalog

Preliminary Phase Input Deliverables:

Architecture principlesArchitecture repositoryOrganization model for enterprise architectureTailored architecture framework

Output Deliverables:

Architecture principlesArchitecture repositiryBusiness principles, business goals, and business driversOrganization model for enterprise architectureRequest for architecture workTailored architecture framework

Requirements:

Architecture Vision Phase A

Inputs:

Reference Materials External to the Enterprise- Architecture reference materials

Non-Architectural Inputs- Request for Architecture Work- Business principles, business goals, and business drivers



approach- Roles and responsibilities for architecture

team(s)- Constraints on architecture work- Re-use requirements- Budget requirements- Requests for change- Governance and support strategy

- Tailored Architecture Framework:- Tailored architecture method- Tailored architecture content (deliverables and

artifacts)- Architecture principles, including business

principles, when pre-existing- Configured and deployed tools

- Populated Architecture Repository — existing architectural documentation (framework description, architectural descriptions, baseline descriptions, ABBs, etc.)

Steps:

Establish the Architecture ProjectIdentify Stakeholders, Concerns, and Business RequirementsConfirm and Elaborate Business Goals, Business Drivers, and ConstraintsEvaluate Business CapabilitiesAssess Readiness for Business TransformationDefine Scope

- The breadth of coverage of the enterprise- The level of detail required- The partitioning characteristics of the architecture- The specific architecture domains to be covered - The extent of the time period aimed at- The architectural assets to be leveraged, or considered for

use, from the organization’s Enterprise Continuum:Confirm and Elaborate Architecture Principles, including Business PrinciplesDevelop Architecture VisionDefine the Target Architecture Value Propositions and KPIs

- Develop the business case for the architectures and changes required

- Produce the value proposition for each of the stakeholder groupings

- Assess and define the procurement requirements- Review and agree the value propositions with the

sponsors and stakeholders concerned- Define the performance metrics and measures to be built

into the enterprise architecture to meet the business needs

- Assess the business riskIdentify the Business Transformation Risks and Mitigation Activities:

- Initial Level of Risk- Residual Level of Risk

Develop Statement of Architecture Work; Secure Approval

Objectives: 1. Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture2. Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision

Outputs:

Approved Statement of Architecture Work- Architecture project description and scope- Overview of Architecture Vision- Architecture project plan and schedule

Refined statements of business principles, business goals, and business driversArchitecture principlesCapability AssessmentTailored Architecture Framework

- Tailored architecture method- Tailored architecture content (deliverables and artifacts)- Configured and deployed tools

Architecture Vision- Problem description- Objective of the Statement of Architecture Work- Summary views- Business Scenario (optional)- Refined key high-level stakeholder requirements

Draft Architecture Definition Document, including- Baseline Business Architecture, Version 0.1- Baseline Technology Architecture, Version 0.1- Baseline Data Architecture, Version 0.1- Baseline Application Architecture, Version 0.1- Target Business Architecture, Version 0.1- Target Technology Architecture, Version 0.1- Target Data Architecture, Version 0.1- Target Application Architecture, Version 0.1

Communications PlanAdditional content populating the Architecture Repository

Artifacts:Stakeholder Map matrix,Value Chain diagramSolution Concept diagram

Architecture Vision Phase AInput Deliverables:

Architecture building blocksArchitecture principlesArchitecture repositoryBusiness principles, business goals, and business driversOrganization model for enterprise architectureRequest for architecture workSolution building blocksTailored architecture framework


Architecture principlesArchitecture roadmapArchitecture visionBusiness principles, business goals, and business driversCapability assessmentCommunications planStatement of architecture workTailored architecture framework

Requirements:

Business Architecture Phase B

Inputs:


Non-Architectural Inputs- Request for Architecture Work- Business principles, business goals, and business drivers- Capability Assessment- Communications Plan



approach- Roles and responsib. for arch. team(s)- Constraints on architecture work- Budget requirements- Governance and support strategy

- Tailored Architecture Framework:- Tailored architecture method- Tailored architecture content (deliverables and

artifacts)- Configured and deployed tools

- Approved Statement of Architecture Work- Architecture principles , including business principles,

when pre-existing- Enterprise Continuum- Architecture Repository

- Re-usable building blocks- Publicly available reference models- Organization-specific reference models- Organization standards

- Architecture Vision- Draft Architecture Definition Document, including

- Baseline/Target Business Arch., v 0.1- Baseline/Target Technology Arch., v 0.1- Baseline/Target Data Arch., v 0.1- Baseline/Target Application Arch., v 0.1

Steps:

Select Reference Models, Viewpoints, and Tools- Determine Overall Modeling Process

- Structured Analysis:- Use-case Analysis- Process Modeling:

- Identify Required Service Granularity Level, Boundaries, and Contracts

- Identify Required Catalogs of Business Building Blocks- Identify Required Matrices

- Business interaction matrix- Actor/role matrix

- Identify Required Diagrams- Identify Types of Requirement to be Collected

Develop Baseline Business Architecture DescriptionDevelop Target Business Architecture DescriptionPerform Gap Analysis

- Perform trade-off analysis to resolve conflicts (if any) among the different views

- Validate that the models support the principles, objectives, and constraints

- Note changes to the viewpoint represented in the selected models from the Architecture Repository, and document

- Test architecture models for completeness against requirements

Define Candidate Roadmap ComponentsResolve Impacts Across the Architecture LandscapeConduct Formal Stakeholder ReviewFinalize the Business ArchitectureCreate Architecture Definition Document

Objectives: 1. Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures

Outputs:

Refined and updated versions of the Architecture Vision phase deliverables, where applicable, including:

- Statement of Architecture Work- Validated business principles, business goals, and business

drivers- Architecture principles

Draft Architecture Definition Document, including- Baseline Business Architecture, Version 1.0- Target Business Architecture, Version 1.0

- Organization structure- Business goals and objectives- Business functions- Business services- Business processes, including measures and

deliverables- Business roles- Business data model- Correlation of organization and functions

- Views corresponding to the selected viewpoints addressing key stakeholder concerns

Draft Architecture Requirements Specification- Gap analysis results- Technical requirements - Updated business requirements

Business Architecture components of an Architecture RoadmapArtifacts:

Catalogs: Organization/Actor, Driver/Goal/Objective, Role, Business Service/Function, Location, Process/Event/ Control/Product, Contract/Measure

Matrices: Business Interaction matrix, Actor/Role matrix,

Diagrams: Business Footprint, Business Service/ Information, Functional Decomposition, Product Lifecycle, Goal/Objective/Service, Use-case, Organization Decomposition, Process Flow, Event

Business Architecture Phase BInput Deliverables:

Architecture building blocksArchitecture principlesArchitecture repositoryArchitecture roadmapArchitecture visionBusiness principles, business goals, and business driversCapability assessmentCommunications planOrganization model for enterprise architectureSolution building blocksStatement of architecture workTailored architecture framework


Architecture definition documentArchitecture principlesArchitecture requirements specificationArchitecture roadmapBusiness principles, business goals, and business driversStatement of architecture work

Requirements:

Information Systems Architectures Phase C

Inputs:


Non-Architectural Inputs- Request for Architecture Work- Capability Assessment- Communications Plan




- Tailored Architecture Framework:- Tailored architecture method- Tailored architecture content - Configured and deployed tools

- Application principles- Data principles- Statement of Architecture Work- Architecture Repository



- Baseline/Target Business Arch., v 1.0- Baseline/Target Data Arch., v 0.1- Baseline/Target Application Arch., v 0.1

- Draft Architecture Requirements Specification- Gap analysis results - Relevant technical req’s for Phase C

- Business Architecture components of an Architecture Roadmap

Steps:

Select Reference Models, Viewpoints, and Tools- Determine Overall Modeling Process- Identify Required catalogs of data or application building

blocks- Identify Required Matrices- Identify Required Diagrams- Identify Types of Requirement to be Collected

Develop Baseline Data or Appl. Architecture DescriptionDevelop Target Data or Appl. Architecture DescriptionPerform Gap Analysis





Define Candidate Roadmap ComponentsResolve Impacts Across the Architecture LandscapeConduct Formal Stakeholder ReviewFinalize the ArchitectureCreate Architecture Definition Document

Artifacts (Application):Catalogs: Application Portfolio, Interface

Matrices: Application/Organization, Role/Application, Application/Function, Application Interaction

Diagrams: Application Communication, Application and User Location, Application Use-Case, Enterprise Manageability, Process/Application Realization, Software Engineering, Application Migration, Software Distribution

Objectives: 1. Develop the Target Information Systems (Data and Application) Architecture, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures

Outputs:


- Statement of Architecture Work- Validated or new Data or Appl. principles

Draft Architecture Definition Document, including- Baseline Data or Appl. Architecture, Version 1.0- Target Data Architecture, Version 1.0

- Business data model- Logical data model- Data management process models- Data Entity/Business Function matrix

- Target Application Architecture, Version 1.0- Process systems model- Place systems model- Time systems model- People systems model


Draft Architecture Requirements Specification including such Information Systems Architecture requirements as:

- Gap analysis results- Data or Appl. interoperability requirements- Relevant technical requirements that will apply - Constraints on the Technology Architecture- Updated business requirements- Updated data or application requirements

Information systems components of an Architecture Roadmap (Data or Appl.)

Artifacts (Data):Catalogs: Data Entity/Data Component,

Matrices: Data Entity/Business Function, Application/Data

Diagrams: Conceptual Data, Logical Data, Data Dissemination, Data Security, Data Migration, Data Lifecycle

Information Systems Architectures Phase CInput Deliverables:

Architecture building blocksArchitecture definition documentArchitecture principlesArchitecture repositoryArchitecture requirements specificationArchitecture roadmapArchitecture visionCapability assessmentCommunications planOrganization model for enterprise architectureSolution building blocksStatement of architecture workTailored architecture framework


Architecture definition documentArchitecture principlesArchitecture requirements specificationArchitecture roadmapStatement of architecture work

Requirements:

Technology Architecture Phase D

Inputs:

Reference Materials External to the Enterprise- Architecture reference materials- Product information on candidate products





- Tailored Architecture Framework:- Tailored architecture method- Tailored architecture content - Configured and deployed tools

- Technology principles- Statement of Architecture Work- Architecture Repository



- Baseline/Target Business Arch., v 1.0- Baseline/Target Data/Appl. Arch., v 1.0- Baseline/Target Technology Arch., v0.1

- Draft Architecture Requirements Specification- Gap analysis results - Relevant technical req’s prev. phases

- Business, Data and Application Architecture components of an Architecture Roadmap

Steps:

Select Reference Models, Viewpoints, and Tools- Determine Overall Modeling Process- Identify Required catalogs of technology building blocks- Identify Required Matrices- Identify Required Diagrams- Identify Types of Requirement to be Collected- Select Services

Develop Baseline Data or Appl. Architecture DescriptionDevelop Target Data or Appl. Architecture DescriptionPerform Gap Analysis





Define Candidate Roadmap ComponentsResolve Impacts Across the Architecture LandscapeConduct Formal Stakeholder ReviewFinalize the technology ArchitectureCreate Architecture Definition Document

Objectives: 1. Develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholder concerns2. Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures

Outputs:


- Statement of Architecture Work- Validated or new technology principles

Draft Architecture Definition Document, including- Baseline Technology Architecture, Version 1.0- Target Data Architecture, Version 1.0

- Technology Components and their relationships to information systems

- Technology platforms and their decomposition, showing the combinations of technology required to realize a particular technology ‘‘stack’’

- Environments and locations- Expected processing load and distribution of

load across technology components- Physical (network) communications- Hardware and network specifications


Draft Architecture Requirements Specification including such Technology Architecture requirements as:

- Gap analysis results- Requirements output from Phases B and C- Updated technology requirements

Technology components of an Architecture Roadmap

Artifacts:Catalogs: Technology Standards, Technology Portfolio

Matrices: System/Technology

Diagrams: Environments and Locations, Platform Decomposition, Processing diagram, Networked Computing/Hardware, Communications Engineering

Technology Architecture Phase DInput Deliverables:

Architecture building blocksArchitecture definition documentArchitecture principlesArchitecture repositoryArchitecture requirements specificationArchitecture roadmapArchitecture visionCapability assessmentCommunications planOrganization model for enterprise architectureSolution building blocksStatement of architecture workTailored architecture framework


Architecture definition documentArchitecture principlesArchitecture requirements specificationArchitecture roadmapStatement of architecture work

Requirements:

Opportunities & Solutions Phase E

Inputs:

Reference Materials External to the Enterprise- Architecture reference materials- Product information on candidate products

Non-Architectural Inputs- Request for Architecture Work- Capability Assessment- Communications Plan- Planning methodologies


- See previous phases- Governance models and frameworks for:

- Corporate Business Planning- Enterprise Architecture- Portfolio, Program, Project Management- System Development/Engineering- Operations (Service)

- Tailored Architecture Framework:- See previous phases

- Statement of Architecture Work- Architecture Repository

- See previous phases- Architecture Vision- Draft Architecture Definition Document, including

- Baseline/Target BDAT Arch., v 1.0- Draft Architecture Requirements Specification

- Architectural requirements- Gap analysis results (BDAT)- IT Service Management requirements

- Change Requests for existing business programs and projects

- Candidate Architecture Roadmap components from Phases B, C, and D

Steps:

Determine/Confirm Key Corporate Change Attributes- Implementation Factor Assessment and Deduction matrix- transition capabilities of the organization units involved

Determine Business Constraints for ImplementationReview and Consolidate Gap Analysis Results from Phases B to D

- Consolidated Gaps, Solutions, and Dependencies matrixReview Consolidated Requirements Across Related Business FunctionsConsolidate and Reconcile Interoperability RequirementsRefine and Validate Dependencies

- Basis for most migration planningConfirm Readiness and Risk for Business Transformation

- Risks should be documented in the Consolidated Gaps, Solutions, and Dependencies matrix

Formulate Implementation and Migration Strategy- Greenfield: A completely new implementation- Revolutionary: A radical change- Evolutionary: A strategy of convergence, such as parallel

running or a phased approach to introduce new capabilities

- Quick win (snapshots)- Achievable targets- Value chain method

Identify and Group Major Work Packages (plateau’s)- Mainstream: Part of the future information system- Contain: Expected to be replaced or modified in the

planning horizon- Replace: To be replaced in the planning horizon

Identify Transition Architectures- Provide measurable business value

Create the Architecture Roadmap & Implementation and Migration Plan

- Management planning, high level

Objectives: 1. Generate the initial complete version of the Architecture Roadmap, based upon the gap analysis and candidate Architecture Roadmap components from Phases B, C, and D2. Determine whether an incremental approach is required, and if so identify Transition Architectures that will deliver continuous business value

Outputs:


- Statement of Architecture Work- Validated or new technology principles

Draft Architecture Definition Document, including- Baseline/Target BDAT Architecture, v1.0 updates- Transition Architecture, number and scope as necessary- Views corresponding to the selected viewpoints

addressing key stakeholder concernsDraft Architecture Requirements Specification including

- Consolidated Gaps, Solutions, and Dependencies Assessment

Capability Assessments, including:- Business Capability Assessment- IT Capability Assessment

Architecture Roadmap- Work package portfolio*- Identification of Trans. Architectures, including

- Relationship to Architecture Definition Document

- Implementation recommendations:- Criteria measures of effectiveness- Risks and issues- Solution Building Blocks (SBBs)

Implementation and Migration Plan, Version 0.1, including:- Implementation and Migration Strategy

Artifacts:Diagrams: Project Context, Benefits

Opportunities & Solutions Phase EInput Deliverables:

Architecture building blocksArchitecture definition documentArchitecture principlesArchitecture repositoryArchitecture roadmapArchitecture visionCapability assessmentCommunications planOrganization model for enterprise architectureSolution building blocksStatement of architecture workTailored architecture framework


Architecture definition documentArchitecture requirements specificationArchitecture roadmapArchitecture visionCapability assessmentImplementation and migration planStatement of architecture work

Requirements:

Migration Planning Phase F

Inputs:




- See previous phases- Governance models and frameworks for:

- Corporate Business Planning- Enterprise Architecture- Portfolio, Program, Project Management- System Development/Engineering- Operations (Service)

- Tailored Architecture Framework:- See previous phases

- Statement of Architecture Work- Architecture Repository

- See previous phases- Architecture Vision- Draft Architecture Definition Document, including

- Baseline/Target BDAT Arch., v 1.0- Transition Architectures, if any

- Draft Architecture Requirements Specification- Architectural requirements- Gap analysis results (BDAT)- IT Service Management requirements

- Change Requests for existing business programs and projects

- Architecture Roadmap, Version 0.1- Identification of work packages- Identification of Transition Architectures- Impl. Factor Assessm. and Deduct Matrix

- Capability Assessment- Business and IT Capability Assessment- Implementation and Migration Plan, v0.1

Steps:

Confirm Management Framework Interactions for the Implementation and Migration Plan

- Business Planning- Enterprise Architecture- Portfolio/Project Management- Operations Management

Assign a Business Value to Each Work Package- Performance Evaluation Criteria- Return-on-Investment Criteria- Business Value- Critical Success Factors (CSFs)- Measures of Effectiveness (MOE)- Strategic Fit

Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

- Resources and timingPrioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk ValidationConfirm Architecture Roadmap and Update Architecture Definition DocumentGenerate the Implementation and Migration PlanComplete the ADM and Document Lessons Learned

Objectives: 1. Finalize the Architecture Roadmap and the supporting Implementation and Migration Plan2. 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 portfolio3. Ensure that the business value and cost of work packages and Transition Architectures is understood by key stakeholders

Outputs:

Implementation and Migration Plan, Version 1.0 including:- Implementation and Migration Strategy- Project and portfolio breakdown of the implementation

- Allocation of work packages to project and portfolio

- Capabilities delivered by projects- Relationship to Target Architecture and any

Transition Architectures- Milestones and timing- Work breakdown structure

- Project charters (optional)- Related work packages- Business value- Risk, issues, assumptions, dependencies- Resource requirements and costs- Benefits of migration- Estimated costs of migration options

Finalized Architecture Definition Document- Finalized Transition Architectures, if any

Finalized Architecture Requirements SpecificationFinalized Architecture RoadmapRe-Usable Architecture Building BlocksRequests for Architecture Work for a new iteration of theADM cycle (if any)Implementation Governance Model (if any)Change Requests for the Architecture Capability arising from lessons learned

Migration Planning Phase FInput Deliverables:

Architecture definition documentArchitecture principlesArchitecture repositoryArchitecture roadmapArchitecture visionCapability assessmentCommunications planImplementation and migration planOrganization model for enterprise architectureSolution building blocksStatement of architecture work (contracts)Tailored architecture framework


Architecture building blocksArchitecture definition documentArchitecture requirements specificationArchitecture roadmapChange requestImplementation and migration planImplementations governance planRequest for architecture workStatement of architecture work

Requirements:

Implementation Governance Phase G

Inputs:


Non-Architectural Inputs- Request for Architecture Work- Capability Assessment


- See previous phases- Tailored Architecture Framework:

- See previous phases- Statement of Architecture Work- Architecture Repository

- See previous phases- Architecture Vision- Architecture Definition Document- Architecture Requirements Specification

- Architectural requirements- Gap analysis results (BDAT)

- Architecture Roadmap- Implementation Governance Model- Architecture Contract (standard)- Request for Architecture Work identified during Phases E

and F- Implementation and Migration Plan

Steps:

Confirm Scope and Priorities for Deployment with Development Management

- Review migration planning outputs and produce recommendations on deployment

- Identify enterprise architecture priorities for development teams

- Identify deployment issues and make recommendations- Identify building blocks for replacement, updates- Perform gap analysis on enterprise architecture and

solutions framework- Produce a gap analysis report

Identify Deployment Resources and SkillsGuide Development of Solutions DeploymentPerform Enterprise Architecture Compliance Reviews

- Review ongoing implementation governance and architecture compliance for each building block

- Conduct post-development reviews- Close development part of deployment projects

Implement Business and IT OperationsPerform Post-Implementation Review and Close the Implementation

- Conduct post-implementation reviews- Publish reviews and close projects

Objectives: 1. Ensure conformance with the Target Architecture by implementation projects2. Perform appropriate Architecture Governance functions for the solution and any implementation-driven architecture Change Requests

Outputs:

Architecture Contract (signed), as recommended in thearchitecture-compliant implemented architecturesCompliance AssessmentsChange RequestsArchitecture-compliant solutions deployed including

- The architecture-compliant implemented system- Populated Architecture Repository- Architecture compliance recommendations and

dispensations- Recommendations on service deliver y requirements- Recommendations on performance metrics- Service Level Agreements (SLAs)- Architecture Vision, updated post-implementation- Architecture Definition Document, updated post-

implementation- Business and IT operating models for the implemented

solution

Implementation Governance Phase GInput Deliverables:

Architecture definition documentArchitecture principlesArchitecture repositoryArchitecture visionImplementations governance modelOrganization model for enterprise architectureRequest for architecture workSolution building blocksStatement of architecture workTailored architecture framework


Change requestCompliance assessmentSolution building blocksStatement of architecture work

Requirements:

Architecture Change Management Phase H

Inputs:


Non-Architectural Inputs- Request for Architecture Work


- See previous phases- Tailored Architecture Framework:

- See previous phases- Statement of Architecture Work- Architecture Repository

- See previous phases- Architecture Vision- Architecture Definition Document- Architecture Requirements Specification

- Architectural requirements- Gap analysis results (BDAT)

- Architecture Roadmap- Change Request technology changes

- New technology reports- Asset management cost reduction initiatives- Technology withdrawal reports- Standards initiatives

- Change Request business changes- Business developments- Business exceptions- Business innovations- Business technology innovations- Strategic change developments

- Change Request from lessons learned- Implementation Governance Model- Architecture Contract (signed)- Compliance Assessments- Implementation and Migration Plan

Steps:

Establish Value Realization ProcessDeploy Monitoring Tools (BI, Benefits reviews)

- Monitor technology changes which could impact the Baseline Architecture

- Monitor business changes which could impact the Baseline Architecture

- Business value tracking; e.g., investment appraisal method to determine value metrics for the business objectives

- Monitor enterprise Architecture Capability maturity- Track and assess asset management programs- Track the QoS performances and usage- Deter mine and track business continuity requirements

Manage RisksProvide Analysis for Architecture Change Management

- Analyze performance- Conduct enterprise architecture performance reviews

with service management- Assess Change Requests and reporting to ensure that the

expected value realization and Service Level Agreement (SLA) expectations of the customers are met

- Under take a gap analysis of the performance of the enterprise architecture

- Ensure change management requests adhere to the enterprise architecture governance and framework

Develop Change Requirements to Meet Performance TargetsManage Governance Process

- Arrange meeting of Architecture Board- Hold meeting of the Architecture Board with the aim of

the meeting to decide on handling changes (technology and business and dispensations)

Activate the Process to Implement Change

Objectives: 1. Ensure that the architecture lifecycle is maintained2. Ensure that the Architecture Governance Framework is executed3. Ensure that the enterprise Architecture Capability meets current requirements

Outputs:

Architecture updates (for maintenance changes)Changes to architecture framework and principles (for maintenance changes)New Request for Architecture Work, to move to anothercycle (for major changes)Statement of Architecture Work, updated if necessaryArchitecture Contract, updated if necessaryCompliance Assessments, updated if necessary

Architecture Change Management Phase HInput Deliverables:

Architecture definition documentArchitecture principlesArchitecture repositoryArchitecture visionImplementations governance modelOrganization model for enterprise architectureRequest for architecture workSolution building blocksStatement of architecture workTailored architecture framework


Change requestCompliance assessmentSolution building blocksStatement of architecture work

Requirements:

Requirements Management

Inputs:

A populated Architecture RepositoryOrganizational Model for Enterprise Architecture

- Scope of organizations impacted- Maturity assessment, gaps, and resolution approach- Roles and responsibilities for architecture team(s)- Constraints on architecture work- Budget requirements- Governance and support strategy

Tailored Architecture Framework- Tailored architecture method- Tailored architecture content (deliverables and artifacts)- Configured and deployed tools

Statement of Architecture WorkArchitecture VisionArchitecture requirements, populating an Architecture Requirements SpecificationRequirements Impact Assessment

Steps:

Baseline requirements- Determine priorities arising from current phase of ADM- Confirm stakeholder buy-in to resultant priorities- Record requirements priorities and place in Requirements

RepositoryMonitor baseline requirementsIdentify changed requirements and record priorities

- Identify changed requirements and ensure the requirements are prioritized by the architect(s) responsible for the current phase, and by the relevant stakeholders

- Record new priorities- Ensure that any conflicts are identified and managed

through the phases to a successful conclusion and prioritization

- Generate Requirements Impact Statement for steering the architecture team

Update the Requirements Repository with information relating to the changes requested, including stakeholder views affected

Objectives: 1. Ensure that the Requirements Management process is sustained and operates for all relevant ADM phases2. Manage architecture requirements identified during any execution of the ADM cycle or a phase3. Ensure that relevant architecture requirements are available for use by each phase as the phase is executed

Outputs:

Requirements Impact AssessmentUpdated Architecture Requirements Specification

Artifacts:Catalogs: Requirements

Requirements Management Input Deliverables:

Architecture repositoryArchitecture requirements specificationArchitecture visionOrganization model for enterprise architectureRequirements impact assessmentStatement of architecture workTailored architecture framework


Architecture requirements specificationRequirements impact assessment

Requirements:

Architectual Artifacts

Cycles of Iteration