OracleUnifiedMethod(OUM)

PostedonMay4th,2011bySanjitAnand|

PrintThisPost| EmailThisPost

HaveyoutriedOracleappsHubinipad/iphone/smartPhone?Don'twait.try
ittoday
SinceretirementforOraclelegacymethods,therewaslotofqueriesonOUMvsAIM,thereforethispostwill
helpreadertoknowmoreaboutnewmethod.
TheOUMakaOracleUnifiedMethodsupportstheentireEnterpriseITLifecycle,includingsupportforthe
successfulimplementationofeveryOracleproduct.
Itisarobust,technologyagnosticmethodologyOracleMethods
Basedonindustrystandardsandfieldexperience
Highlyscalabletosupportprojectorprogramspecificrequirements
Iterativelydevelopedthroughacontinuous,evolutionaryprocess
OUMPrincipal
Thisisbasedoutoffivemainprinciples
1. Business:Focusonthebusinessandassurestakeholderacceptanceanddeliveryofthedevelopments
efforts.
2. Architecture:Definearchitecturebeforeresourcesarecommittedfordevelopmentandimplementation.
3. Adaptability:Encouragesadaptabilityforscalabledeliveryacrosssmallandlargeprojectspossessing
disparateresourcesandskilllevels.
4. Implementation:Providesrapidimplementationtechniquestoensurebusinesssolutionsinshorttime
frames
5. Standards:LeveragetheUnifiedModelingLanguageandtheUnifiedSoftwareDevelopmentProcess
OUMisableto
SupportthecompleterangeofOracletechnologyprojectsincluding
ServiceOrientedArchitecture(SOA)
EnterpriseIntegration
CustomSoftware
EnterprisePerformanceManagement(EPM)
BusinessIntelligence(BI)
Enterprise2.0
EnterpriseApplicationImplementation
SoftwareUpgrade
CurrentlyOracleConsultingusingthismethods,toolssupportacompleterangeoftechnologyengagements.
InSummary...OUMstructure
isacomprehensivesetofmethodmaterialsthatisapplicabletoanytypeofinformationtechnology
project.
isaplanbasedmethodthatincludesoverviewmaterialonvariousapproachesandstandards.
Itincludesbaseguidelinesforfocusareas,views,phases,activities,processesandtasks,aswellaswork

productdescriptions.
OUMbasicallyhavefocusareasandthereunderlinephasesandprocesses,insummary
OUMFOCUSAREAS
These3FocusAreasprovideaframeworksforenterpriselevelplanning,projectandprogrammanagementand
implementing.
1. EnvisionFocusAreadealswithdevelopmentandmaintenanceofenterpriselevelITstrategy,
architecture,andgovernance.Thisalsoassistsinthetransitionfromenterpriselevelplanningand
strategyactivitiestotheidentificationandinitiationofspecificprojects.
2. ManageFocusAreaprovidesaframeworkinwhichalltypesofprojectscanbeplanned,estimated,
controlled,andcompletedinaconsistentmanner.
3. ImplementFocusAreaThisfocusAreaprovidesaframeworktodevelopandimplementOraclebased
businesssolutions.
NextlettakeaquickoverviewforImplementFocusareawhichgotreplacementofoldmethodslikeAIM
Foundation,AIMforBusinessFlows,Compass,ResultsRoadmap,etc.
UnderstandingOUM'sImplementFocus
Thisfocusareatypicallybasedoutofmilestonebasedapproach.TypicalMilestoneare:
Lifecycleobjectivemilestone
Lifecyclearchitecturemilestone
Initialoperationcapabilitymilestone
Systeminproductionmilestone
Signoffmilestone
Asmentionearlierthiscomprisesof5phasesand14processes,detailsasfollows:
OUMProjectPhases
TheWorkflowswithinanOUMprojectarecategorizedintofivephases:Inception,Elaboration,Construction,
Transition,andProduction.Thesephasesaredescribedbelow:
(A)PhaseI:Inception:Asthefirstphasesintheprojectlifecycle.Majorgoalofthisphaseisto
achieveconcurrenceamongallstakeholdersonthelifecycleobjectivesfortheproject.Kickoff's,
review,highlevelbusinessrequirementsalongwithinitialprojectplanisbeingtargetedinthis
phaseonly.
(B)PhaseII:Elaboration:Thisisthesecondphasesintheprojectlifecycle,wheremajorfocus
wouldbetodevelopthedetailedrequirementsmodels,partitionthesolution,developfunctional
prototyping,andbaselinethearchitectureofthesystem.
(C)PhaseIII:Construction:Asthethirdphasesintheprojectlifecycle,Constructionfocuseson
design,implementation,andtestingoffunctionstodevelopacompletesystem.
(D)PhaseIV:Transition:Thistypicallyconsistfrominstallationontotheproductionsystem
throughtheUATandlaunchoftheliveapplication,openandreadyforbusiness.
(E)PhaseV:Production:ThegoaloftheProductionphaseistooperatethenewlydeveloped
system,assessthesuccessofthesystem,andsupporttheusers.Thisincludes:monitoringthe
systemactingappropriatelytoensurecontinuedoperationmeasuringsystemperformance

operatingandmaintainingsupportingsystemsrespondingtohelprequests,errorreportsand
featurerequestsbyusersandmanagingtheapplicablechangecontrolprocesssothatdefectsand
newfeaturesareprioritizedandassignedtofuturereleases.
OUMProcessTypicallyOUMprocessdefinedas"Adisciplineorsubprojectthatdefinesasetoftasks
relatedbysubjectmatter,requiredskills,andcommondependencies".Aprocessusuallyspansseveralphases
inanapproach.
AllOUMtasksarealsoorganizedintoprocessesthatgrouprelatedtaskstogether.Projectteammembersare
assignedtothesegroupingsaccordingtotheirspecializationandbackground.OUMincludesthefollowing14
processes

1. BUSINESSREQUIREMENTS[RD]ObjectiveoftheBusinessRequirementsprocessistoidentify,
refine,andprioritizethebusinessrequirementsfortheproposedsystem
2. REQUIREMENTSANALYSIS[RA]ObjectiveoftheRequirementsAnalysisprocessistofurther
analyzetherequirementsidentifiedduringtheBusinessRequirementsprocessasthebasisforanalysis
anddesign.
3. ANALYSIS[AN]ObjectiveoftheAnalysisprocessistoanalyze,refine,andstructurethesystem
requirementsviatheAnalysisModel.
4. DESIGN[DS]ObjectiveoftheDesignprocessistotranslaterequirementsintoasystemdesignthat
meetsallfunctionalandsupplementalrequirements.
5. IMPLEMENTATION[IM]ObjectiveoftheImplementationprocessistodevelopthefinalsystem,
throughanumberofiterativesteps.
6. TESTING[TE]TheTestingprocessisanintegratedapproachtotestingthequalityandconformance
ofallelementsofthenewsystem.
7. PERFORMANCEMANAGEMENT[PT]ObjectiveofthePerformanceManagementprocessisto

define,construct,andexecuteaneffectiveapproachtomanagingperformancethroughouttheprojectlife
cycle.
8. TECHNICALARCHITECTURE[TA]ObjectiveoftheTechnicalArchitectureprocessistodesign
aninformationsystemarchitecturethatrealizesthebusinessvision.
9. DATAACQUISITIONANDCONVERSION[CV]ObjectiveoftheDataAcquisitionand
Conversionprocessistoconvertalllegacydatanecessaryfortheoperationofthenewsystem.
10. DOCUMENTATION[DO]ObjectiveoftheDocumentationprocessistodevelopdocumentationthat
augmentsproductmanualswithinformationaboutcustomsoftwareandbusinessprocedures.
11. ORGANIZATIONALCHANGEMANAGEMENT[OCM]ObjectiveoftheOrganizationalChange
Managementprocessistoidentifythehumanandorganizationalchallengesoftheprojectinorderto
mitigaterisk.
12. TRAINING[TR]ObjectiveoftheTrainingprocessistoadequatelytraintheprojectteamtobeginthe
projectandtraintheuserstorunthenewsystem.
13. TRANSITION[TS]ObjectiveoftheTransitionprocessistoinstallthesystemandgoproduction.
14. OPERATIONSANDSUPPORT[PS]ObjectiveoftheOperationsandSupportprocessistomonitor
andrespondtosystemproblemstofixerrorsandperformanceproblemsandplanenhancements.
Believewiththismethodcompaniesgetsimplifiedprojectmanagement,improvedplanning,reducedrisk
whichmakethemmanageprojectwithintimewithinBudget.NextpostwillmorethedetailsforotherFocus
area.Keepwatchingthisspace.
RelatedPosts
1. OraclesApplicationImplementationMethodology(AIM):PartII
2. WhatisOraclesApplicationImplementationMethodology(AIM)
3. OracleEBusinessSuiteSizing
4. RetirementofOracleAIM&AIMforBusinessFlows
5. AbitonOraclesbusinessflow
PostedinMethodology/Process|NoComments

EmailThisPost| PrintThisPost

HaveyoutriedOracleappsHubinipad/iphone/smartPhone?Don'twait.try
ittoday
LeaveaComment
Name
Mail(willnotbepublished)
Website

Pleasenote:Commentmoderationisenabledandmaydelayyourcomment.Thereisnoneedtoresubmityourcomment.

SubmitComment

AllcontentpresentonthiswebsiteispropertyofOracleappsHub.comandsubjecttointernationalcopyright
laws.
20062011CopyrightOracleAppsEpicenter.AllRightsreserved.