by Dr. Vsevolod S.

Chernyshenko

Process of identifying projects, programs, or portfolios that effectively deliver the Target Architecture identified in previous phases
Consolidate gaps mentioned in phases A to D Formulate Strategy a high level Implementation and Migration

Articulate the clients way from Baseline Architecture to Target Architecture

o What are the requirements analysed o What are the dependencies o What are the risks

 To review the target business objectives and capabilities, consolidate the gaps from Phases B to D, and then organize groups of building blocks to address these capabilities To review and confirm the enterprise's current parameters and ability to absorb 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 Implementation and Migration Strategy on an outline

 Output of Preliminary phase

Output of Architecture Vision phase

Output of Business Architecture phase

Output of Information System Architecture phase

Output of Technology Architecture phase

 Implementation and Migration Plan

Finalized Architecture Definition Document

Finalized Architecture Requirements Specification

Finalized Architecture Roadmap

Finalized Transition Architecture

1. Determine/Confirm Key Corporate Change Attributes 4. Review IT Requirements from a Functional Perspective 7. Confirm Readiness and Risk for Business Transformation

2. Determine Business Constraints for Implementation 5. Consolidate & Reconcile Interoperability Requirements 8. Formulate High-Level Implementation and Migration Strategy 11. Create Portfolio and Project Charters & Update the Architectures

3. Review & Consolidate Gap Analysis Results from Phases B to D

6. Refine & Validate Dependencies

9. Identify & Group Major Workpackages

10. Identify Transition Architectures

Step 1: Determine/Confirm Key Corporate Change Attributes

Create an Implementation Factor Assessment and Deduction Matrix
Implementation Factor Assessment and Deduction Matrix

Factor <Name of factor>

Change in technology

Description <Description of factor>

Shut down the message centers, saving 700 personnel, and have them replaced by email

Deduction <Impact on Migration Plan>

Need for personnel training, re-assignment Email has major personnel savings and should be given priority

All factors, gathered in the following steps should be documented in the Implementation Factor Assessment and Deduction matrix Assess Transition Capabilities

Step 1: Determine/Confirm Key Corporate Change Attributes

Assess Transition Capabilities: For corporate organization and any partner organizations
o organizational impact on shaping the Transition Architecture o assignment of responsibilities within the organization for the implementation
o corporate cultural influences for handling change

For enterprise, and specifically the IT organization

o organization and culture of the enterprise and the IT organization o enterprise personnel skill sets o gap analysis between the Baseline and Target Architectures

Step 2: Determine Business Constraints for Implementation

Identify any business drivers that would constrain the sequence of implementation

Steps:
Review Corporate Strategic Plan Review the Enterprise Architecture Maturity Assessment Review Corporate Line-of-Business Strategic Plans

Step 3: Review and Consolidate Gap Analysis Results from Phases B to D

Create an Implementation Factor Assessment and Deduction Matrix
Consolidated Gaps, Solutions, and Dependencies Matrix

No.
1

Architecture
Business

Gap
New Order Processing Process

Potential Solutions

Dependencies

Use COTS software Drives tool process Implement applications custom solution (No X)

Review the Phase B, C, and D Gap Analysis Results Rationalize the Consolidated Gaps, Solutions, and Dependencies Matrix

Step 4: Review IT Requirements from a Functional Perspective

Assess the IT requirements, gaps, solutions, and factors to identify a minimal set of functional requirements Integration into work packages would efficient and effective implementation lead to a more

Steps:
Assess the IT Requirements from a Functional Perspective Determine Issues Associated with Functional Integration

Updating Consolidated Gaps, matrix, listing the new "gaps"

Solutions,

and

Dependencies

Step 5: Consolidate and Reconcile Interoperability Requirements

Ensure that there are no interoperability conflicts

Step 6: Refine and Validate Dependencies

Assess key dependencies:

Business dependencies
Information dependencies Workflow dependencies

IT dependencies
Foundation dependencies

Step 7: Confirm Readiness and Risk for Business Transformation

Determine implementation approaches that will be feasible for both tactical and strategic success

Step 8: Formulate High-Level Implementation and Migration Strategy

Overall solutions strategy that will guide implementation Steps: Determine Overall Strategic Implementation Direction
o Greenfield: start from the beginning o Revolutionary: radical change o Evolutionary: phased approach

Determine an Implementation Approach

o most common implementation include: Quick win Achievable targets Value chain method

methodology

recommendations

Step 9: Identify and Group Major Work Packages

Group the architectural activities into a set of portfolios and projects (work packages) Use Consolidated Gaps, Solutions, and Dependencies matrix and Implementation Factor Assessment and Deduction matrix

Steps:
Identify Major Work Packages Analyze the Work Packages

Step 10: Identify Transition Architectures

Step 11: Create Portfolio and Project Charters and Update

the Architectures

by Dr. Vsevolod S. Chernyshenko

Formulation of an Implementation and Migration Plan that realizes some or all of the Transition Architectures identified in Phase E

 Ensure that the Implementation and coordinated with management frameworks

Migration

Plan

is

Prioritize work packages and projects, by assigning business value and conducting a cost/business analysis Finalize the Architecture Vision and Architecture Definition Documents, in line with the agreed implementation approach Confirm the Transition Architectures with relevant stakeholders Create, evolve, and monitor the detailed Implementation and Migration Plan

 Output of Preliminary phase

Output of Architecture Vision phase Output of Business Architecture phase Output of Information System Architecture phase Output of Technology Architecture phase

Draft Architecture Requirements Specification

Output of Opportunities and Solutions phase

 Implementation and Migration Plan Finalized Architecture Definition Document Finalized Architecture Requirements Specification

Finalized Architecture Roadmap

Finalized Transition Architecture

 Confirm Management Framework Implementation and Migration Plan

Interactions

for

Establish the Architecture Evolution Cycle and Document Lessons Learned

1. Confirm Management Framework Interactions for Implementation and Migration Plan

2. Assign a Business Value to Each Project

3. Estimate Resource Requirements, Project Timings, & Availability/Delivery Vehicles

4. Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment & Risk Validation
6. Generate the Architecture Implementation Roadmap (Time-Lined) and Migration Plan

5. Confirm Transition Architecture Increments/Phases and Update Architecture Definition Document

7. Establish the Architecture Evolution Cycle and Document Lessons Learned

Step 1: Confirm Management Framework Implementation and Migration Plan

Interactions

for

Four management frameworks that have to work closely together for the Migration Plan Business Planning Enterprise Architecture

Portfolio/Project Management
Operations Management

Steps 2-6: Architecture Change to be managed in Project Management tasks

Assign a Business Value to Each Project

Estimate Resource Requirements, Availability/Delivery Vehicles

Project

Timings,
Conduct of

and
a

Prioritize the Migration Projects through the Cost/Benefit Assessment and Risk Validation

Confirm Transition Architecture Increments/Phases and Update Architecture Definition Document

Generate the Architecture Lined) and Migration Plan

Implementation

Roadmap

(Time-

Step 7: Establish the Architecture Document Lessons Learned

Evolution

Cycle

and

Strategic enterprise Architecture Definition and Transition Architectures treated as configuration items o managed in accordance with an accepted standard e.g. Information Technology Infrastructure Library (ITIL) Enterprise Architectures must be kept up-to-date o By iterative evolution cycles

Lessons learned are crucial within a learning organization!! o should be documented and assessed as part of enterprise evolution process

the

by Dr. Vsevolod S. Chernyshenko

Providing an implementation

architectural

oversight

of

the

 Formulate recommendations for each implementation project

Govern and manage an Architecture Contract overall implementation and deployment process covering the

Perform appropriate governance functions while the solution is being implemented and deployed
Ensure conformance with the defined architecture

 Ensure that the program of solutions is deployed successfully

Ensure conformance of the deployed solution with the Target Architecture

Mobilize supporting operations that will working lifetime of the deployed solution

underpin

the

future

 Output of Preliminary phase

Output of Architecture Vision phase Output of Business Architecture phase Output of Information System Architecture phase Output of Technology Architecture phase

Draft Architecture Requirements Specification

Output of Opportunities and Solutions phase Output of Migration Planning phase

o Implementation and Migration Plan

 Architecture contract
Compliance Assessments Change results Architecture-compliant solutions deployed

 Populated Architecture Repository

Architecture compliance recommendations and dispensations Recommendations on service delivery requirements Recommendations on performance metrics Service Level Agreements (SLAs)

Architecture Vision, updated post-implementation

Architecture Definition Document, updated post-implementation Transition Architecture, updated post-implementation Business and IT operating models for the implemented solution

1. Confirm Scope & 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

by Dr. Vsevolod S. Chernyshenko

Providing an implementation

architectural

oversight

of

the

 Ensure that baseline architectures continue to be fit-for-purpose

Assess the performance of recommendations for change the architecture and make

Assess changes to the framework and principles set up in previous phases

Establish an architecture change management process for the new enterprise architecture baseline Maximize the business value from the architecture and ongoing operations Operate the Governance Framework

 Organizational Model for Enterprise Architecture

Tailored Architecture Framework Statement of Architecture Work Architecture Vision Architecture Repository

Architecture Definition Document

Architecture Requirements Specification

 Architecture Roadmap
Change Request Transition Architecture Implementation Governance Model Architecture Contract (signed)

Compliance Assessments
Implementation and Migration Plan

 For maintenance changes Architecture updates Changes to architecture framework and principles For major changes New Request for Architecture Work, to move to another cycle Update if necessary Statement of Architecture Work Architecture Contract Compliance Assessments

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

What (risks)

Change or replacement of the eWorkspace. Incompatibility of provided solutions and modern IT-technologies, code decay (browsers, OS, platforms, etc.). Deterioration of processing software. New law(-s) and burocracy requirements Probably five-seven years, if university will not decide to change their eWorkspace.

When

How

Update purchased software. Reprogram our parts of eWorkspace, or just recode them with new SDK, IDE. Implement new technologies. Train members of Processing office, show and explain them new solutions in processing software.

Steps
1

Non-functional requirements
Fulfillment of wishes User can satisfy all his demands in record transcription in the most comfort, easy way.

Functional requirements

A way to comply

Communicate with university staff before launching the software implementation, know their expectations and wishes. Stable eWorkspace Careful updating under Modification of the workspace supervision of the should be safe and not noticed by developers from university users. in closed network. Qualitative, unhurried tests. Completeness Observing real-life work, Project can be finished only in providing all kinds of tests, case of reliability of new meeting no incomprehension technologies operation. among university staff and students.