Oracle® Unified Method (OUM)

Oracle’s Full Lifecycle Method for

Developing and Implementing
Technology-based Business Solutions
An Oracle White Paper
September 2007
 Oracle Unified Method (OUM) White Paper

Executive Overview.......................................................................................... 3
Introduction ....................................................................................................... 3
Standards Based ............................................................................................ 3
Supports Both Agility and Discipline ........................................................ 4
Benefits of OUM............................................................................................... 4
Key Features of OUM...................................................................................... 5
Flexible ........................................................................................................... 5
Scalable ........................................................................................................... 5
Pre-defined Views......................................................................................... 5
Implementing an OUM Project ...................................................................... 6
Project Phases for Control .......................................................................... 7
Inception.................................................................................................... 7
Elaboration................................................................................................ 7
Construction ............................................................................................. 7
Transition .................................................................................................. 7
Production................................................................................................. 7
Project Processes for Continuity ................................................................ 8
Business Requirements............................................................................ 8
Requirements Analysis............................................................................. 8
Analysis ...................................................................................................... 8
Design ........................................................................................................ 9
Implementation ........................................................................................ 9
Testing........................................................................................................ 9
Performance Management .................................................................... 10
Technical Architecture........................................................................... 10
Data Acquisition and Conversion........................................................ 11
Documentation....................................................................................... 11
Adoption and Learning ......................................................................... 11
Transition ................................................................................................ 12
Operations and Support........................................................................ 12
Project Activities Represent the Engagement Lifecycle........................ 13
Managing an OUM Project............................................................................ 13
Developing and Maintaining Enterprise Architecture Activities ............. 15
Components of OUM .................................................................................... 16
Hardware and Software Requirements......................................................... 16
Conclusion........................................................................................................ 16

Oracle Unified Method (OUM) White Paper Page 2

 Oracle Unified Method (OUM) White Paper

EXECUTIVE OVERVIEW
The Oracle® Unified Method (OUM) can help you develop and implement
OUM supports the complete range of
technology-based business solutions with precise development and rapid
Oracle technology projects including:
- Service-Oriented Architecture (SOA) deployment. You can tailor OUM to support your specific project situation. With
- Enterprise Integration its ready-made templates, guidelines, and tailored work breakdown structure, OUM
- Custom Software provides the programmatic tools you need to manage the risks associated with your
- Identity Management (IdM) information technology-based projects.
- Database Security
- Governance, Risk, & Compliance (GRC) Oracle Consulting Services has packaged OUM to accelerate your development and
- Performance Tuning technology-based efforts. OUM presents an organized, yet flexible, approach. Its
defined, operational framework helps anticipate critical project needs and
dependencies throughout your software development and implementation project.
With OUM, you can move efficiently through the development lifecycle to quickly
achieve business results.

INTRODUCTION

Reference: The Unified Software Standards Based

Development Process by Ivar Jackobson,
OUM is standards based. OUM leverages one of the de facto industry standards,
Grady Booch, and James Rumbaugh and
Unified Software Development Process (UP). UP is an iterative and incremental
UML Distilled by Fowler and Scott
approach to developing and implementing software systems. Project managers use
UP’s four-step approach (inception, elaboration, construction, and transition) to
make sure they and their stakeholders develop a shared understanding of what is
needed, choose an appropriate architecture, and transfer the ownership of the end-
product to the stakeholders. OUM tailors and extends the Unified Process by
incorporating field experience and intellectual capital contributed by Oracle
practitioners. OUM recognizes the advantages of an iterative and incremental
approach to development and deployment of information systems. Any of the
tasks within OUM may be iterated. Whether or not to iterate, as well as the
number of iterations, varies. Tasks may be iterated to increase the quality of the
work products to a desired level, to add sufficient level of detail, or to refine and
expand the work products on the basis of user feedback.
OUM also employs the Unified Modeling Language™ (UML®) as the basis for
analyzing software requirements and modeling software architecture and design.
UML is a modeling language defined by the Object Management Group (OMG).

Oracle Unified Method (OUM) White Paper Page 3

 OMG is a consortium that focuses on developing enterprise integration standards
for a wide range of technologies and industries.

References: Agile Manifesto - Supports Both Agility and Discipline

http://www.agilemanifesto.org and
OUM supports both Agility and Discipline. OUM is designed to support a broad
Balancing Agility and Discipline: A Guide
range of project types. As such, it must be scalable and adaptable. At a high level,
for the Perplexed by Barry Boehm and
Richard Turner there are two different camps in today’s method landscape: plan-driven and agile.
The plan-driven camp’s members include Capability Maturity Model® Integration
(CMMI®) and its relatives, the Department of Defense Standards (DoD-STD’s)
including DoD-STD-2167, Cleanroom, and methods like Personal Software
Process (PSP). The Unified Process has its roots in this camp.
The Agile camp, which begins with the Agile Manifesto, has some well known
members including eXtreme Programming (XP), Adaptive Software Develop
(ASD), Scrum, and Crystal. With agile development, stakeholders and developers
meet on a daily basis, and software is delivered and previewed often. Instead of
relying on e-mails and memos, everyone involved accepts that face-to-face
conversations are the most effective method of communication. As part of this
process, stakeholders and developers are willing to discuss what’s working and
what’s not and make adjustment based on that. There is a growing body of
evidence that a properly executed agile approach can markedly increase the
probability of a favorable outcome on many information technology projects.
OUM supports a continuum with “pure agility” and “pure plan based” at its ends.
The appropriate point of balance for a given project varies based on a number of
project risk and scale factors. OUM provides guidance on determining the
minimum set of tasks to be executed, the level of detail targeted in those tasks, and
the frequency and type of end user deliverables.

BENEFITS OF OUM
• More Focused Effort – OUM enables projects to clearly define business
scope and needs to create enterprise business process models. This planning
results in tighter scope control, more accurate business understanding, and a
firm foundation for client acceptance.
• Built-in Flexibility – By combining activities and tasks in different ways,
OUM can be applied to many types of information technology software
development and implementation projects.
• Saves Time – Seasoned information technology practitioners representing
years of experience contributed their knowledge to OUM. OUM allows
project teams to take advantage of this experience by leveraging these leading
practices along with industry standards.
• Higher Quality – OUM subscribes to an iterative approach that
incorporates testing throughout the lifecycle, rather than testing for quality
only at the end of the project.

Oracle Unified Method (OUM) White Paper Page 4

 • More Cost Effective – OUM facilitates improved control of project
expenses by using a flexible work breakdown structure that allows you to
perform only necessary tasks.
• Reduced Project Risk – Implementing an iterative, broadly applicable
method mitigates requirements mismatch and reduces schedule and budget.

KEY FEATURES OF OUM

OUM was developed with the following key features:
• Flexible
• Scalable
• Pre-defined Views

Flexible
OUM is flexible because it allows your organization to select the strategy,
techniques, and tasks appropriate for your project. OUM provides specific
guidelines for tailoring your project plan to fit your situation - from the most basic
development to changes in the underlying technical architecture. By combining
activities and tasks in different ways, OUM can be applied to many types of
information technology software development and implementation projects.

Scalable
OUM was designed with scalability in mind. From the largest, multi-national,
multi-site, multi-entity projects, through to the smallest, limited size, constrained
scope projects—OUM provides the scalability required by each unique project.
Guidelines aid in determining which tasks to include in the project plan. This
greatly reduces the complexity for the project management team in planning the
work effort required.

Pre-defined Views of OUM can be seen by Pre-defined Views

applying Filters.
The method material is organized into pre-defined Views. Views provide an initial
tailoring of the workplan specific to a focus area, discipline, or service offering.
Each view page provides access to guidance and a tailored work breakdown
structure.
OUM 4.4 provides the following pre-defined views:
• Full Method Views
• Full Method
• Full Method - Activities and Tasks

Oracle Unified Method (OUM) White Paper Page 5

 • Focus Area View
• Manage
• Envision
• Implement
• Discipline Views
• Technology Full Lifecycle
• Strategy
• Service Offering Views
• Business to Business Integration Statement of Work
• Middleware Architecture Statement of Work
• Portal Development Statement of Work
• Systems Integration Statement of Work
• Systems and Software Architecture Statement of Work

IMPLEMENTING AN OUM PROJECT

The Implement Focus Area provides a framework to develop and implement
technology-based business solutions. OUM uses project phases and processes to
include quality and control checkpoints and allow coordination of project activities
throughout the project. During a project phase, the project team executes tasks in
several processes.

Oracle Unified Method (OUM) White Paper Page 6

Phase - A chronological grouping of tasks Project Phases for Control
in an approach. Engagements are
OUM includes the following phases.
delivered by phase in order to reduce
project risk. Each phase allows a
Inception
checkpoint against project goals, and
measurement against quality criteria to be The Inception phase is used to kick-off a solution development engagement, review
made. the strategic direction of the client’s business, and confirm, document, and
prioritize the high-level business requirements for the implementation. It is also
the time to begin assembling and integrating the project team, to scope the entire
engagement, and develop the initial project plan.

Elaboration

The goal of the Elaboration phase is to move development of the solution from the
scoping and high-level requirements done during the Inception phase to
development of detailed requirements models, the partitioning of the solution, the
user interface prototype, and the architectural prototype. The Elaboration phase is
used to verify the development team's understanding of the client's business
requirements and to reduce development risk.

Construction

The Construction phase takes the solution from detailed requirements models,
through development and testing of components, and integration to a system that
is ready for a first release that goes into production, often a limited release and
often called a beta release. An iterative process is used to refine the data and detail
the use cases, as well as develop the physical database and components, until they
meet the business requirements, within the constraints of the project timeboxes and
priorities.
When all of the planned iterations have been completed, the complete system is
tested. The tested system is the end deliverable of the phase.

Transition

The Transition phase takes the completed solution from installation onto the
production system through the acceptance test to launch of the live application,
open and ready for business. The goals of the Transition phase are to gain
acceptance of the new system within the user organization, and, if the new system
replaces and old one, to provide a smooth cut-over to the new application. Minor
upgrades may be developed and released after production starts. Also, planning is
performed for the development of any remaining functionality, in a new increment.

Production

The goal of the Production phase is to provide system support, monitor the system,
to determine, develop and implement required upgrades, as well as measure the

Oracle Unified Method (OUM) White Paper Page 7

 system performance, assess the success of the system, and put a plan into place for
future enhancements to the application.

Process - A discipline or sub-project that Project Processes for Continuity

defines a set of tasks related by subject
All OUM tasks are also organized into processes that group related tasks together.
matter, required skills, and common
Project team members are assigned to these groupings according to their
dependencies. A process usually spans
several phases in an approach. specialization and background. OUM includes the following processes.

Business Requirements

In the Business Requirements process, the business requirements for the proposed
system or new enhancements are identified, refined, and prioritized by a tightly
integrated team of empowered ambassador users and experienced analysts. The
process often begins from an existing high-level requirements document and a
scope document. However, it is possible to begin from an agreed on scope and
objectives before requirements have been defined.
The Business Requirements process delivers a set of requirements models and a
prioritized list of requirements as a basis for system development. Both the models
and requirements list are dynamic work products that change as the understanding
of the team develops with the system.
The main work products of this process are the business objectives and goals, the
list of functional requirements, and non-functional requirements.

Requirements Analysis

In the Requirements Analysis process, the requirements captured during the

Business Requirements process are analyzed. They are refined and structured via a
Use Case Model in order to establish a more precise understanding of the
requirements. The Use Case Model is used as the basis for the solution
development. This process helps provide structure and shape to the entire
solution. The Use Case Model is used to document, in detail, the requirements of
the system in a format that both client and the developers of the system can easily
understand.
The main work products of this process are: the use case model, a prototype of the
use interface, and a high-level description of the software architecture.

Analysis

In the Analysis process, the captured requirements are analyzed by refining and
structuring them via a conceptual object model, called the Analysis Model. The
Analysis Model provides a more precise understanding of the requirements and
provides details on the internals of the system. The Analysis Model is described
using the language of the developers as opposed to the requirements obtained in
the Business Requirements and Requirements Analysis processes where the
emphasis is on the functionality of the system expressed in the language of the
client. Thus, it contributes to a sound and stable architecture and facilitates an in-

Oracle Unified Method (OUM) White Paper Page 8

depth understanding of the requirements. Many of the work products produced
during the Analysis process describe the dynamics of the system as opposed to the
static structure. The Analysis Model is also considered the first cut of the Design
Model, since it contains the analysis classes that are further detailed during the
Design process.
The main work product of the Analysis process is the Analysis Model that includes
a set of analysis classes that realize the use cases documented in the Requirements
Analysis process and new software architecture views are added to the software
architecture description initialized during the Requirements Analysis process.

Design

In the Design process, the system is shaped and formed to meet all functional and
non-functional requirements. This form is based on the architecture created and
stabilized during the Analysis process. Thus, the work products produced during
Analysis are an important input into this process.
Design is the focus during the end of Elaboration phase and the beginning of
Construction iterations. Models are created that are used during the
Implementation process. The Design Model can be used to visualize the
implementation of the system.
The main work products of this process are the Design Model which includes an
object model that describes the design realization of the use cases, design classes
that detail the analysis classes outlined in the Analysis Model, the software
architecture description enriched with the new architecture views, and deployment,
and design models.

Implementation

Through a number of steps, mostly iterative, the final application is developed

within the Implementation process. The results from the Design process are used
to implement the system in terms of source code for components, scripts,
executables, etc. Developer testing is also implemented on software components.
Implementation is the main focus of the Construction phase, but it starts in the
Elaboration phase in order to implement the architectural baseline (trial
architecture and prototype). During Transition, it occurs in order to handle any
defects or bugs discovered while testing and releasing the system.
The main work product of this process is the final iteration build that is ready to be
tested. The software architecture description is also enriched with the
implementation view to create the architectural implementation.

Testing

The Testing process is an integrated approach to testing the quality and

conformance of all elements of the new system. Therefore, it is closely related to
the review tasks in the Quality Management process of the Project Management

Oracle Unified Method (OUM) White Paper Page 9

Method (PJM) and to the definition and refinement of requirements in the Business
Requirements process. It addresses mainly functional testing. The Performance
Management process addresses non-functional testing activities. Testing includes
systems integration testing that essentially extends the system testing to test
integration of the new system with the other enterprise systems with which it
communicates.
Testing activities are a shared responsibility of developers, quality assurance
engineers, and ambassador users, working together as an integrated project team.
The Testing process presupposes that there is a highly visible user interface from
which system events can be driven and results validated. The higher proportion of
artifacts that are visible to the ambassador users (for example, user interfaces and
reports) the more they are able to participate in the Testing process.

Performance Management

The objective of the Performance Management process is to proactively define,

construct, and execute an effective approach to managing performance throughout
the project implementation lifecycle in order to ensure that the performance of the
system or system components meet the user requirements and expectations when
the system is implemented. Performance Management is not limited to conducting
a performance test or an isolated tuning exercise, although both of those activities
may be part of the overall Performance Management strategy. The requirements
that drive Performance Management also impact Technical Architecture and the
two processes are closely related.
The Performance Management team defines the scope of testing and relates it to
point-in-time snapshots of the transactions expected in the real production system.
Technical analysts create or set up transaction programs to simulate system
processing within the scope of the test and populate a volume test database against
which to execute the transactions. Once the system and database administrators
have created the test environment, the project team executes the test and the final
results are documented.

Technical Architecture

The goal of the Technical Architecture process is to design an information systems

architecture to support and realize the business vision. The tasks in the Technical
Architecture process identify and document the requirements related to the
establishment and maintenance of the application and technical infrastructure
environment for the project. Processes and procedures required to implement,
monitor and maintain the various environments are established and tested.
The Technical Architecture process is a critical project element, particularly for
systems that have complex requirements. Examples of complex requirements
include systems that are deployed as public facing on the Internet, systems with
high transaction volumes, systems with aggressive performance targets, systems
with high availability requirements, or systems servicing user communities that are

Oracle Unified Method (OUM) White Paper Page 10

distributed geographically over large distances or a variety of time zones. If the
project is implementing using software or technology that is not commonly in use
or has been very recently released, the level of complexity is also more significant
due to increased potential of encountering issues during the implementation
process.

Data Acquisition and Conversion

In the Data Acquisition and Conversion process the data that is required to be
converted is explicitly defined, along with its sources. This data may be needed for
system testing, training, and acceptance testing as well as for production. In some
cases, it is beneficial to convert (some) data at earlier stages to provide as realistic as
possible reviews of the components during the development iterations. On the
other hand, this may be difficult, as the actual Database Design for the new system
is not yet stabilized.
The amount of effort involved with conversion greatly depends on the condition of
the data and the knowledge and complexity of the data structure in legacy systems
and existing applications. For large projects, where large existing systems are
replaced, and most all of the data needs to be converted, consider running this as a
separate project in parallel to the development project. In such situations,
thoroughly analyze the existing systems, map them to the new data model, and
build multiple conversion modules of various complexities. The project team
determines an overall Data Conversion Strategy to meet the Data Conversion
Requirements, including both automated and manual methods. The process
includes designing, coding, and testing any conversion modules that are necessary
as well as the conversion itself. The cleaning of legacy data is visibly identified as a
user and client project staff task so that it can be staffed and scheduled. If data
anomalies exist in the current system(s), or there is an unusual number of
exceptions, recommend data clean-up to the project sponsor.

Documentation

Quality documentation is a key factor in supporting the transition to production,

achieving user acceptance, and maintaining the ongoing business process. For
projects that include Oracle Application products, the Oracle Application manuals
are the foundation of implementation documentation. The Documentation
process allows for development of documentation to augment the standard Oracle
Application products manuals with specific information about the organization's
custom software extensions and specific business procedures. The Oracle
Application manuals are the foundation of implementation documentation.

Adoption and Learning

Adoption and Learning focuses on the use and acceptance of new applications by
all users and the optimization of organizational performance. Inherent in every
technology change is the opportunity to become a stronger, more cohesive
organization; a more efficient performer; a more agile competitor. The benefits are

Oracle Unified Method (OUM) White Paper Page 11

great, but the challenges are many. Organizations who implement new technology
cannot afford to neglect key areas that might ultimately compromise the value of
the technology investment. The goal is for full adoption of the new business
system. The human and organizational aspects of an implementation are often the
decisive factors in its success. Adoption and Learning provides a structured
approach that addresses the human and organizational acceptance and use of new
applications. Adoption and Learning increases the organization’s return on
investment by reducing the risks of implementing applications, increasing the
productivity of all user groups, and assisting the organization to reach peak
performance with the new business system. The more quickly and effectively the
business can adopt new technology, the more productive and competitive is the
organization.
The nature of the OUM approach, often requiring a significant change in the
implementing organization’s business processes, coupled with the rapid
implementation timelines, increases the importance of the change management
aspects of the Adoption and Learning process.

Transition

In the Transition process, we focus on installing the solution (which includes

providing installation procedures) and then going production. It begins early in the
project by defining the specific requirements for cut-over to the new application
system. It then includes tasks to carry out the elements of that strategy such as
developing an Installation Plan, preparing the Production Environment, performing
the cut-over, and decommissioning any legacy systems.

Operations and Support

The goal of the Operations and Support process is to monitor and respond to
system problems, upgrade the application to fix errors and performance problems,
evaluate the system in production and plan enhancements for increased
functionality, improved performance, and tighter security.
The development project does not come to an abrupt end when the team installs
the application system into production. In fact, the months following that
milestone can determine the real success or failure of the project. Internal auditors
have not yet produced the system evaluation, and users most likely still have a few
problems to uncover. There are certain to be requirements with lower priorities
that have not been implemented. The “Could have” requirements and any
remaining “Should have” requirements can now be re-prioritized into an
enhancement plan, from which upgrades can be defined.

Oracle Unified Method (OUM) White Paper Page 12

 Project Activities Represent the Engagement Lifecycle
Activity - Groupings of similar tasks within
a Phase that produce a major project work
An activity is the next level of organization below a phase. Tasks in OUM are
product or milestone. grouped into activities to better represent the engagement lifecycle. For example,
Gather Solution Requirements is one of the activities within the Inception phase.
This activity consists of five tasks related to collecting requirements for the
solution.
Activities allow the project manager to streamline creation and management of the
Work Breakdown Structure (WBS) for an engagement. Because all tasks fall within
an activity, project managers (and other practitioners) are able to manage to the
activity-level rather than the task-level.

MANAGING AN OUM PROJECT

The Manage Focus Area provides a framework in which all types of projects can be
planned, estimated, controlled, and completed in a consistent manner. Oracle's
Project Management Method (PJM) is part of the Manage Focus Area. Consistency
is required in today's business environment, where projects often implement
packages, develop application extensions, and create a data warehouse in order to
satisfy a business need.
Project Management enables the project manager to manage delivery of an agreed
upon level of solution quality while planning for and controlling the scope, cost,
and schedule.
PJM has three phases:
• Project Start Up Phase
• Project Execution and Control Phase
• Project Closure Phase
Integration of the PJM phases with OUM is illustrated below:

Oracle Unified Method (OUM) White Paper Page 13

The PJM Project Start Up phase precedes the Inception phase. Project startup is
where all of the project planning activities take place and where policies,
procedures, and strategies are defined for each of the PJM processes, which govern
the conduct of the engagement.
PJM’s Project Closure phase occurs after the Production phase.
Project Execution and Control is the PJM Phase that runs concurrently with OUM.
The purpose of the Project Execution and Control Phase is to provide adequate
visibility into actual progress so that management can take effective actions when
the project's performance deviates significantly from the project plans. The Project
Execution and Control Phase includes tracking and reviewing the projects
accomplishments and results against documented WBS-dictionary, project
estimates, time schedule, resources plan, and cost budget, and adjusting these plans
based on the actual accomplishment and results.
PJM is organized into 13 processes:
• Bid Transition
• Scope Management
• Financial Management
• Work Management
• Risk Management
• Issue and Problem Management
• Staff Management
• Communication Management
• Quality Management
• Configuration Management
• Infrastructure Management
• Procurement Management
• Organizational Change Management
Collectively, these processes form a comprehensive set of tasks required to manage
technology-based development and implementation projects. Every project
includes most, if not all, of these processes, whether they are the responsibility of a
consulting organization, a client organization, or a third party.

Oracle Unified Method (OUM) White Paper Page 14

DEVELOPING AND MAINTAINING ENTERPRISE ARCHITECTURE
ACTIVITIES
The Envision Focus Area provides a framework for development and maintenance
of enterprise level IT strategy, architecture, and governance. Envision extends
OUM's capabilities beyond delivery and management of software implementation
projects into the realm of IT vision and strategy.
Envision consists of two phases:
• Initiate
• Maintain and Evolve
The Initiate phase is used to perform a set of foundational tasks. These tasks have
a broad range of objectives and applicability. At one end, the Initiate phase can
establish the vision for one or more projects intended to achieve a focused set of
business objectives. On the other end, the Initiate phase can result in establishment
of a broad set of enterprise level IT processes that are continued in the Maintain
and Evolve phase.
The Maintain and Evolve phase forms the foundation for governing and managing
enterprise level business processes and strategies. Envision is not intended to be a
broad treatise on corporate strategic planning. It is focused on information
technology related business architecture and practices.
Envision is organized into six processes:
• Envision Roadmap
• Enterprise Business Analysis
• Adoption and Learning
• Enterprise Architecture
• IT Portfolio Management
• IT Governance
The Envision Focus Area provides an evolving set of best practices around
enterprise level IT strategy, architecture, and governance. It is not likely that all of
Envision's processes and tasks will be executed within any single enterprise, nor is it
likely that Envision will ever contain an exhaustive set of enterprise level processes.
Rather, Envision should serve as a framework that can be scaled to suit the needs
of a particular enterprise.

Oracle Unified Method (OUM) White Paper Page 15

COMPONENTS OF OUM
With OUM, you receive the following:
• Guidelines – Provides an overview of OUM’s approach to software-related
projects, including the industry standards upon which OUM is based.
• Guidelines – Phases, processes, tasks, roles, and template guidelines that
cover every aspect of a technology-based solution.
• Templates – Templates enable fast and easy creation of high quality work
products.
• Tailored Work Breakdown Structure – These standards enable an easy
start in managing your project.

HARDWARE AND SOFTWARE REQUIREMENTS

The following hardware and software are required to run OUM:
• Minimum of 1 GHz processor speed
• 55 MB of disk space
• 520 MB RAM minimum
• Windows 2000, XP, NT 4.0
• Microsoft Office 2000 or later
• Microsoft Project 98 or later (Optional)
• Microsoft Visio 5.0 or later (Optional)
• Adobe Acrobat Reader 6.0 or later
• Microsoft Internet Explorer version 6.0 or later or Netscape 7.0 or later

CONCLUSION
With OUM, Oracle’s full lifecycle method for developing and implementing
technology-based business solutions, you can move efficiently through the
development and implementation lifecycle to quickly achieve business results.
For more information about OUM, contact [email protected].

Oracle Unified Method (OUM) White Paper Page 16

Oracle Unfified Method (OUM) White Paper
September 2007

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Copyright © 2007, Oracle. All rights reserved.

This document is provided for information purposes only and the
contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied
in law, including implied warranties and conditions of merchantability
or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document. This document
may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle
Corporation and/or its affiliates. Other names may be trademarks
of their respective owners.