Introduction to Phase E
In Phase B, C and D, we’ve developed the baseline and target architectures for different domains, and recognized their gaps in between. Preliminary
Goals Overview:
• Identify the delivery vehicles to effectively deliver the Target Architecture: Work packages Transition Architectures (if required) Implementation and migration plan
A H
B
Requirements Management
G
F
C
D
E © Copyright 2017 Visual Paradigm | All Rights Reserved 1
Opportunities and Solutions
2
Phase E Activities
• Identify and detail the work packages, transition architectures to develop the implementation and migration plan. • Work packages are the logical group of changes • Transition architectures are the intermediate architectures in between the baseline and target outlining the status of the enterprise architecture at specific times • Implementation and migration plan is the schedule of projects for realizing the target architecture 3
Major changes identified from Gap Analysis In phase B, C and D you’ve performed gap analysis. You know what components will be added, and removed, but there are still some questions we need to answer before you can go realizing the differences. Gap Analysis
Front Office
Gap Analysis
CRM Data Legal Expense CRM System
Web Portal
customer data
Home & Away Headquarters
Front Office
Homeowner’s & Travel Back Office
Home & Away Financial Application
Web Portal
call report Call Center Application
General CRM System
Home & Away Policy Application
FO Web Hosting Server
call report
Home & Away Policy Administration General CRM Legal Expense System CRM System
customer data
Back Office
ArchiSurance General Purpose Server Cluster
Document Mnt. System
FO General Purpose Server
Docment Mnt. Back-up Server
Home & Away Financial Application
Home & Away Policy Administration
Auto Insurance Application
Legal Expense Back-Office System
ArchiSurance Back Office Suite
Home & Away LAN
ArchiSurance WAN
Shared Service Centre
document data
document data
document data
document data
PRO-FIT Headquarters
document data Auto Back Office
Shared Service Center
Document Management System
Both in Baseline and Target
Only in Plateau Baseline
Auto Insurance Application
Document Management System
Auto General-Purpose Server
Document Management Server
Only in Plateau Target
Legally Yours Headquarters Legal Expense Back Office
PRO-FIT LAN
Legal Expense Back Office System Legal Expense General-Purpose Server
ArchiSurance Back Office Suite ArchiSurance Back-u Server Cluster
Both in Baseline and Target
Only in Plateau Baseline
Only in Plateau Target
4
Develop Architecture Roadmap
5
Architecture Roadmap What are the changes required to realize the target architecture?
Work Packages Will there be any intermediate states throughout the changes?
Transition Architectures What’s the schedule of the delivery of changes?
Implementation and Migration Plan
6
Implementation Factor Assessment Factor
Description
Deduction
Upgrade of server O/S
Upgrade the server machines to the latest version of Linux
• Need for training • Update of various guidelines writen for old O/S
Factor is typically a kind of • Risk • Issue • Assumption • Dependency • Impact
Examples Risk - a reduction of profit due to the temporary suspension of service Issue - an outdated system Assumption - it is supposed that the staff will have the required knowledge to use the new system without further training Dependency - back-up must be done before kick-off Impact - the dismissal of employees 7
Implementation Factor Assessment Factor
Description
Deduction
Upgrade of server O/S
Upgrade the server machines to the latest version of Linux
• Need for training • Update of various guidelines writen for old O/S
Source
• Problem statement • Business cases • Gaps identified in previous phases
8
Implementation Factor Assessment Factor
Description
Deduction
Upgrade of server O/S
Upgrade the server machines to the latest version of Linux
• Need for training • Update of various guidelines writen for old O/S
Source Need for training
• Problem statement • You can identify the factors based on the problem statement, the business cases created, and • Business cases the gap identified. • Gaps identified in previous phases
• New factors deduced by assessing a given factor. The new factor usually leads to a decision of extra work, a reminder of problem awareness or further plan for communication • By assessing the factors deduced, new factors can be found, constituting the actions or changes needed to be taken to implement the target architecture.
9
Consolidated Gaps, Solutions & Dependencies Matrix No.
Architecture
Gap
Potential Solutions
Dependencies
1
Business
Integrate Front-End CRM for three Organization Units
Use COTS CRM to replace the existing one
Drives application, information and non-IT factors in (2) & (3) accordingly
2
Application
The new CRM needs to support issue to be sent to the back-end system
...
...
3
Information
• We can consolidate and integrate the gap analysis results from the Business, Information Systems, and Technology Architectures (created in Phases B to D) and assess their implications with respect to potential solutions and inter-dependencies. This should be done by creating a Consolidated Gaps, Solutions, and Dependencies matrix
10
Business Transformation
Improve Competitiveness
Baseline Architecture
Target Architecture
Gap
• Business transformation is the process to reach the desired target architecture from where you are today, which is the baseline architecture. • A gap, represents the difference between the baseline and target.
11
Business Transformation
Improve Competitiveness
Baseline Architecture
Target Architecture
Gap
Project A
Project B
Project C
• To better represent the work required to fill-in the gap, identify the projects, which are the grouped activities that must be performed to achieve the target architecture and associate them with the gap.
12
Business Transformation
Improve Competitiveness
Baseline Architecture
Target Architecture
Gap
Project A
Project B
Project C
Work Packages
Work Packages
Work Packages
• But project can be very big. What you have to do is to decompose work into smaller, more manageable components until satisfied that, the work is defined at a sufficient level of detail to estimate time, cost and resource.
13
Work Packages Description
• Summary of Work • Relationship to Oppurtunity
• Relationship to Architecture Definition • Relationship to Architecture Requirements
Work Packages
Business Value
Objective & Approach
Functional Requirements
Dependecies with other Work Package
Outcome & Deliverables
14
Specify a Package Description
Functional Requirements
Describe what will be performed under this work package and the expected outcome. You may also explain the reason of initiating the work package, the pre-requisites, and relationship to opportunity, architecture definitions and architecture requirements.
Specific functionality that define what the work package is supposed to accomplish.
Business Value
Dependencies with Other Work Packages
Describe the value the work package will deliver upon its successful completion. Here are some kinds of business values you can think about: economic value/profit, employee value, customer value, supplier value, partner value, managerial value, marketing value, societal value, etc.
The completion of a work package may rely on the prior completion (or partial completion) of other work packages. State the dependencies between work packages in a way that allows audiences to understand the priority and sequencing of implementation efforts.
Objective Approach
Outcome and Deliverables
State the target to achieve in concrete manner (e.g. Setup of back-up server). Describe the direction or the way chosen to reach the target (e.g. Change the existing, obsolete data server to a back-up server).
Both tangible and non-tangible outcome upon the success completion of work package.
15
Business Transformation
Baseline Architecture
Target Architecture
• If there are little changes between baseline and target architecture, the changes can probably be implemented within a short period of time, which is nice • But if this is not the case
16
Business Transformation
Baseline Architecture
Transition Architecture
Transition Architecture
Target Architecture
• You might want to add multiple milestones in between the baseline and target • Each milestone is known as a transition architecture, which describes the enterprise at an architecturally significant state between the Baseline and Target Architectures. • You start from the baseline and make some changes in a transition architecture. And make some more changes in the next transition architecture, until all changes are implemented
17
Business Transformation: Pattern 1
One after Another • There are several patterns in representing the possible intermediate situations that may happen in between the baseline and target. • The first pattern is straightforward. • You start from the baseline architecture, and then reaching the transition architecture, finally the target architecture.
18
Business Transformation: Pattern 2
AND Junction
To Accomplish Multiple Target Architectures Simultaneously • This is another pattern, which involves the use of an And junction. If there are sufficient resources to carry out the changes required to meet multiple transitions in parallel, use the And junction to connect them.
19
Business Transformation: Pattern 3
OR Junction
Accomplish Either of the Two (or more) Transition Architectures • Besides the And junction, there is also an OR junction.
• Obviously the Or junction means either one.
• Either aim to reach this transition architecture first, or another one.
• The transition architecture here is a combination of the two previous transition architectures.
• It means that no matter which transition architecture to reach first, the next phase of activity would be to get the remaining part complete.
20
Develop Implementation and Migration Plan
21
Implementation and Migration Plan
CRM System Integration
Staff Training
• This activity focuses on the scheduling and sequencing of work. • It involves determining the dependencies among work packages and creating schedule for implementation activities.
22
Project A
PERT Chart
Project B
CRM System Integration
Staff Training
• Tasks are the alternative form of work packages. • In order to represent the dependencies among work packages, form a PERT chart with the work packages, and establish connectivity between tasks. • A PERT chart stands for Program Evaluation Review Technique, which helps you to create diagram workflows, milestones, schedules, time tables, critical paths, and other planning requirements for a project. • The connections between tasks represent their dependencies. 23
PERT Chart Closer Look
For each task in a PERT chart, specify the task name, which is the name of the work package, by default.
Task Name ID Start Date
CRM System Integration 001
48 days
Dec 16, 2016
Feb 02, 2017 Peter
Duration End Date Responsible Person
• An ID that uniquely identifies the task. • The planned start and finish date of the task. Note that a task can only be start if the depending task is completed. In other words the start date of a task must be greater than the finish date of all the depending tasks. • The duration, which is the number of days between start and end date. And, The person who are responsible for this task.
24
Mirgration Roadmap
describes a timeline of the progression from the Baseline Architecture, to the Target Architecture.
• The projects, and the work packages are listed vertically in the roadmap. Jan
Feb
May
Jun
Jul
Work Package N
Target Architecture
Project A
Apr
• Major check points are indicated as triangles below the timeline.
Work Package M
Work Package O
Work Package W
Project B
Baseline Architecture
Mar
• On top of the roadmap there is a timeline.
Work Package X
• The durations of work packages are shown as bars.
Work Package Y Work Package Z
Transition A
Transition B
• The bottom part of the roadmap shows the transition architectures, if any, with the planned available date indicated by the vertical line. • You can optionally indicate the points of investment as well.
25
E e s a h P f o t l Resu
26
Results Production of Deliverables: Print
• Produces a detailed Architecture Roadmap and Migration Plan • The identification of work packages, transition architectures, and the creation of migration plan
Architecture Roadmap
Implementation and Migration Plan
Architecture Reqirements Specification (updated)
27