Enterprise Systems

Enterprise Architecture
11-01-2021
Lecture No:15
 Enterprise Architecture – Introduction

• Why Enterprise Architecture

- aligning Business with IT
• Enterprise architecture (EA) is the practice of
analyzing, designing, planning and implementing
enterprise analysis to successfully execute on
business strategies. EA helps businesses structure
IT projects and policies to achieve desired
business results and to stay on top of industry
trends and disruptions using architecture
principles and practices, a process also known as
enterprise architectural planning (EAP).
 Benefits with Enterprise Architecture
• Align business and IT objectives and resources
• Efficient decision-making through established principles,
models, standards, and processes
• Improve communication, prioritization, and authority of
enterprises
• Increase time-to-market by reducing lead time for installing
and testing technology (have the technology ready before it is
needed)
• Simplify integration problems through compliance with
architecture
• Reduce costs by reserved duplicative or non-operational assets
• Provide a foundation for skills development
• Follow an established roadmap for infrastructure development
 Following phases are defined for the Enterprise Architecture
evolvement

i p les
Introduction Input rin c i s ion Roadmap
P V
get
r
Ta

• EA Definition Problem Statement Principles • View

• Goals •architecture • what it is • Architectural changes
• Structure • business • how to define • Business changes
• Layers • application • what it defines • Organization
• Roles • information • EA realization
• Governance • technology Target Vision
• Deliverables • infrastructure • common understanding
• Measurements • governance • definition of architecture
• processes • architectural framework
• ‘to be’ architecture
• ownership of HBG EA
•

4
 Enterprise Architecture Definition
EA enables:
 Alignment between Business and IT
 Authority
 Transition
 Realisation of Business and IT Strategies
• EA provides reference material in many forms
• EA ensures the architecture is maintained and used
• EA works at many levels
• EA is not just passive or reactive, it is proactive
Enterprise Architecture layers and structure
• The gap between Business and IT is something that has to
be manageable and controlled; how to plan, build and
maintain.
• Enterprise Architecture can be the ‘vehicle’ to align
Business with IT.
• Good EA planning and good EA engineering can be
managed using a EA framework and a EA method.
• Enterprise Architecture links strategy formulation through
ensuring that “the right things are done” - upstream EA
• Enterprise Architecture assets ensure that “things
are done right” when building specific solutions –
downstream EA
 Enterprise Strategy Strategy
Business Technology = “the city’s purpose & goals”
Bus Strategy IT Strategy
Strategy Opportunity Availability

Doing the right things!

Enterprise wide Focus

Enterprise Architecture
Enterprise Architecture
= “the city plan”

Planning

”Downstream EA”
Good Engineering

Doing things right!

System Design
Program Focus

Business Operating Environment

and IT Infrastructure = “the buildings”
Design n i
I
mi
t

n i
I t
mp l
i e
a
i
g r
d e
l
a
e r
v
i

a
i
l
P
n f
I
.U
B

G r

D e

i
t
t
y e

a s t
r
O u
t s
i
t
me
.U
B

o u p I
A r
c
T

n v i
n n in g
a / D
u c t
r
o u
r c
i
u r
g
n
e
D re
a
W

e s f
v
i
n
r

e
v
g t
o
i
h
sta e

e
t
n i
i
f

o c
o t
n me
e s ig n

s
t

n t
u
o
h

n g t
i h e
cu m
yst In
S
o
D
Ae
trW

o c
f
sa
m
n
e
p h
ra
t M
G

ifrM
N
l IS
ica

m le
sto
t/M
e
n
u
C
id
M
n g
a
g iln
n
a ce

c t
u r
o n
i
e
rS re
fstru
a
w
n ra
m
Pla nnin g/ Desi gn

n t
m
e
vic
cet u
stu re

s e d
u

s e
u
o n
h n e
e w

o n
d
v
t
n

s
i o n
i
Ini t

I
D e
P l
a
i at iv es

f
n a
r
i
s
n n
i

Ke yG r
t
s
n &
g
g
n
u c
r t u r
e

oup D ecisi on
Inf r ast r uct ur e Ini t iat iv es

n t
I e
WA N (

E n

U p
g r

E s
t
C o
m
C e
n t
m
i
-
r

d U s
n f
I r s
a

b l
a i
o mp a
c

r
t
d e
a

e t
p
e
r
e
e
u c
u r
t

h I
s
l
p

r
.
e

c y
n
T
y
n
)

e
O ut sour ci ng In it ia t

O
O u

H e
D e
t
n e
t
N E

s o
T WO R K

u r
w o
r

s o u
t
u
C o r
e
r
k

c
y s
s t

s o u
t
u
l
p
s
r
d e
t
k
c
s k
p
o
e
c
i ves

e N e
e
m

e
a
w
s

n d
C om pet en cy Cent r eI ni t iat i ves

l
E c
e
e r
S

a t
D

u s
C

e r
S v

O h e
t r
u s i
B
y s t
S
i o
K
e l
T
n e
r
t
c
i
v

W
a

o me
t

c
i
r
o n

s s U n i
e ms
s k s
e me
t r
y s y
s t
t
c
i
e D e

r
a

C e
h o u
e s e
v
i
l

r
t
n e
e

ms
e
y
r

Programme Architecture
and
l
P n n in g
a / d
e s ig
n t c
e
T C o mp
I e t
e n
c y c e
n t
r e Po int s

Soln Outline Inf r ast r uct ur e Ini t iat iv es

n t
I e
WA N (
m
i
-
r o mp a
c
l
p .
e
y
n
)
O ut sour ci ng In it ia t

O
N E T

t
u
W

o u r
s c
O R
K

e
i ves

l
E c
e
e r
S
r
t
c
i
v
o n
c
i
e D e

Macro Design Micro Design

C om pet en cyC ent r eI ni t iat i ves

v
i
l e y
r

Devt, etc.
Programme Architecture
n e w o r
t k
Pla nnin g/ Desi gn I nit i at iv es

p h
ra
G lIS
ica
a t
D W
a r
a h o u
e s e
.U
B re h
tW
a
D s e D
u
o Ce
m
cu
o m
so
tu
n id M
M rS
e
g
n
a lw e
rvic t
n
m
.U
B Nn
A
W
tra
In ifr iln
a
t/M
e c stru
stu
fra ce u
re
yst e
S sM a
m g e
n t
n
m

r
G o u
p I T O u t
s o u
r c N
e w
e
I r
f
n a t
s u c
r t u r
e E n
d U s e r C o r
e y s
s t m
e s
r
A c t
i
h e u r
t
c e D e
s i n &
g n f
I r s t
a r u c
u r
t e
e f
D n t
i i n
o P l
a n n
i g
n U p
g r d e
a

C u
s t me
o r

Delivery
S e
r v e
c
i e n t
C e
r
n i
I t a
i i
t e s f
v o c s e d
u o n
mig r
a t i
n g t
o t h n e
e w
d e
l e
v
i r y n v
e r
i n me
o t
n O u t
s o u
r c e
l
P n n in g
a / D
e s ig n H e p d e
l s k n d
a
n f
I a s t
r u c t
r u r
e D e s k
t p
o O t
h e r
B u s i
n e
s s U n i
t
O ut s
o u
r c
i g
n
n i
I t a t
i i e s f
v o c s e
u o n
d E s
a b l
t i h I
s T S y s
t e ms
C o
mp e t
e c y
n K i o
s k s
mp l
i e me t
n n g t
i h e v s
i o n
i
Ke yG r oup D ecisi on C e
n t
r e T e l
e me
t r
y s y
s t ms
e
l
P n n in g
a / d
e s ig
n
T C o mp
I e t
e n
c y c e
n t
r e Po int s e t
c

Soln Outline Macro Design Micro Design Devt, etc.

Change Programs

7
 Enterprise Architecture Framework
• Organising, storing and using architectural
information (models and building blocks) in
support of transition planning and delivery
project guidance
• The EA Framework provides the structure for
defining
and managing Enterprise Architecture assets
and functions as a reference catalog for use
in solution architecting
• Enterprise Capabilities:
• Capabilities and architecture principles are defined
to reflect and be regular with the business
direction i.e. business strategy and IT strategy

• Business Architecture:
• Business components or activities define “what the
business needs to do” to realize the capabilities
i.e. a business architecture has no concern for
the use of automation
• Information Systems Architecture:
Application & data (business-specific) and
technology (business-independent) services
define “what IT needs to do” to support the
business activities.

An Information Systems Architecture describes

those aspects of the business that are to be
automated – sometimes known as the “business
dependent IT architecture”
• Technology Architecture:
• Application and technology components are
structured into standard arrangements called
Reference Architectures i.e. a Technology
Architecture describes the underlying,
“business independent” IT architecture
needed to support automation
 The EA Framework consist of horizontal- and vertical aspects…

Operational
External to Functional Aspect of Aspect of
architecture Architecture Architecture

Enterprise
Capabilities
A good EA is
driven from an
assessment of the
Business
capabilities
Architecture
needed by the
enterprise It is helpful to We need to include
describe external elements that help
Information influences in a us deploy our
Systems consistent Business & IT
Architecture manner, such as systems in a
“requirements” consistent and
joined up fashion

Technology
Architecture
 …and then sub-dividing it into a number of “vertical”
aspects to complement our “horizontal layers”
Operational
External to architecture Functional Aspect of Architecture Aspect of Architecture

(Strategy) Events People Activities Data Location

Enterprise
Capabilities
We need to describe
the operational
We need to describe We need to describe the basic structure needed and
Business building blocks from which our used by the enterprise;
the events that the
Architecture architecture must systems are built. Typically, in together with the
support, in terms of an IT centric EA, these can be manner in which the
their business purpose categorised into… enterprise’s building
and their operational blocks are distributed
Information characteristics across this structure
Systems ...And data; and the
Architecture People, their roles and things required to
skills; and the things support their storage
required to give them and use within the
access to the enterprise’s IT systems
enterprise’s IT ...Activities and
Technology Processes; and the
systems…
Architecture things required to
automate and support
their execution within
the enterprise’s IT
systems…
13
Enterprise Architecture – using a
Method
Next….. class