ORACLE UNIFIED METHOD (OUM)



OUM Level 1 - Overview & Awareness


The OUM aka Oracle Unified Method supports the entire Enterprise IT Life cycle, including support for the successful implementation of every Oracle product.

It is a robust, technology agnostic methodology Oracle Methods …

  • Based on industry standards and field experience
  • Highly scalable to support project or program specific requirements
  • Iteratively developed through a continuous, evolutionary process
>>OUM is able to…

Support the complete range of Oracle technology projects including
  • Service-Oriented Architecture (SOA)
  • Enterprise Integration
  • Custom Software
  • Enterprise Performance Management (EPM)
  • Business Intelligence (BI)
  • Enterprise 2.0
  • Enterprise Application Implementation
  • Software Upgrade

>>Module 1: Basics


> OUM is
  1. Standards Based
  2. Iterative and Incremental
  3. Supports Both Agility and Discipline







> OUM Goals:
  1. Best of the best
  2. Single Method Framework
  3. Fusion Technology Foundation
  4. Release Independent
  5. Tight Integration with Sales Methodology and Enterprise Level Processes 







> OUM Benefits
  1. Common language
  2. Reduce confusion
  3. Integrate Oracle's acquisitions
  4. Reduce duplication 




> OUM is:
  1. Product and technology agnostic
  2. Tool and language independent.

> OUM is standards based. OUM aligns with, supports and extends the following popular methodologies: 
  1. Unified Process (UP)
  2. Project Management Institute Project Management Body of Knowledge (PMI PM BOK)
  3. Business Analysis Body of Knowledge (IIBA BABOK)
  4. Unified Modeling Language (UML)
  5. Business Process Modeling Notation ( BPMN)

































>>Module 2: Core Components
     

































OUM Process - 
Typically OUM process defined as "A discipline or sub-project that defines a set of tasks related by subject matter, required skills, and common dependencies". A process usually spans several phases in an approach.

All OUM tasks are also organized into processes that group related tasks together. Project team members are assigned to these groupings according to their specialization and background. OUM includes the following 14 processes




 
  1. BUSINESS REQUIREMENTS [RD] – Objective of the Business Requirements process is to identify, refine, and prioritize the business requirements for the proposed system
  2. REQUIREMENTS ANALYSIS [RA]– Objective of the Requirements Analysis process is to further analyze the requirements identified during the Business Requirements process as the basis for analysis and design.
  3. ANALYSIS [AN]– Objective of the Analysis process is to analyze, refine, and structure the system requirements via the Analysis Model.
  4. DESIGN [DS] – Objective of the Design process is to translate requirements into a system design that meets all functional and supplemental requirements.
  5. IMPLEMENTATION [IM] – Objective of the Implementation process is to develop the final system, through a number of iterative steps.
  6. TESTING [TE]– The Testing process is an integrated approach to testing the quality and conformance of all elements of the new system.
  7. PERFORMANCE MANAGEMENT [PT]– Objective of the Performance Management process is to define, construct, and execute an effective approach to managing performance throughout the project life cycle.
  8. TECHNICAL ARCHITECTURE [TA]– Objective of the Technical Architecture process is to design an information system architecture that realizes the business vision.
  9. DATA ACQUISITION AND CONVERSION [CV]– Objective of the Data Acquisition and Conversion process, is to convert all legacy data necessary for the operation of the new system.
  10. DOCUMENTATION [DO]– Objective of the Documentation process is to develop documentation that augments product manuals with information about custom software and business procedures.
  11. ORGANIZATIONAL CHANGE MANAGEMENT [OCM]– Objective of the Organizational Change Management process is to identify the human and organizational challenges of the project in order to mitigate risk.
  12. TRAINING [TR]– Objective of the Training process is to adequately train the project team to begin the project and train the users to run the new system.
  13. TRANSITION [TS]– Objective of the Transition process is to install the system and go production.
  14. OPERATIONS AND SUPPORT [PS]– Objective of the Operations and Support process is to monitor and respond to system problems to fix errors and performance problems and plan enhancements.


Phases in OUM:

(A) Phase I: Inception: As the first phase of the project life cycle, the major goal of this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. Kick off's, review, high-level business requirements along with initial project plan is being targeted in this phase only.
(B) Phase II: Elaboration: This is the second phases in the project life cycle, where the major focus would be to develop the detailed requirements models, partition the solution, develop functional prototyping, and baseline the architecture of the system.
(C) Phase III: Construction: As the third phases in the project life cycle, Construction focuses on design, implementation, and testing of functions to develop a complete system.
(D) Phase IV: Transitions: This typically consists of installation onto the production system through the UAT and launch of the live application, open and ready for business.
(E) Phase V: 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 ensure continued operation; measuring system performance; operating and maintaining supporting systems; responding to help requests, error reports and feature requests by users; and managing the applicable change control process so that defects and new features are prioritized and assigned to future releases.













There are 5 Lifecycle Milestones defined in OUM. Their acronyms are LO, LA, IOC, SP and SO.
  1. LO = Lifecycle Objective
  2. LA = Lifecycle Architecture
  3. IOC = Initial Operating Capability
  4. SP = System Production
  5. SO = Sign-off

>> Module 3: OUM Structure

>>OUM FOCUS AREAS

These 3 Focus Areas provide a framework for enterprise level planning, project and program management and implementation

  1. Envision Focus Area deals with development and maintenance of enterprise level IT strategy, architecture, and governance. This also assists in the transition from enterprise-level planning and strategy activities to the identification and initiation of specific projects.
  2. Manage Focus Area provides a framework in which all types of projects can be planned, estimated, controlled, and completed in a consistent manner.
  3. Implement Focus Area This focus Area provides a framework to develop and implement Oracle-based business solutions.











>> Module 4: OUM Principles



> Iterative and Incremental
OUM, like the Unified Process (UP) from which it has been derived, employs an iterative and incremental approach to implementing software systems.
In OUM, the terms iteration and increment are defined in a way that is consistent with these concepts. An increment is the difference between the release of one iteration and the release of the next iteration. An iteration is a distinct set of activities conducted according to a devoted.














>>AIM vs OUM

 AIM the legacy methodology of software development and project management, is similar to OUM, but below are the key differences in documentation phase wise:



















  • Note:- The certification exam for OUM is 1Z0-568 (Click the link to know more).


    Comments

    Post a Comment

    Popular posts from this blog

    IoT under the magnifying glass

    Image
    IoT as you may have already heard and read the term refers to the connection of devices (other than typical fare such as computers and smartphones) to the Internet. Cars, kitchen appliances, and even heart monitors can all be connected through the IoT. And as the Internet of Things grows in the next few years, more devices will join that list. Let's just dig a bit deeper how is it going to change and shape our future... IoT represents an architectural shift IoT is changing the computer hardware model that we’ve had for the past 30 or 40 years. Consider all the different phases of hardware models that have existed; green screen, to mini-computer, to PC, to cloud and mobile. The computer architecture has been consistent; Client and Server.  What's changed over the years are the clients. For IoT, however, there is actually a third hardware layer which breaks the traditional client-server model. Developers and architects are used to building software systems acros
    Read more

    Linux 'terminal' is actually not a terminal

          Linux 'terminal' is actually not a terminal.! The abundantly used 'Terminal' in Linux/Unix is actually not a terminal. The modern day 'Terminal' is actually a pseudo terminal, or an emulator to be precise, where you can execute your commands. A terminal, historically, was a device connected to a computing system over a serial connector. The modern systems have emulators with a GUI. The actual definitions are as below, they are interconnected, but different, terms: 1. Terminal: A special kernel-provided device that handles textual input/output and supports the backbone of job control. It works with the keyboard and display drivers to read keystrokes and write to the screen.   2. Terminal window: A GUI window with nothing but a text terminal inside it. Usually synonymous with a terminal emulator.   3. Console: The control panel where you sit and do stuff. Very general term and means very different things to very different kinds of
    Read more