Short Notes On Oracle Unified Methodology - OUM


The Oracle Unified Method (OUM) is Oracle’s standards-based method that enables the entire Enterprise Information Technology (IT) lifecycle.
OUM presents an organized, yet flexible, approach.

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

The method has been developed with the intent that the approach for a given project be “built up” from a core set of activities to implement an appropriate level of discipline, rather than “tailored down”.

Key Features of OUM

OUM was developed with the following key features:

 Flexible
 Scalable
 Views

OUM is flexible because it allows to select the strategy, techniques, and tasks appropriate for Specific project.

The OUM 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.

Views provide an initial tailoring of the work plan. Each view page provides access to guidance and a tailored work breakdown structure.

Implementing an OUM Project

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.

Project Managemnt

Business Requirement

Requirement Analysis





Performance Management

Technical Architecture

Data Acquisition & Conversion


Organizational Change Management



Operation and Support


Inception -Develop an approximate vision of the system, make the business case, define the scope, and produce rough estimate for cost and schedule.

Goal of the Inception phase is to gain concurrence among all stakeholders on the lifecycle objectives
For the project.

Relatively it is the Smallest Phase of the project.

The following are typical goals for the Inception phase.

ü     Establish a justification or business case for the project
ü    Establish the project scope and boundary conditions
ü    Outline the use cases and key requirements that will drive the design tradeoffs
ü    Outline one or more candidate architectures
ü    Identify risks
ü    Prepare a preliminary project schedule and cost estimate
ü    The Lifecycle Objective Milestone marks the end of the Inception phase.

Elaboration -The final Elaboration phase deliverable is a plan (including cost and schedule estimates) for the Construction phase

The goal of the Elaboration phase is to develop the detailed requirements, partition the solution, and create any necessary prototypes, and baseline the architecture of the system.

This effort results in a stable basis for the design and implementation effort in the Construction phase.

During the Elaboration phase, the project team’s understanding of the client’s business requirements is verified to reduce development risk.

By the end of the Elaboration phase the system architecture must have stabilized and the executable architecture baseline must demonstrate that the architecture will support the key system functionality and exhibit the right behavior in terms of performance, scalability and cost.

Construction - In this phase the remainder of the system is built on the foundation laid in Elaboration.

The goal of the Construction phase is to take the solution from detailed requirements models, through
Configuration of standard packaged software functionality, development and testing of custom
Components, and integration to a system that is ready for a first release that goes into production.

Team completes the development of the application system, make sure that all components fit together, and prepare the system for the acceptance test and deployment.

When all of the planned iterations have been completed for each partition, the complete application system is tested. The tested system is the end work product of the phase.

Transition – The transition phase can span several iterations and includes testing the system in preparation for release.

The goal of the Transition phase is to install the solution onto the production system, perform acceptance testing, and launch the live application.

Feedback received from an initial release (or initial releases) may result in further refinements to be incorporated over the course of several Transition phase iterations.

 During this phase, the new system is accepted by the organization, the organization is made ready for the new system, and the system is put into production.

Production –

The goal of the Production phase is to operate the newly developed system, assess the success of the
System, and support the users.
This includes: monitoring the system; acting appropriately to enable continued operation; measuring system performance; operating and maintaining supporting systems; responding to help requests, error reports and feature requests by users