Sunday, June 29, 2014

Oracle unified method (OUM)

Oracle announced the retirement of AIM and ABF in 2011
•Oracle Application Implementation Method (AIM)
•Oracle AIM for Business Flows (ABF)

Oracle Unified Method(OUM) :
OUM release 6.1 provides support for Application Implementation, Cloud Application Services Implementation, and Software Upgrade projects as well as the complete range of technology projects including Business Intelligence (BI), Enterprise Security, WebCenter, Service-Oriented Architecture (SOA), Application Integration Architecture (AIA), Business Process Management, Enterprise Integration, and Custom Software. Detailed techniques and tool guidance are provided, including a supplemental guide related to Oracle Tutor and UPK.
- OUM to accelerate your development and technology-based efforts;
 - OUM presents an organized and flexible approach.
- Operational framework helps critical project needs and dependencies for development and implementation of project.
- Move efficiently through the project lifecycle to quickly achieve measurable business results.

Components of OUM:
With OUM, you receive the following:
Overview Materials – Provides an overview of OUM’s approach to IT projects, including the
industry standards upon which OUM is based.
Guidelines – Phase, process, task, role, and output guidelines that cover every aspect of an Oracle-based business solution.
Templates – Templates enable fast and easy creation of high quality outputs.
Tailored Work Breakdown Structure – These standards enable an easy start in managing your
project.
OUM supports the complete range of Oracle technology projects including:
 - Oracle Database
- Oracle E-Business Suite
 - Oracle Enterprise 2.0
- Oracle Fusion Middleware
- Oracle Data Warehousing
- Identity Management (IdM)
 - Oracle Transportation Management
- Performance Management
- Business Intelligence and Analytics
 - JD Edwards Enterprise One
- PeopleSoft Enterprise
 - Siebel

Vision for OUM is a single, integrated method to support the entire Oracle economy across the complete suite of Oracle projects. The “best of the best” of Oracle’s portfolio of methods is being coupled with OUM’s industry standards, new techniques, and strong tool support.

There are many exciting changes incorporated in OUM as compare with AIMS:
The primary Benefits of using UOM are:

More Focused Effort - OUM enables projects to clearly define business scope and needs to createenterprise business process models.
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 have contributed their knowledge to OUM.
Higher Quality - OUM subscribes to an iterative approach that incorporates testing and validation throughout the lifecycle.
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. A key focus of each iteration in OUM is to identify and reduce the most significant project risks.



Difference between OUM's approach and AIM for Business Flow's (ABF) conference room pilot approach:
  1. AIM for Business Flows (ABF) utilized iterative conference room pilots (CRPs) to initially map the client's business to the standard Oracle Business Flows and to refine/tailor the business solution to the specific requirements of the project.
  2. However, most of the other elements of the ABF approach were more waterfall than interative. OUM is a true iterative approach. Virtually any and all activities and tasks are performed in an iterative fashion based on an iteration plan developed by the project manager.
  3. While any OUM task or activity can be iterated as necessary to meet project objectives, keep in mind is that you should do only what is necessary to meet the project objectives - nothing more. Make the method serve you - not the other way around.
  4. One significant similarity between OUM's Application Implementation View and ABF is that both methods use the Conference Room Pilot (CRP) technique to refine and iteratively converge on a business solution best suited to the client's requirements. In OUM’s Application Implementation View, Conference Room Pilots are referred to as Functional Prototypes.
  5. It is in name only that JCDM was limited to J2EE. JCDM’s framers designed the method to be technology agnostic. JCDM, and therefore OUM, provides a broadly applicable, yet cohesive collection of activities, tasks, artifacts, roles and responsibilities, and guidelines for technology-based business solutions. In the transition from JCDM, OUM immediately became the single method for technical architecture, technology implementation, and custom software development at Oracle.