SIA LESSON.pptx

JOURNAL OF STRATEGIC INFORMATION SYSTEMS
ACHIEVING BENEFITS WITH
ENTERPRISE ARCHITECTURE
GRAEME SHANKSA,⁎, MARIANNE GLOETA, IDA ASADI SOMEHB, KEITH
FRAMPTONA, TOOMAS TAMMC
THE UNIVERSITY OF MELBOURNE, AUSTRALIA
PUBLISHED IN 7 MARCH 2018
ADVANCE MANAGEMENT INFORMATION SYSTEM
INSTRUCTOR: ASST. PROF. DR. MÜESSER NAT
PREPARED BY MUNSF SOKIYNA
DEPARTMENT OF MIS

OUTLINE
• What is Enterprise Architecture?
• Enterprise Architecture definitions.
• Enterprise Architecture types
• When we use EA?
• Enterprise architecture Diagrams.
• Enterprise Architecture Frameworks.
• How Enterprise architecture align business ?
• Short video .

OUTLINE
• The emergence of Enterprise Architecture?
• Enterprise Architecture definitions.
• Enterprise Architecture types
• When we use EA?
• Enterprise architecture Diagrams.
• Enterprise Architecture Frameworks.
• How Enterprise architecture align business ?
• Short video .

WHAT IS ENTERPRISE
ARCHITECTURE ?
• The concept of enterprise architecture was discovered in 1978
by IT and Business Consultant John Zachman, who published
his popular article in “IBM journal”, Its title was "A framework
for Information Technology Architecture "(Hermans, 2015).
• Systems Development Life Cycle (SDLC).

ENTERPRISE ARCHITECTURE DEFINITIONS
• Enterprise Architecture (EA) defines the current and desirable
future states of an organization's processes, capabilities,
application systems, data, and IT infrastructure and provides a
roadmap for achieving this target from the current state (Ross
et al., 2006; Tamm et al., 2011; Zachman, 1987).
• EA has been traditionally conceptualized as a collection of
artefacts that represent an organization's business systems and
IT systems, together with a planning process for documenting
these systems (Ross et al., 2006).
• EA includes details about an organization's processes,
capabilities, data, application systems and IT infrastructure
using a variety of standardized representation techniques
(Kaisler et al., 2005; Lankhorst, 2013).

ENTERPRISE ARCHITECTURE DEFINITIONS
• The Open Group definition : Enterprise Architecture is about
understanding all of the different components that go to make
up the enterprise and how those components inter-relate.
• Wikipedia :Enterprise Architecture is the practice of applying a
comprehensive and rigorous method for describing a current
and/or future structure and behavior for an organization's
processes, (information) systems, personnel and organizational
sub-units, so that they align with the organization's core goals
and strategic direction. Although often associated strictly with
information technology, it relates more broadly to the practice
of business optimization in that it addresses business
architecture, performance management, organizational
structure and process architecture as well.

Enterprise architecture is a complete expression
of the enterprise; a master plan which “acts as a
collaboration force” between aspects of business
planning such as goals, visions, strategies and
governance principles; aspects of business
operations such as business terms, organization
structures, processes and data; aspects of
automation such as information systems and
databases; and the enabling technological
infrastructure of the business such as computers,
IFEAD

ENTERPRISE ARCHITECTURE TYPES
• Business architecture: business process,
organization, people.
• Information system architectures
• Data or information architecture: data and Information
• Application architecture: Services
• Technology architecture: hardware, software,
network.

When we use Enterprise
architecture.
System complexity—Organizations were
spending more and more money building IT
systems.
Poor business alignment—Organizations
were finding it more and more difficult to
keep those increasingly expensive IT
systems aligned with business need.

THE POSITION OF IT ARCHITECTS
Weknow
solutions to every
problem? What’s
your problem?
HowdoI know
what I want,
when I don’t
knowwhat you
candofor me
it
IT
TOGAF - The Continuing Story

Business architecture that
defines the organisation
What to do, Where to do it, and
How to do it?
Business
Strategy
Applications and information
Information
Systems
Infrastructure that supports the IS
Technology
The Enterprise Architecture discipline defines and
maintains the architecture models, governance, and
transition initiatives needed to effectively co-ordinate
semi-autonomous groups towards common
business and IT goals

Business
Technology
Information
Systems
Strategy
Documentation of organisation capabilities,
resources, product portfolio, external interfaces,
high-level business process blueprint that
supports the strategy
Infrastructure that supports the IS:
- Technical components: servers, networks, etc.
- Technology: platforms, etc.
Applications and information that support the
business and implement the business functions in
the IT systems
Assets that define the enterprise
strategy, goals and objectives.
What to do, and how to do it?

ENTERPRISE ARCHITECTURE FRAMEWORKS
• An architectural framework is a tool for:
• Designing a broad range of a architectures.
• Assisting the evaluation of different architectures.
• Selecting and building the right architecture for an
organization.

ZACHMAN’S EA FRAMEWORK
TDT4252, Spring 2013
LECTURE 14 - ENTERPRISE
ARCHITECTURE: ZACHMAN,
TOGAF
2
1
d e r
SCOPE
M
O
DEL
(
C
O
N
C
E
P
T
U
A
L
)
ENTERPRISE
gner
Y S T E M
ODEL
OGCAL)
ODEL
H
Y
S
I
C
A
L
)
DETAILED
R
E
P
R
E
S
E
N
-
TATIONS (
O
U
T
-
OF-
C
O
N
T
E
X
T
)
Sub-
Contractor
FUNCTIONING
ENTERPRISE
e.g.DATA
FUNCTI
e
.g
.D
a
ta
D
e
fin
itio
n
Ent=Field
Reln=Adres
E
C
H
N
O
L
O
G
Y
e
.
g
.
P
h
y
s
i
c
a
l
D
a
t
a
M
o
d
e
l
E
n
t
=
S
e
g
m
e
n
t
/
T
a
b
l
e
/
e
t
c
.
R
e
l
n
=
P
o
i
n
t
e
r
/
K
e
y
/
e
t
c
.
Ent=DataEntity
R
e
l
n
=
D
a
t
a
R
e
l
a
t
i
o
n
s
h
i
p
e
.
g
.
S
e
m
a
n
t
i
c
M
o
d
e
l
L
i
s
t
o
f
T
h
i
n
g
s
I
m
p
o
r
t
a
n
t
(
C
O
N
T
E
X
T
U
A
L
)
t
o
t
h
e
B
u
s
i
n
e
s
E
N
T
I
T
Y
=
C
l
a
s
o
f
BusinesThing
ListofPr
oce
se
sthe
B
u
s
i
n
e
s
P
e
r
f
o
r
m
s
F
u
n
c
t
i
o
n
=
C
l
a
s
o
f
Busine
sProce
s
I/O=
U
s
e
r
V
ie
w
s
n
e
.
g
.
S
y
s
t
e
m
D
e
s
i
g
n
P
r
o
c
.
=
C
o
m
p
u
t
e
r
F
u
n
c
t
i
o
n I
/
O
=
D
a
t
a
E
l
e
m
e
n
t
s
/
S
e
t
s
e.g.Program
P
r
o
c
.
=
L
a
n
g
u
a
g
e
S
t
m
t
I/O=
C
o
n
t
r
o
l
B
l
o
c
k
e.g.FUNCTION
e
.
g
.
B
u
s
i
n
e
s
P
r
o
c
e
s
M
o
d
e
l
Ent=BusinesEntity P
r
o
c
.
=
B
u
s
i
n
e
s
P
r
o
c
e
s
R
e
l
n
=
B
u
s
i
n
e
s
R
e
l
a
t
i
o
n
s
h
i
p
I
/
O
=
B
u
s
i
n
e
s
R
e
s
o
u
r
c
e
s
L
i
s
t
o
f
L
o
c
a
t
i
o
n
s
i
n
w
h
i
c
h t
h
e
B
u
s
i
n
e
s
O
p
e
r
a
t
e
s
N
o
d
e
=
M
a
j
o
r
B
u
s
in
e
s
Location
e
.g
.B
u
s
i
n
e
s
L
o
g
i
s
t
i
c
s
S y s t e m
N
o
d
e
=
B
u
s
i
n
e
s
L
o
c
a
t
i
o
n
L
i
n
k
=
B
u
s
i
n
e
s
L
i
n
k
a
g
e
e.g.LogicalDataModel e
.
g
.
A
p
l
i
c
a
t
i
o
n
A
r
c
h
i
t
e
c
t
u
r
ee.g.DistributedSystem
N
o
d
e
=
I
/
S
F
u
n
c
t
i
o
n
P
r
o
c
.
=
A
p
l
i
c
a
t
i
o
n
F
u
n
c
t
io (
P
r
o
c
e
s
o
r
,
S
t
o
r
a
g
e
,
e
t
c
)
L
i
n
k
=
L
i
n
e
C
h
a
r
a
c
t
e
r
i
s
t
i
c
s
L
i
n
k
=
L
i
n
e
S
p
e
c
i
f
i
c
a
t
i
o
n
s
e
.
g
.
N
e
t
w
o
r
k
A
r
c
h
i
t
e
c
t
u
r
e
Node
=Adre
se
s
L
in
k
=
P
r
o
to
c
o
ls
e.g.NETWORK
Architecture
Planer
O
S
M
( L I
Desi
T
M
( P
Buil
wner
Builder
ENTERPRISE
M
O
DEL (
C
O
N
C
E
P
T
U
A
L
)
Designer
SYSTEM
M
O
DEL
(
L
O
G
I
C
A
L
)
T
E
C
H
N
O
L
O
G
Y
M
O
DEL
(
P
H
Y
S
I
C
A
L
)
DETAILED
R
E
P
R
E
S
E
N
-
TATIONS (
O
U
T
-
O F
C
O
N
T
E
X
T
)
Sub-
Contractor
e
.
g
.
R
u
l
e
S
p
e
c
i
f
i
c
a
t
i
o
n
E
n
d
=
S
u
b
-
condition
Means=Step
End=Condition
M
e
ans=Action
E
n
d
=
B
u
s
i
n
e
s
O
b
j
e
c
t
i
v
e
M
e
a
n
s
=
B
u
s
i
n
e
s
S
t
r
a
t
e
g
y
E
n
d
s
/
M
e
a
n
s
=
M
a
j
o
r
B
u
s
.
G
o
a
l
/
C
r
i
t
i
c
a
l
S
u
c
e
s
F
a
c
t
o
r
e
.
g
.
P
r
o
c
e
s
i
n
g
S
t
r
u
c
t
u
r
e e
.
g
.
,
B
u
s
i
n
e
s
R
u
l
e
M
o
d
e
l
Time=SystemEvent E
n
d
=
S
t
r
u
c
t
u
r
a
l
A
s
e
r
t
i
o
n
C
y
c
l
e
=
P
r
o
c
e
s
i
n
g
C
y
c
l
e M
e
a
n
s
=
A
c
t
i
o
n
A
s
e
r
t
io
n
Time
=Ex
e
cute
T
i
m
e
=
I
n
t
e
r
u
p
t
C
y
c
l
e
=
M
a
c
h
i
n
e
C
y
c
l
e
e
.g.SCHEDULE
T
i
m
e
=
B
u
s
i
n
e
s
E
v
e
n
t
C
y
c
l
e
=
B
u
s
i
n
e
s
C
y
c
l
e
P
e
o
p
l
e
=
M
a
j
o
r
O
r
g
a
n
i
z
a
t
i
o
n
s
T
i
m
e
=
M
a
j
o
r
B
u
s
i
n
e
s
E
v
e
n
t
e.g.WorkFlowModel e
.
g
.
M
a
s
t
e
r
S
c
h
e
d
u
l
e
P
e
o
p
l
e
=
O
r
g
a
n
i
z
a
t
i
o
n
U
n
i
t
W
o
r
k
=
W
o
r
k
P
r
o
d
u
c
t
People=Role
Wo
r
k
=
D
e
l
i
v
e
r
a
b
l
e
e.g.TechnologyArchitecturee.g.PresentationArchitecturee.g.ControlStructure e.g.RuleDesign
N
o
d
e
=
H
a
r
d
w
a
r
e
/
S
y
s
t
e
m
Software P
e
o
p
l
e
=
U
s
e
r
Work=ScrenFormat C
y
c
l
e
=
C
o
m
p
o
n
e
n
t
C
y
c
l
e
e
.
g
.
S
e
c
u
r
i
t
y
A
r
c
h
i
t
e
c
t
u
r
e e
.g
.T
imin
g
D
e
fin
itio
n
P
e
o
p
le
=
Id
e
n
tity
Work=Job
e
.
g
.
O
R
G
A
N
I
Z
A
T
I
O
N
Planer
Owner
ListofEventsSignificant L
i
s
t
o
f
B
u
s
i
n
e
s
G
o
a
ls
/
S
t
r
a
t
totheBusines
L
i
s
t
o
f
O
r
g
a
n
i
z
a
t
i
o
n
s
I
m
p
o
r
t
a
n
t
o
t
h
e
B
u
s
i
n
e
s
D A T A W
hat O N H o w N E T PEOPLE Wh o T I ME W
he n M
O
TI V
A
TI O
N W
hy
J
o
h
n
A
.Z
a
c
h
m
a
n
,Z
a
c
h
m
a
n
I
n
t
e
r
n
a
t
i
o
n
a
l(
8
1
0
)
2
3
1
-
0531
SCOPE (
C
O
N
T
E
X
T
U
A
L
)
e
.
g
.
H
u
m
a
n
I
n
t
e
r
f
a
c
e
Architecture
e.g.STRATEGY
FUNCTIONING
ENTERPRISE
e
.g.Busine
sPlan
View
E
N
T
E
R
P
R
I
S
E
A
R
C
H
I
T
E
C
T
U
R
E
-
A
F
R
A
M
E
W
O
R
K
T
M
AspectW
s
O
R
K W
here
Viewpoints

TOGAF’S ENTERPRISE
ARCHITECTURE
TDT4252, Spring 2013
TOGAF
Describes the
processes the
business uses to
meet its goals.
Describes how
specific applications
are designed and
how they interact
with each other.
Describes how the
enterprise datastores
are organised and
accessed.
Describes the hardware
and software
infrastructure that
supports applications
and their interactions.

TOGAF are complements Zachman’s
Framework: Zachman tell you how to
categorise artifacts;
TOGAF provides a process for creating
them.

Business alignment through
• Deeper understandinE
gA
of organizational strategic intent.
• Correct IT investment allocation.
• Realized economies of scale.
• Elimination of redundancies.
• Reduced IT delivery time due to reuse Higher-quality decision making
at all levels An organization that works on the right things at the right
time.
• Selection/identification of correct technologies/functionality required
by the organization.
• An understanding of what we are doing and why and how individual
roles and responsibilities support.
• Creation of an environment for enterprise success
TOGAF

SIA LESSON.pptx

More Related Content

Similar to SIA LESSON.pptx

More from FranzLawrenzDeTorres1

Recently uploaded

SIA LESSON.pptx