[g3-2nd.presnt] the oracle enterprise architecture framework

1

THE ORACLE ENTERPRISE ARCHITECTURE FRAMEWORK

Presented by Group 3: Hoang Hai Nguyen – Le Vinh DucInstructor: Dr. Nguyen Huy

2

WHY OEAF ?

3

WHY OEAF ?

4

WHAT IS OEAF ?

• Oracle Enterprise Architecture Framework (OEAF)• OEAF is a hybrid EA framework, influenced by

TOGAF, FEA and Gartner.• Providing “just enough” structure, which can be

created “just in time” to meet the business requirements of the organization• help customers align their IT and business

strategies• OEAF may be used standalone or as a

complement a customer’s selected EA methodology.

5

KEY VALUES

• Driven by business strategy .• Standardizes and simplifies the technical

architecture. • Comprises “just enough” modeling for enterprise

solution architecture efforts. • Reuses best practice business models and

reference architectures from industry and commercial vendors.

6

KEY VALUES (CONT.)

• Developed collaboratively with business owners, stakeholders, and skilled architects. • Developed iteratively and matures evolutionarily

for breadth and depth. • Can be enforced. • Technology agnostic but leverages Oracle

expertise and IP.

7

VALUE & BENEFITS

The Oracle Enterprise Application Framework provides significant value to an organization, including: • Continuous alignment of business and IT.• Improved Return on Investment (ROI) through better

execution of the business strategy using IT, and more efficient reuse of IT resources.

• Leveraging technology to create new business strategies.

8

HOW IS OEAF ?

COMPONENTS

PROCESS

9

COMPONENTS

10

COMPONENTS

Business Function

Business Organization

Business Strategy

Business Architecture

11

COMPONENTS

12

COMPONENTS

Application services

Logical components

Application Strategy

Application Architecture

Application processes

Physical components

13

COMPONENTS

14

COMPONENTS

Information Assets

Information Strategy

Information Architecture

15

COMPONENTS

16

COMPONENTS

Technology services

Physical components

Technology Strategy

Technology Architecture

Logical components

17

COMPONENTS

18

COMPONENTS

People

People, process, and Tools

Pro

cess

Tools

19

COMPONENTS

20

COMPONENTS

People

EA Governance

Tech

nolo

gy

Finan

cial

Pro

cesse

s an

d Po

licies

21

COMPONENTS

22

ORACLE ARCHITECTURE DEVELOPMENT PROCESS

23


Architecture Maturity Assessment

Architecture Scope

Business Architecture

Architecture Vision

Architecture Principles

24


Current Application Architecture

Current Technology Architecture bn

Current Business Architecture

Current State Architecture

Current Information Architecture

25


Architecture Principles

Reference Models and Architectures

Business Objectives and Strategies

Input

Current State Analysis

1. The future state architecture artifacts2. A set of architectural gaps3. A set of architectural recommendations and a cost-benefit analysis

Output

Future State Architecture

26


The Strategic Roadmap should produce the following key artifacts:1. A prioritized list of architecture recommendations based on the list from the Future State Architecture phase2. A set of transition architectures that progress the current state to the desired Future State using those architecture recommendations3. A project implementation plan implementing each transition4. A cost analysis of each project implementation and a benefit analysis from each transition architecture

27


• The key purpose of the EA Governance Phase is to help customers develop a governance strategy that has one single mission: ensure a successful transition to the desired Future State Architecture.

• Measure the following dimensions:

• People: defined key performance indicators (KPIs)

• Processes and Policies: The basic objectives of processes and policies should

be alignment, performance measurement, and communication of new

requirements and strategies.

• Financials: measure and ensure progress in terms of business

benefits, such as lowering data storage costs by 50%.

28


• The Business Case phase provides a cost-benefit analysis for the architecture and resulting IT projects in the roadmap. • This phase can be initiated at the beginning of

the OADP lifecycle since having a focus on the business case can drive decision in almost every phase of the process, such as Current State, Future State, and Strategic Roadmap analysis.

30

REFERENCE

• The Oracle Enterprise Architecture Framework, October 2009, Oracle.• Oracle Architecture Development Process:

the Art of Realizing Your Future State Architecture, October 2009, Oracle.