Вы находитесь на странице: 1из 30

THE ORACLE ENTERPRISE ARCHITECTURE FRAMEWORK

Presented by Group 3: Hoang Hai Nguyen Le Vinh Duc Instructor: Dr. Nguyen Huy

WHY OEAF ?

WHY OEAF ?

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 customers selected EA methodology.

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.

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.

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.

HOW IS OEAF ?
COMPONENTS PROCESS

COMPONENTS

COMPONENTS
Business Architecture

Business Strategy

Business Function

Business Organization

10

COMPONENTS

11

COMPONENTS
Application Architecture
Application Strategy Application services Application processes Logical components Physical components
12

COMPONENTS

13

COMPONENTS
Information Architecture

Information Strategy

Information Assets

14

COMPONENTS

15

COMPONENTS
Technology Architecture
Technology Strategy

Technology services

Logical components

Physical components
16

COMPONENTS

17

COMPONENTS
People, process, and Tools
Process People Tools
18

COMPONENTS

19

Financial

COMPONENTS

EA Governance

Technology Processes and Policies


People

20

COMPONENTS

21

ORACLE ARCHITECTURE DEVELOPMENT PROCESS

22

ORACLE ARCHITECTURE DEVELOPMENT PROCESS


Architecture Vision
Business Architecture Architecture Maturity Assessment Architecture Principles

Architecture Scope
23

ORACLE ARCHITECTURE DEVELOPMENT PROCESS


Current State Architecture
Current Business Architecture Current Application Architecture Current Information Architecture Current Technology Architecture bn
24

ORACLE ARCHITECTURE DEVELOPMENT PROCESS


Future State Architecture

Input
Business Objectives and Strategies
Architecture Principles

Output
1. The future state architecture artifacts 2. A set of architectural gaps 3. A set of architectural recommendations and a cost-benefit analysis

Current State Analysis

Reference Models and Architectures

25

ORACLE ARCHITECTURE DEVELOPMENT PROCESS


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 phase 2. A set of transition architectures that progress the current state to the desired Future State using those architecture recommendations 3. A project implementation plan implementing each transition 4. A cost analysis of each project implementation and a benefit analysis from each transition architecture
26

ORACLE ARCHITECTURE DEVELOPMENT PROCESS


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%.

27

ORACLE ARCHITECTURE DEVELOPMENT PROCESS


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.

28

29

REFERENCE
The Oracle Enterprise Architecture Framework, October 2009, Oracle. Oracle Architecture Development Process: the Art of Realizing Your Future State Architecture, October 2009, Oracle.

30