EA Outcomes & Value

EA Components

•••

Need for a more effective

and standardized method of

presentation

City districts reorganized according to priorities

Blueprint-based management at time of constructing a new building

EA is a base document/blueprint to help effective and systematic IT system development and management

Apply

architectural

techniques

and approach

to the area of IT

systems

City Design Building Design

City Optimization

Building Optimization

City Development

Building Development

GovernmentIT System

Individual Systems

Overall Architecture Unit System Design

Government IT Optimization

Unit System Optimization

System DevelopmentUnit System

Development

Enterprise is an organizational entity comprised of business functions, processes, and resources to pursue its vision and goals

•Mission and Business

•Business Information Resources

•IT Systems to Support Business Processes

•Technical Components to Build IT Systems

• Enterprise Definition• Enterprise Scope• Architecting Target

• Visualization for easier enterprise recognition by business managers or other employees

• Definition of ‘Architecture’ in Korean language

(1) Architectural technique

(2) Architectural style

(3) Structure, Framework, Organization, Design

• Definition of ‘Architecture’ in English

The art, science and profession of designing buildings,

ships and other large structures and supervising their

construction

• ‘Architecture’ in Wikipedia :

Architecture is both the process and product of

planning, designing and constructing space that reflects

functional, social, and aesthetic considerations.

+=

EA defines business and IT blueprints/architecture in each different view using abstraction

Level Perspective

Components Perspective

Business Application Data Technology

Executive

Director

Manager

System A

Projects

System B

Projects

System C

Projects

Head Office

ZachmanSet of primitive, descriptive artifacts that constitute the knowledge infrastructure of the

Enterprise

U.S. Federal

Government

Integrated framework for evolving or maintaining existing information technology and acquiring

new information technology to achieve the agency's strategic goals and information resources

management goals (ITMRA, 1996)

U.S. CIO Council

A strategic information asset base that defines the business, information necessary to operate

the business, technologies necessary to support business operations, and transitional processes

for implementing new technologies in response to changing needs of the business.

Meta GroupThe holistic expression of the enterprise’s key business, information, application, and technology

strategies and their impact on business functions and processes.

Japan

Government

A method to improve business and IT systems by modeling and managing organization’s entire

business and systems in an unified fashion.

Korea

Government

A framework and method to analyze and optimize organization’s components (business,

application, data, technology, security) based on standardized rules and processes

To view organization’s resource in its entirety, we align enterprise resources (vision, business function/process, data, application, technical infrastructure, etc.) and manage their changes

Vision & Strategy

Organization

Business Functions & Process

Data, App, Technical Architecture

TRM & Standards Profile

In 1987 John Zachman raised the need for a conceptual framework for the integration and linkage

of information systems and named it 'Architecture Framework'

Zachman ‘A Framework for Information systems architecture’ (1987)

EA initially presented a solution to the increasing complexity of information systems

• Simple expression

• Expansion of communication

• Effective acceptance of changed requirements

Began to be used as a tool for systematic management of IT in the 1990s

In the 2000s EA was extended to include the whole enterprise as a focus area

Enterprise Architecture is an organized results of human thought about complicated problem

areas (in this case, the enterprise)

Is EA about business or technology issues?

Business function requirement

changes

Sudden change in management

strategy

IT budget limitations

Business method changes

Management Environment

Changes in IT elements

From C/S to web environment

Even more demanding business support requirements

Strong evaluation requirements

for IT effectiveness

Change in role ofIT department

Increased IT complexity

IT Environment

Based on an established standard EA connects organizational resources and tasks vertically from the vision and strategy level downwards. It also provides a single view of the present and future states of the organization

EA Concept & Necessity

EA Components

• Increasing IT investment and level of IT resources complexity

• IT development optimized in unit business/system’s level

• Conflict of technical specifications /Lack of standards

• Difficulty in assessing current IT resources

• Less system integration, non-reuse of components

Commanding view of agency’s IT plans

and resources

Standard-based

technical acquisition

Easier identificationof redundant IT resources

EA DB

IT Status

Design Standards

Design

Current Target

Maintenance

System

Optimization

Increased ROI

Technical incompatibilities are substantially reduced with EA, an ideally coordinated IT plan

that puts IT standards and guidelines in practice

Agency Information Systems

Connectivity and CompatibilityAbility to link to other components

inside and outside of the organizational environment and to

share any type of information across technology components

Other Organization Information Systems

Information

Linkage

Information

Linkage

Info

rmat

ion

Lin

kage

Information resources are organized by user layers (e.g. planners, owners, designer, and

developer), and are managed in a structured manner with EA Management System.

Planner

Owner

Designer

Developer

Business Data Applications Technology

EA can be used as a communication tool, facilitating effective communication and cooperation

between business and IT departments.

Enterprise Architecture defines:

Promotion of better planning

and decision making

• core business processes• common data elements• crosscutting applications• standard system platforms.

Enterprise Architecture identifies:• common system needs that

span multiple business processes

Enterprise Architecture ensures:• Technology aligned with

business requirements

Common Language Seamless

flow

"Customer""Client""User"

?ITILCOBITISO

A new system can be developed using EA without going through the trouble of researching and

analyzing existing systems since EA maintains the latest information on business processes, system

architectures, and functionality and purpose of key applications

Functionality Purpose

Business Processes System Architecture

Organized Enterprise Architecture Information

Allows organizations to

focus efforts of the most

strategic applications and

investment plans

Streamlining of

components

that are

managed

Strategic Plan

Since organization’s IT resources are managed at hand with EA, a new system can be built using pre-

existing system components with a minimal or no modification. EA entails an inventory of key

application that facilitate reuse in new application or in improving application functionality

Existing Application New Application

Individual functional

components

EA Concept & Necessity

EA Outcomes & Value

EA Governance

Organizational structure, process, and systems

Transition Plan

ReferenceModels

EA InformationEA Framework

TADA AA SABA

EA Repository

EA Team EA Guidelines EA Management System

Current and Target Architecture

Mapping and Utilization

A conceptual framework that defines information needed to attain organization’s EA vision, resources of management interest, and their relationships

By range of EA components

By type of management

interest

[Descriptive Framework]

Zachman Framework

[Procedural Framework]

TOGAF

[Framework in a broad sense]

• EA Reference Model defines a set of standard representations and specifications

• Used for developing EA; and for ensuring consistency, uniformity, and interoperability.

Standards/Principles

Construction

IT SystemsDevelopment

Blueprints City/Buildings

EAIT-empowered enterprise

/Unit systems

Reference Models

Standards/Rules

SRM

DRM

TRM

BRM

PRM

Architecture style and model,Blueprint rules and notations

Example: Interface specifications,Communication specifications

Example: Access to sunlight, Solidity of structures

Benefits of Reference Models

BRM SRM DRM TRMPRM

Reference Models

Business Application Data Technology

Owner

Designer

Planner

Developer

Security

EA

Per

spec

tive

Business Application Data Technology Security

PlannerBV1 Organization Chart

BV2 Business Description

AV1 Application Service

Overview/Definition

DV1 Data Model Overview

/Definition

TV1 Infrastructure

Overview/Definition

SV1 Security Policy

SV2 Security Overview

/Definition

Owner

BV3 Business Function

Relationship/Description

BV4 Business Function

Partition/Description

AV2 Application Service

Relationship/Description

AV3 Application Service

Partition/Description

DV2 Conceptual Data

Relationship

/Description

DV3 Data Exchange

Description

TV2 Infrastructure

/ Description

SV3 Security Relationship

/Description

DesignerBV5 Business Process

DesignAV4 Application Function

DesignDV4 Logical Data ModelDV5 Data Exchange Design

TV3 Infrastructure Design/Specification

TV4 System PerformanceDesign

SV4 Management SecurityDesign

SV5 Physical SecurityDesign

SV6 Technical SecurityDesign

Developer BV6 Business ManualAV5 Application Program

ProfileDV6 Physical Data Model TV5 Product Profile SV7 Security Manual

EA metamodel is a set of artifacts which defines architectural information of interest

View

Architectural information is defined in a form of entities and their relationships

Target ArchitectureCurrent Architecture

Agency’s EA components and their relationships are defined according to the Government EA Metamodel

Security

Business

Data

Application

Technical

Business

Data

Application

Technical

Security

Each agency defines its own EA with a reference toGovernment EA Metamodel.

EA transition plan defines projects and action plans for attaining its target architecture.

EA Governance is a base document to ensure effective and efficient EA management

Includes EA management process, and roles and responsibilities of EA team and related business units.

EAMS(EA Management System) is an electronic depository system that stores EA information, and it gives users convenient access to EA information.

< System manager>

<IT planner>

<IT manager>

ArchitecturalInformation

<IT developer>

Change

Analyze

Create

Report

EA Model Repository

BADA

AATA

use

manage

Model Repository

EA Portal

EA Management System

THANK YOU