Oracle Business Intelligence and Data Warehousing Practice Notes and Knowledge Repository

  • About Me

    Hello Friends,

    This is Santosh Kumar Gidadmani, a Business Intelligence and Data Warehouse Enthusiast passionate about blogging articles in the BI, Data warehousing, space. This is my attempt to share my experience and knowledge on Oracle BI & Data Warehousing Subjects.

  • OBIEE 11g Certified Implementation Specialist

  • Oracle Partner Network Certified Specialist

  • Visit My Profiles

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 73 other followers

  • Blog Hits Since Nov 2010

    • 364,321 Hits
  • Live Traffic

  • Visitors Country

    Since-Mar'12Free counters!

Archive for the ‘Oracle Unified Method (OUM)’ Category

Oracle Unified Method (OUM) – Part 2

Posted by Santosh Kumar Gidadmani on July 8, 2011

The Implementation focus area provides a framework to develop and implement Oracle based business solutions.
OUM uses project phases and processes to include quality and control checkpoints and allow coordination of project activities throughout the project.

OUM Supports the following Oracle Technologies
Oracle Business Intelligence – Applications
Oracle Business Intelligence – Technology
Oracle Data Warehousing
Oracle Database
Oracle E-Business Suite
Oracle Enterprise 2.0
Oracle Fusion Middleware
Oracle Service-Oriented Architecture (SOA)
Oracle Transportation Management
Oracle JD Edwards EnterpriseOne
Oracle PeopleSoft Enterprise
Oracle Siebel

OUM Project phases and processes

Project Phases:

The inception phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. It is important phase to understand the scope, effort, high level requirements and risk invovled in the project. It is used to kick start the project with strategic direction of the business.

This phase involves detailing down the business requirements, create solutions, create prototypes, baselines 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.

This phase involves taking details from the solution design documents and developing and testing the components, and integration to a system that is ready for a first release that goes into production. Unit testing is performed to check all components and integration is fine.

The goal of the Transition phase is to install the solution onto the production system, perform acceptance testing, and launch the live application. A new system is set up for the production release.

The purpose of this phase is to operate the newly developed system, testing users for performance, monitoring the system and managing the applicable change control process so that defects and new features are prioritized and assigned to future releases.

Project Processes

Business Requirements
Identify and prioritize the business requirements, understand the scope of the implementation. The main work products from this process are the business objectives and goals and the list of functional and non-functional requirements.

Requirements Analysis
The functional and supplemental requirements are analyzed further into a Use Case Model. The Use Case Model is built to ensure IT and Business understands the requirements.

The captured requirements are analyzed and mapped onto the chosen product set. Analysis is also done to capture the conceptual object model.

This process involves designing the solution architecture to meet the functional requirements. Design process is the end of Elaboration phase and the beginning of Construction phase.

This process is development phase of components, writing codes and testing the systems for integration. This process is done on iterative method.

The Testing process is an integrated approach to testing the quality and conformance of all elements of the new system.
Testing activities are a shared responsibility of developers, quality assurance engineers, and end users, working together as an integrated project team.

Performance Management
This process involves proactively define, construct, and execute an effective approach to managing performance throughout the project implementation lifecycle.

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

Data Acquisition and Conversion
The objective of the Data Acquisition and Conversion process is to create the components necessary to extract, transform, transport, and load the source data to support the information needs of the new system.

The documentation process includes development of documentation including technical and functional requirement documents.

Organizational Change Management
This process starts at the strategic level and then identifies challenges of the implementations in order to design the systems that allow lowering the risk. Identifying the change requirements from the beginning of the project would help organization to manage it effectively.

This process involves training the end users to start the project and to ensure they are adequately trained to take on the tasks of running the new application system.

The goal of the Transition process is to install the solution, which includes providing installation procedures, and then take it into production.

Operations and Support
This process monitors and responds to system problems, upgrade the applications, performance problems, evaluate the system in production, and plan enhancements for increased functionality, improved performance, and tighter security.

OUM Components
You receive the following with OUM kit
Overview Materials
Tailored Work Breakdown Structure

For more information about OUM, visit or join Oracle Unified Method group on LinkedIn.

– Santosh

Posted in OBIEE 10g, OBIEE 11g, Oracle Unified Method (OUM) | Leave a Comment »

Oracle Unified Method (OUM) – Part 1

Posted by Santosh Kumar Gidadmani on July 7, 2011

After retirement of Oracle Application Implementation Method (AIM), Oracle has introduced new methodology called Oracle Unified Method (OUM) – Oracle’s Full Lifecycle Method for Deploying Oracle-Based Business Solutions.

OUM is designed to support a broad range of project types. As such, it must be flexible and scalable. The appropriate point of balance for a given project will vary based on a number of project risk and scale factors. Oracle’s Global Methods team has packaged OUM to accelerate IT projects.

Benefits of OUM
1. More Focused Effort: OUM enables projects to clearly define business scope and needs to create enterprise business process models.

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

3. Saves Time: Seasoned information technology practitioners representing years of experience have contributed their knowledge to OUM. Project teams to take advantage of this experience by leveraging these leading practices along with industry standards.

4. Higher Quality: OUM subscribes to an iterative approach that incorporates testing and validation throughout the lifecycle, rather than testing for quality only at the end of the project.

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

6. Reduced Project Risk: Implementing an iterative, broadly applicable method mitigates requirements mismatch.

7. Industry Standards: OUM leverages one of the de facto industry standards, Unified Software Development Process (UP).

8. Incorporates Iterative method: OUM recognizes the advantages of an iterative and incremental approach to development and deployment of information systems.

Key Features of OUM

1. Flexible
OUM is flexible because it allows your organization to select the strategy, techniques, and tasks appropriate for your project.

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

The method material is organized into views. Views provide an initial tailoring of the workplan. Each view page provides access to guidance and a tailored work breakdown structure.

I will provide more details about OUM Phases and processes in my Part 2 Post.
Source Reference:

– Santosh

Posted in OBIEE 10g, OBIEE 11g, Oracle Unified Method (OUM) | Leave a Comment »

%d bloggers like this: