Enterprise Systems

Enterprise Architecture
Methodologies
13-01-2021
Lecture # 16
 The structure of the architecture areas in the EA Method
Client
Objectives Proposal and Meeting Planning

Enterprise Capabilities

Transition

Emerging
Opportunities Business Architecture
Strategic Gap Analysis
Current
Environment

IS Architecture
Technology Architecture

Governance

2
From the ‘Enterprise Architecture’ on ‘one page’ there is a relation to the EA
Method and the EA Framework
Enterprise Enterprise
Architecture on Architecture
one page Method

Enterprise Capabilities

Enterprise
Business Architecture Architecture
Framework

IS Architecture

Technology Architecture
3
 The concept of work product dependencies suggestions at another dimension in
which to think about an EA’s architecture framework

Functional view
Enterprise Capabilities

Data view
User view
Capability Business
Model Strategic CBM Directions
Resources Enterprise Architecture Framework
EA Business
EA Guiding Overview Scenarios
Principles
Business
Diagram
Architecture

Business Architecture Business

Showing only a few, Architecture
IT
representative, work Business Business Event Business Architecture
product Activity Mdl
Enterprise
List Structure
dependencies Usage Information
Matrices Enterprise KPIs Users
Model
Locations
Roles Business Reference
Technology Architecture
Market Business
Business Plans
Plans Insured Party Sponsoring Organization Prospects
POLICY

Insured Objects Policy Insurance Product Policy Financials

Info

Architectures IS Architecture
Claim
Claim Objects
Claimant
Claimant Claim
Claim
Service Providers Producer Producer Compensation
Business Partners

Third Parties External Agencies Legal & Recovery Actions

Training, Education,
Education, AdviceInquiries

Applications Data
IT Components IT Nodes IS Architecture
Application Deployment
Groups Standard Use Unit Matrices
Technology Reference Architectures Cases
Data Deployment
Technology
Stores Standard NFRs
Units (IS) Technology
Architecture
Architecture
User Groups Placement
IS Reference Architectures Guidelines

4
 We can develop this way of thinking about an EA architecture
framework a little more.
Business Architecture
Enterprise Architecture Framework
Functional Aspect of Architecture

Business
A business architecture has no
Architecture
regard for the use of automation

IT
Information Systems Architecture Architecture
“line of
Users automation”
An information systems architecture
describes those aspects of the business
that are to be automated – sometimes
Market Business Plans Insured Party Sponsoring Organization Prospects

POLICY

Insured Objects Policy

Policy Insurance Product Policy Financials
Info

known as the “business dependent IT

Claim Objects

Claimant
Claimant Claim
Claim Service
Service Providers
Providers Producer
Producer Producer Compensation Business Partners

architecture”
Third Parties External Agencies Legal & Recovery Actions Training,
Training, Education,
Education, Advice
Advice Inquiries

Applications Data

Technology Architecture

Technology “line of
A technology architecture describes business
Architecture
the underlying, “business interest”
independent” IT needed to support
automation
5
 Enterprise Architecture Deliverables

• From the abstract EA level to actual

documentations
ALL deliverables created by Solution Architects across the business and IT architecture domains should, ideally, be guided
by the EA’s framework… which may be at its most powerful when the Solution Architect also uses the Work Products

PLAN BUILD RUN

Enterprise 1 Business and
Architecture Programmes & Projects 2 IT environment
n
Business
Business Solution
Architecture Work Products
Business
Infrastructure

IT Solution Requirements Analysis WPs

IS Architecture Information
Systems
Infrastructure

IT Solution Architecture
Technology
Architecture Technology
Infrastructure

Solution Guidance Solution Deployment

7
Enterprise Architecture Governance – ‘doing it right

“Balancing good Enterprise Design with good Solution Design”

EA Authority area - the Architecture Management Processes

Roles, Responsibilities.
An enterprise will use its Enterprise Architecture to guide the interpretation
of its business and IT strategies across the multiple layers of its development

Strategy

Architecture
Enterprise
Architecture

Dev’t Programme Infrastructure

Architecture

Programme, or Architecture
Solution
Architecture
Project P P Infra. Proj

Architecture Arch

Dev’t Dev’t D D D D D

06/08/2021 9
 The Enterprise Architecture Governance consist of
‘three bodies’
 Ensure solution designs comply with the
architecture
 Maintain the architecture

Architecture Review
Board
 Decides on which Technical Review
architecture is best suited Board
for the needs of the
enterprise
 Decides when a change in
the architecture is
needed Architecture Sponsors
 Prioritise Initiatives
Enterprise Architects
 Uses the architecture to
best satisfy the project’s
Project Design
needs Solution Architects
Authority

10
 We have the ‘important peoples’ – approving the architecture…

Invited
Council Enterprise
chair Architects

Chief
Architect
Architecture Review Business
Board Representatives
Technical Review
Board

A.C.A.
“Architecture
Council”:
maintaining the ARB
authority of the
EA TRB
Project Design
PDA
Authorities

11
 we have the ‘clever peoples’ - creating the architectures

Chief
Business experts Architect

Architecture Review
Board
Project Architects Enterprise
Technical Review
Board Architects

ARB
The Office of the
Chief architect: TRB
maintaining the
Project Design DA
vitality and use of
Authorities the EA

12
we have the peoples who will use the architecture in the solution projects

Architecture Review
Board
Technical Review
Board

Solution Projects
with
Design Authorities
Project Design
Authorities

13
 These three bodies exercise a number of different processes…

Is used by the TRB

Is used by the ARB Is used by the TRB

SeSelelec ction
tion
CCo
onnfo
form
rma
annce
ce liltiyty
ita
VVita
Enterprise
Enterprise
Architecture
Architecture
Management
Management
Is used by the ARB Processes
Processes
nnss CCo
o ommm
ce pptitio muun
EExxce nicicati
ation
Used by all on

14
 that work together to ensure the architecture is managed
and exploited to the benefit of the enterprise as a whole

Making
Planning
Busi ness
Admi nistration

Business Planning
Product
Management

Sector Marketing
Plans
Acquisitions
Customer
Portfolio
Managem ent
Customer
Service and Sales

Customer Portfolio
and Analysis Customer Servicing
Product
Operations

Product Operations
Customer
Accounting

Customer Accounting
Financial
Management

Risk Management
an EA Using an
EA
& and Sales Planning Management Policies
Analysis Business Architec ture Managing Products
Credit and Risk
Management
Acquisition Planning
Busi ness Unit and Oversight
Administration
Securitization
Application
Manage Alliance Processing Case Handling
Checks Relationships Operations
& Admi nistration Reconciliations
Policy & Procedure
Controls Manuals
Product Development
and Deployment Customer Behavior Financial Control
Decisioning Service/ Sales
Administration
HR Management

Treasury
Sales and Cross- Authorizations Billing
Administer Alliance Sell
SLAs Target Lists
(Prospecting) Customer Profile Financial
Marketing Financial Capture Payments Consolidation
Audit/ QA/ Legal
E x te r n a l C o rp o ra te
DMZ In t e r n a l N e tw o r k D o m a in
E n v ir o n m e n t
Execution Facilities Servicing
Contact/ Event Product Processing
Market Research History (Dialogue Handler)
Customer Account D ir e c t o r y a n d S e c u r ity
Collections and
Develop and Operate Campaign Execution Recovery N ode
Systems Rewards Management
Corr espondence

Use
Product Directory Smart Routing
Accounting and G/L Inventory Management
Merchant Operations
C o n te n t
P e r s o n a l iz a t i o n
M anagem ent
N o de
N ode

Public & Private Networks

C lie n t

Enterprise Firewall Node

Protocol Firewall Node

Domain Firewall Node

Node

Edge Server Node

R e v e rs e W eb In t e g r a tio n E n t e r p r is e
P ro x y W e b P o rta l A p p lic a tio n Hub S y s te m s
N o de Node S e rv e r N ode N ode
N o de

E x te r n a l
S ys te m s
N ode

D a ta b a s e
T ran sco de r
S e rv e r
Node
N ode

W e b S e r v ic e s
Cre

G a te w a y
sh
S y s te m s
M anagem ent
E x te r n a l
N ode
S e r v ic e s
D ir e c t o r y
bl i

N e tw o r k
ate

I n t r u s io n
D e t e c tio n N o d e
Pu

over n
G
Vitality On Demand – Technology Overview – Detail

B Collaborati
P
View
Reporting
C
Workflow Acquired
u ono o
…
…

Policy
…

Personaliza
Services ETL
Services
…

s Presentatio
r Based tion
m
i nt Orchestrati Integration
m
on Applica Framework
n
…

a tion so
…

e Business
l Web Connec Adaptors/ n
s Connection
Services tivity Connectors
Mediation Events
s Service
S License Data Access
MeteringRating Billings Mgmt
e Policy
Services S Services
…Services
Capacity
S
ntr Based Manageme
e
e vOrchestrati nt r
r i on v
…
v c i
i e c
c s e
e s
s

Vitality

15
 Enterprise Architecture as a Management Tool
Strategic and
long term;
Value Proposition

General Business Product

Business Vision
Management Roadmap

Planning and Design

Product Market Needs Product Line
Development Operation Plans

Architecture Architecture Architecture

Technical Vision
Office Principle, Vision Roadmap

Construction and
Delivery

16
Enterprise Architecture Measurements
Next------Class