Introduction to Phase BCD
Instead of introducing phase B, C and D separately, we put them together because the three phases do share similar goals, objectives, approaches and steps, but just each phase focuses on a specific architecture domain. Preliminary
Goals Overview:
• Get the Architecture Right by creating and studying the followings: Business Architecture (Phase B) Information Systems Architectures (Phase C) Technology Architecture (Phase D)
A
• An enterprise architecture consists of three domains: Business Domain
B
H
Information systems domain Technology domain
• Each phase focuses on a specific architecture domain.
Requirements Management
G
C D
F E
© Copyright 2017 Visual Paradigm | All Rights Reserved 1
Phase B – Goals
Business Architecture
To-be Performed in Phase C and D
Recap Architecture Scope, Goals, Drivers, Constraints and Principles
Develop Baseline Business Architecture Description
Perform Gap Analysis
Mapping to Architecture Repository
Architecture Defintion Document
Develop Target Business Architecture Description
Develop Architecture Requirements Specification
• Develop Baseline Business Architecture Representing the components that form the business, and their inter-relationships today.
Architecture Requirements Specification
• Develop Target Business Architecture Which is the business architecture we want to become in the future.
2
Phase C – Goals Information Systems Architectures
To-be Performed in Phase C and D
Recap Architecture Scope, Goals, Drivers, Constraints and Principles
Develop Baseline Data Architecture Description
Develop Baseline Application Architecture Description
Develop Target Data Architecture Description
Develop Target Application Architecture Description
• Develop Baseline and Target Data Architecture Find out a compreshensive approach to data management, data migration and data governance.
Perfor Gap Analysis
Mapping to Architecture Repository
Architecture Defintion Document
Develop Architecture Requirements Specification
Architecture Requirements Specification
• Develop Baseline and Target Application Architecture Find out approach to the coordination of application resources.
3
Phase D – Goals Technology Architecture
Develop Baseline Technology Architecture Description
Perform Gap Analysis
Mapping to Architecture Repository
Architecture Defintion Document
Develop Target Technology Architecture Description
• Develop Baseline and Target Technology Architecture Represent how devices and physical software components are allocated in a way that can support the oprations of application components.
• Perform Gap Analysis
Develop Architecture Requirements Specification
Architecture Requirements Specification
Identify the differences between the baseline and target.
• Rationalize and justify the Architectural Approaches • Produce the Architecture Definition and Architecture Requirements Specification 4
Develop Architecture Definition Activities of Phase B, C and D
5
What is an Architecture Defintion? An Architecture Definition spans all architecture domains:
Business Business domain focuses on the product and service strategy, and the organizational, functional, process, information, and geographic aspects of the business environment.
Information System Information system domain focuses on IT system, services and processes, and the interfaces of those IT related resources.
Technology Technology domain focuses on the allocation and coordination of devices and physical software components in supporting IT services.
6
Domain Architectures will be developed: Baseline Architecture The TOGAF standard is a framework for creating an Enterprise Architecture capability in your organization
Target Architecture
Business (Phase B)
7
From Baseline to Target Architecture Target Architecture The Archimate views the model as a set of layers (Business, Application, and Technology) as well as some specialized extensions (Motivation, and Implementation and Migration).
Baseline Architecture
Information System (Phase C)
8
From Baseline to Target Architecture Baseline Architecture
Target Architecture
Technology (Phase D)
The ArchiMate language is an Open Group standard that provides an Enterprise Architecture modelling language. 9
Architecture Definition Overview In Phase B, C and D we will develop architectures for each of the three domains
Baseline architectures will be developed to present the current situation.
Baseline Architecture
Target Architecture
Business Architecture
Business Architecture
Application Architecture
Data Architecture
Application Architecture
Technology Architecture
Data Architecture
Technology Architecture
While the desired outcome will be represented the target architecture. In between the baseline and target architecture is what we called the gap. A gap consists of items thathave been left out, or added. We have to perform a gap analysis in finding out the changes, which constitue the basis of requirements of changes
Perform Gap Analysis
Develop Architecture Roadmap
Develop Mirgration Plan
10
TOGAF splits Enterprise Architecture Improve Competitiveness Three different domains Business, Application and Data Technology. Archimate also takes the same approach where in the three domains are considered as three different layers which are dependent on one another Archimate has separate metamodels for Business, Application and Technology layers and a different set of interaction diagrams between Business-Application layers and Application-Technology layers which are
Governance
Motivation Extension Preliminary
ArchiMate Core A
H
Requirements Management
G
Business Architecture
B
F
C
D
Data Application Architecture Architecture
Technology Architecture
E Implementation & Mirgration Extension 11
Business Architecture
12
Phase B Objectives
• 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 concerns. • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures.
13
Business Actors using the Stakeholder Viewpoint Represent the business stakeholders as business actors using the stakeholder viewpoint.
ArchiSurance
Home & Away Headquarters
Front Office
Homeowner’s & Travel Back Office
PRO-FIT Headquarters
Auto Back Office
Shared Service Center
Legally Yours Headquarters
Legal Expense Back Office
ArchiMate diagram is used to describe the organization structure: • The diagram focuses on the organization of the company, a department, or a network of companies. • In this example, the high level organization structure of ArchiSurance is presented, with its main locations and departments. • And here are the key stakeholders of the company. 14
Departments and Services Front Office
Homeowner’s & Travel Back Office
Auto Back Office
Shared Service Center
Legal Expense Back Office
15
Identify the Inter-Relationships between business actors and business functions
Homeowner’s & Travel Back Office Handle Claims
Underwriting
• With the key stakeholders identified, you can describe the major business functions involved in the business, grouped by stakeholders.
Actuarial Front Office
Investment Management
Customer
Finance Customer Relations
Submit Claims
Sales
Buy Insurance
Marketing
Get Informed
Auto Back Office
Shared Service Center
Handle Claims Document Processing Underwriting
Actuarial
Bank
Banking
Investment Management
Finance
• After that, evaluate the business functions by modeling the processes involved. • We can see that the three office can actually use the same set of services to get their work done.
Legal Expense Back Office Handle Claims
Underwriting
Investment Management
Actuarial
• By this way, you can factorize the commonalities of operations among them.
Finance
16
Inter-Relationship Breakdown Legal Expense Back Office
Home & Travel Back Office
Handle Claims
Underwriting
Investment Management
Actuarial
Finance
Share the Same Operations
Auto Back Office 17
Elaborate and Zoom In
Handle Claims
Handle Claims Claim Received
Capture Information
Notify Addition Stakeholders
Valuate Claims
Investigate
Pay Claim
18
Baseline Business Layer and Application Layer Handle Claims Capture Information
Claim Received
Scanning
Shared Service Center
Document Management System
Notify Addition Stakeholders
Customer Administration
Front Office
General CRM System
Valuate Claims
Investigate
Claims Administration
Printing
Pay Claim
Payment
Back Office
Legal Expense CRM System
Home & Away Policy Administration
Home & Away Financial Application
Auto Insurance Application
Legal Expense Back-Office System
• Model the application services that support the business operations, and the application components that provide the services. • When you perform this step, you may need to consider the fact that the same business function may be supported by different application services when before performed under different business domains. • Like in this case, the function handle claim may involve different services in handling different kinds of insurance.
19
Perform Necessary Factorization
Finally, create the target business architecture Maintain CRM Data Centrally
Support for Policy Administration
Support for Financial Transactions
Handle Claims Capture Information
Claim Received
Scanning
Shared Service Center
Notify Addition Stakeholders
CRM Data Access
Document Management Server
Pay Claim
Printing
Financial Services
Back Office
General CRM System
Document Management Back-up Server
Investigate
Policy Administration Services
Front Office
Document Management System
Document Management System
Valuate Claims
ArchiSurance Back Office Suite
ArchiSurance Back Office Suite
General CRM System
FO General Purpose Server
Auto Back-Up Server Cluster
ArchiSurance General-Purpose Service Cluster
• You will need to combine the various scenarios in figuring out the application services and components involved. • Finally, perform the necessary factorization and optimization and produce the target architecture. 20
Repeat and Analysis each of the Processes Legal Expense Back Office
Home & Travel Back Office
We had done the analysis for Handle Claims.
Handle Claims
Underwriting
Investment Management
Actuarial
Finance
Repeat those steps for the other 4 processes to complete the analysis for factorization of the commonalities or operations
Auto Back Office 21
Information Systems Architectures
22
Phase C Objectives
IT implementations is to meet company operations needs such as: • Automated their operations • Speed-up the decisions • Better control of organization resources
23
Information Systems Architectures Development The development of information systems architectures include two parts. (Data Architecture and Applications Architecture)
Data architecture describes the major relationships between the conceptual business objects and its logical data objects.
C
Information Systems Architecture
Data Architecture
Applications Architecture
24
Conceptual Data Model
Here is an ArchiMate diagram that shows a subset of the business objects that ArchiSurance defines. • Part of the customer information involves an insurance file, which is composed of insurance requests, insurance policies, and damage claims.
Cheque
Application
Order
Claim
• Besides, there is a number of specialized insurance policies defined, one for each type of the insurance type.
Customer
Insurance File
Insurance Request
Travel Insurance Policy
Insurance Policy
Homeowner’s Insurance Policy
Damage Claim
Auto Insurance Policy
Legal Expense Insurance Policy 25
Data Dissemination Diagram Showing the baseline business architecture
Data Dissemination Diagram • It shows the relationship between business objects, data entity, application components and functions.
Customer
• The diagram represents how the business objects are to be physically realized by application components.
Insurance File
Damage Claim
Insurance Policy
Policy Data
Claim Data
Home & Away Policy Administration Customer Data
Customer Data Access
Policy Data Management
26
Create Target Business Architecture Associating Business objects with Target Business Architecture:
• This is another Data Dissemination diagram, which shows the target architecture with the back office suite in-place, as a replacement of the policy administration component existing in the baseline.
Customer
Insurance File
Damage Claim
Insurance Policy
Policy Data
Claim Data
AchiSurance Back Office Suite Customer Data
27
Create Baseline Applications Architecture • It shows the overview of the current application landscape and the relation ships between the applications components in terms of the information flows, or the services they provide and consume.
Front Office CRM Data Legal Expense CRM System
Web Portal
customer data
call report Call Center Application
General CRM System call report
customer data
Back Office
Home & Away Financial Application
Shared Service Centre
Home & Away Policy Administration
Auto Insurance Application
document data
document data
Legal Expense Back-Office System
document data
document data Document Management System
28
Create Target Applications Architecture • The back office suite has been created, and it comprises a number of application components that support the various back office activities.
Front Office CRM Data
Web Portal
call report Call Center Application
call report
General CRM System
customer data
Back Office
ArchiSurance Back Office Suite Underwriting System
Policy Administration System
Claims System
Product Configurator Mgmt. System
Data Warehousing Solution
Business Rule Mgmt. System
Shared Service Centre
document data
document data
Document Management System
29
Technology Architectures
30
Phase D Objectives
Develop a Technology Architecture that will form the basis of the following implementation work.
31
Create Baseline Technology Architecture • It shows the software and hardware infrastructure elements supporting the Application architectures, such as physical devices, networks, or system software, such as operating systems and databases.
Home & Away Headquarters
Front Office
Homeowner’s & Travel Back Office
Web Portal Home & Away Financial Application FO Web Hosting Server
Call Center Application
Home & Away Policy Application
General CRM Legal Expense CRM System System
FO General Purpose Server
ArchiSurance General Purpose Server Cluster
Home & Away LAN
ArchiSurance WAN
PRO-FIT Headquarters
Legal Expense Back Office
PRO-FIT LAN Auto Back Office
Legally Yours Headquarters
Shared Service Center
Auto Insurance Application
Document Management System
Auto General-Purpose Server
Document Management Server
Legal Expense Back Office System Legal Expense General-Purpose Server
32
Create Target Technology Architecture • This is the proposed target architecture, with the integration of some systems.
Home & Away Headquarters Front Office
Homeowner’s Travel Back Office
Web Portal
ArchiSurance Back Office Suite
FO Web Hosting Server
Call Center Application
ArchiSurance General Purpose Server Cluster
General CRM System
Document Management System
FO General Purpose Server
Document Management Back-up Server
Home & Away LAN
ArchiSurance WAN
PRO-FIT Headquarters PRO-FIT LAN Shared Service Center
Document Management System
ArchiSurance Back Office Suite
33
Gap Analysis A method of assessing the differences in performance between a business' information systems or software applications to determine whether business requirements are being met and, if not, what steps should be taken to ensure they
Gap
are met successfully. Key factors for change Current State
Desired State
Action Plan
34
Perform Gap Analysis (Applications Architecture) customer data
Legal Expense CRM System
Web Portal
call report
Gap Analysis
Call Center Application
General CRM System
call report
Front Office customer data
Back Office
CRM Data Legal Expense CRM System
Web Portal
customer data
call report
Home & Away Financial Application
Home & Away Policy Administration
Front Office
document data CRM Data Baseline Shared Web Service PortalCentre
Call Center Auto Insurance Application Application
call report
Back Office document data
call report document data Call Center Application
call report
Document Management System customer data
Back Office
Home & Away Financial Application
General CRM System
Shared Service Centre
Legal Expense General CRM Back-Office System System
document data
Home & Away Policy Administration
document data
customer data
Auto Insurance Application
document data
Legal Expense Back-Office System
document data
ArchiSurance Back Office Suite
document data
document data
ArchiSurance Back Office Suite Underwriting System
Policy Administration System Product Configurator Mgmt. System
Target
Business Rule Mgmt. System
Document Management System
Claims System
Both in Baseline and Target
Data Warehousing Solution Only in Plateau Baseline
Only in Plateau Target 35
FO Web Hosting Server
Perform Gap Analysis (Technology Architecture) Home & Away Policy Application
General CRM Legal Expense System CRM System
Gap Analysis
FO General Purpose Server
Homeowner’s & Travel Back Office
Home & Away Policy Administration
Homeowner’s Travel Back Office ArchiSurance WAN
PRO-FIT Headquarters
ArchiSurance Back Office Suite
General CRM Legal Expense System CRM System
ArchiSurance General Purpose Server Cluster
Document Mnt. System
FO General Purpose Server Legally Yours Headquarters
Legal Expense Back Office
PRO-FIT LAN
Docment Mnt. Back-up Server
Home & Away LAN
FO Web Hosting Server
Call Center Auto Insurance Application Application
Home & Away Policy Application
FO Web Hosting Server
Home & Away Headquarters
Web Portal
Home & Away Financial Application
Web Portal
Home & Away LAN Front Office
Home & Away Headquarters
Front Office
ArchiSurance General Purpose Server Cluster
Shared Service Center ArchiSurance General Purpose Server Cluster
Baseline
General CRM System
FO General Purpose Server Auto General-Purpose Server
Document Document Management Management System System
ArchiSurance WAN
PRO-FIT Headquarters
Auto Back Office
Legally Yours Headquarters Legal Expense Back Office
Legal Expense General-Purpose PRO-FIT LAN Server
Document Management Server Document Management Back-up Server
Home & Away LAN
Legal Expense Back Office System
Shared Service Center
Auto Insurance Application
Document Management System
Auto General-Purpose Server
Document Management Server
Legal Expense Back Office System Legal Expense General-Purpose Server
ArchiSurance WAN ArchiSurance Back Office Suite
PRO-FIT Headquarters PRO-FIT LAN
ArchiSurance Back-u Server Cluster
Shared Service Center
Document Management
Both in Baseline and Target
Target
ArchiSurance Back Office Suite
Only in Plateau Baseline
Only in Plateau Target 36
Typical Steps for Performing Gap Analysis
1 2 3 4
Identify Strategic Objectives
Identify Current Standings and Deficiencies
Create a Plan of Action
Back Up Your Plan of Action with Data and Analysis
37
Develop Architecture Requirements Specification
38
Architecture Requirements Specification
• Provide a set of quantitative statements that outline what an implementation project must do in order to comply with the architecture. • Form a major component of an implementation contract or contract for more detailed Architecture Defintion
39
Qualitative View & Quantitative View
Baseline Architecture
Target Architecture
(”As is”)
(”To be”)
Architecture Definition Document
Architecture Requirements Specification
Provide a Qualitative View of the solution and aims to communicate the intent of the architect.
Provide a Quantitative View of the solution, stating measurable cristeria that must met during the implementation of the architecture.
40
Architecture Requirements Objective: Outline what has to do to comply with the target architecture Conditions or capabilities an organization must conform in creating and enterprise architecture.
REQ
Baseline Architecture
Target Architecture Gap
41
Architecture Requirements – Examples
Separate back-office servers wil be replaced by a shared server cluster located in the data center at Home & Away Headquarters to reduce maintenance cost and to solve the problem of data redundancy.
Describes a necessary change to components in an architecture Describes the reasons behind the change
42
Architecture Requirements – Examples
Upgrade of O/S is required because the version we use currently is outdated and does not support the technology we need.
Explain the limitations and constraints of the existing architecture components.
Besides describing the change required, other requirement may include the limitation of the existing architecture components, which is the outdated O/S makes it impossible to support the technology required.
43
Key Performance Indicator
KPI Key: A major contributor to the success or failure of architecture work Performance: A metric that can be measured and quantified Indicator : Representation of performance required Use Key Performance Indicator (KPI) to measure the compliance of architecture works 44
Key Performance Indicator
KPI KPI
Measurement of Compliance
Profit in 6 months
> 1.5m
Expenditure of hardware
< 1.3m
Customer complaints
< 30 new cases per week
45
D C B e s a h P f to
l u s e R
46
Results Production of Deliverables: Print
Architecture Definition Document
â&#x20AC;˘ Produce the baseline, target and the gap for the three architecture domains â&#x20AC;˘ Completion of architecture model development
Architecture Requirements Specification
47