Oracle unified method ver1.0


Published on

A handbook to quickly compare Oracle AIM vs OUM method.

Published in: Business, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Oracle unified method ver1.0

  1. 1. Oracle Unified Method Author: Manoj Sharma LinkedIn id: Email id: Reviewed by: Industry Experts
  2. 2. Purpose of the DocumentOracle legacy implementation methodology called Application ImplementationMethod (AIM) is retired by Oracle couple of years back and new method calledOracle Unified Method (OUM) is introduced. But adoption of OUM is very slow.An implementer, Consultant OR Business Analyst worked years on understandingAIM, are assuming their AIM understanding would be wasted and they have to doa new beginning with OUM, hence such peoples are reluctant to adopt OUM. Inthis document we have tried to give simple comparison between AIM and OUM,so that someone already understands AIM, can quickly understand OUM as well.PrerequisitesBasic knowledge of Oracle AIM.AudienceConsultant, Project Managers, Subject Matter Experts (SMEs), Developers &Business Analysts working/planned to work on Oracle Project Implementations.
  3. 3. Introduction to OUMOUM provides an implementation methodology that is rapid, broadly adaptive,and business-focused. OUM includes a comprehensive project and programmanagement framework and materials to support IT implementations of allscales. OUM presents an organized, yet flexible, Project Implementation approach. Itsdefined, operational framework helps anticipate critical project needs anddependencies. With OUM, Implementer can move efficiently through the ITlifecycle to quickly achieve measurable business results.Oracle recommends using OUM instead of legacy implementation method AIM(Application Implementation Method).
  4. 4. AIM vs OUM PhasesAIM has six implementations phases, where OUM has only five phases:OUM AIMInception DefinitionElaboration Operation AnalysisConstruction Solution DesignTransition BuildProduction Transition Production
  5. 5. AIM vs OUM ProcessAIM was having 12 processes, where OUM has 14 processes:AIM (12 Processes) OUM (New Processes) 0. Project Management1. Project Management 1. Business Requirements2. Business Process architecture 2. Requirements Analysis3. Business Requirement Mapping 3. Analysis (Overall Project, not just requirement)4. Business requirement definition 4. Design5. Application & technical architecture 5. Implementation6. Module Design & Build 6. Testing7. Data Conversion 7. Performance Management8. Documentation 8. Technical Architecture9. Business System Testing 9. Data Acquisition and Conversion10. Performance Testing 10. Documentation 11. Organizational Change11. Adoption & Learning Management12. Production migration 12. Training 13. Transition 14. Operations and Support
  6. 6. OUM vs AIM Process SpreadAIM use to have straight process spread between phases where OUM has curvebased spread of a process in different phases. This curve based spread makesOUM much more flexible than AIM. Refer underneath comparison of processspread between phases AIM vs OUM.AIM vs OUM
  7. 7. OUM vs AIM : Phase enter/exit MilestoneAIMAIM does not provide any structured phase entry/exit milestone check points.Most of the Implementers were using customize phase enter & exit process basedon their understandings. On many implementations there weren’t any standardcheck point followed for phase enter and exit.OUMOUM provides an out of box structured phase enter/exit process. In OUM it’scalled Lifecycle Milestones: it occurs at each phase boundaries to assureobjectives of phase are met and ensuring readiness of project to move to nextphase.There are five Milestones defined in OUM. Their initials are LO, LA, IOC, SP andSO. 1. LO = Lifecycle Objective 2. LA = Lifecycle Architecture 3. IOC = Initial Operating Capability 4. SP = System Production 5. SO = Sign-off (Complete project sign off)
  8. 8. OUM vs AIM Template CodesAIM has several template codes, which was difficult to follow. Some of thetemplate codes commonly used in AIM :  TA – Technical Architecture  BP - Business Process  BR – Business Rule  CV – Conversions  MD – Extensions, Interface  TE – Test ExecutionOUM has simplified template codification; it has only three template code  AN –Requirements  DS - Design & Solution  IM – ImplementationThe interesting part is that there no one to one mapping of AIM to OUMtemplates. If someone is looking which template replace AIM- MD070 in OUM,the answer would be the nearest one is DS.140, but you cannot expect DS.140content exactly same like MD070. This is true for most of the templates, as thereis no one to one mapping OR quick comparison available between templates. Werecommend doing a fresh start on these templates rather than comparison ontwo templates.
  9. 9. SummaryOracle announced to retire AIM on 31-Jan-2011. AIM is a legacy method which isbeing replaced by OUM in a couple of iterations. Currently OUM is better inaddressing situations where - next to application implementation - there also is acustom development effort that goes beyond creating extension on standardapplications, like integration leveraging a SOA, IDM to do a real-time integrationbetween various applications (Siebel, PeopleSoft and Oracle Ebiz etc)