AIM (Application Implementation Methodology) Documents

Oracle A.I.M. Methodology encompasses a project management methodology with documentation templates that support the life cycle of an implementation. The life cycle methodology and documentation templates allows A.I.M. to be a very useful tool for managing implementation projects successfully. This is a depiction of the A.I.M. methodology life cycle:

Application Implementation Method is a proven approach for all the activities required to implement oracle applications. there are eleven processes of implementation. 1. Business Process Architecture [BP] This phase outlines: !isting "usiness #ractices $atalog change practices %eading practices &uture practices "#.'(' )efine "usiness and #rocess *trategy "#.'+' $atalog and Analy,e #otential $hanges "#.'-' )etermine )ata .athering /equirements "#.'0' )evelop $urrent #rocess Model "#.'1' /eview %eading #ractices "#.'2' )evelop 3igh4%evel #rocess 5ision "#.'6' )evelop 3igh4%evel #rocess )esign "#.'7' )evelop &uture #rocess Model "#.'8' )ocument "usiness #rocedure +. "usiness /equirement )efinition 9/): 4 This phase e!plains about the initial baseline questionnaire and gathering of requirements. /).'(' Identify $urrent &inancial and Operating *tructure /).'+' $onduct $urrent "usiness "aseline /).'-' stablish #rocess and Mapping *ummary /).'0' .ather "usiness 5olumes and Metrics /).'1' .ather "usiness /equirements

/).'2' )etermine Audit and $ontrol /equirements /).'6' Identify "usiness Availability /equirements /).'7' Identify /eporting and Information Access /equirements -. "usiness /equirement Mapping 9"/: ; In this phase the requirements of business are matched with the standard functionality of the oracle applications. "/.'(' Analy,e 3igh4%evel .aps "/.'+' #repare mapping environment "/.'-' Map "usiness requirements "/.'0' Map "usiness )ata "/.'1' $onduct Integration &it Analysis "/.'2' $reate Information Model "/.'6' $reate /eporting &it Analysis "/.'7' Test "usiness *olutions "/.'8' $onfirm Integrated "usiness *olutions "/.('' )efine Applications *etup "/.((' )efine security #rofiles 0. Application and Technical Architecture 9TA: ; This outlines the infrastructure requirements to implement oracle applications. TA.'(' )efine Architecture /equirements and *trategy TA.'+' Identify $urrent Technical Architecture TA.'-' )evelop #reliminary $onceptual Architecture TA.'0' )efine Application Architecture TA.'1' )efine *ystem Availability *trategy TA.'2' )efine /eporting and Information Access *trategy TA.'6' /evise $onceptual Architecture TA.'7' )efine Application *ecurity Architecture TA.'8' )efine Application and )atabase *erver Architecture TA.('' )efine and #ropose Architecture *ubsystems TA.((' )efine *ystem $apacity #lan TA.(+' )efine #latform and <etwor= Architecture TA.(-' )efine Application )eployment #lan TA.(0' Assess #erformance /is=s TA.(1' )efine *ystem Management #rocedures 1. "uild and Module )esign 9M): ; This phase emphasi,es the development of new functionality >customi,ation? required by the client. It mainly details how to design the required forms@ database and reports. M).'(' )efine Application !tension *trategy M).'+' )efine and estimate application e!tensions M).'-' )efine design standards M).'0' )efine "uild *tandards M).'1' $reate Application e!tensions functional design M).'2' )esign )atabase e!tensions M).'6' $reate Application e!tensions technical design M).'7' /eview functional and Technical designs M).'8' #repare )evelopment environment M).('' $reate )atabase e!tensions M).((' $reate Application e!tension modules

M).(+' $reate Installation routines 2. )ata $onversion 9$5: ; )ata $onversion is the process of converting or transferring the data from legacy system to oracle applications. !. Transferring customer records from the legacy to the $ustomer Master. $5.'(' )efine data conversion requirements and strategy $5.'+' )efine $onversion standards $5.'-' #repare conversion environment $5.'0' #erform conversion data mapping $5.'1' )efine manual conversion procedures $5.'2' )esign conversion programs $5.'6' #repare conversion test plans $5.'7' )evelop conversion programs $5.'8' #erform conversion unit tests $5.('' #erform conversion business objects $5.((' #erform conversion validation tests $5.(+' Install conversion programs $5.(-' $onvert and verify data 6. )ocumentation 9)O: ; )ocumentation prepared per module that includes user guides and implementation manuals. )O.'(' )efine documentation requirements and strategy )O.'+' )efine )ocumentation standards and procedures )O.'-' #repare glossary )O.'0' #repare documentation environment )O.'1' #roduce documentation prototypes and templates )O.'2' #ublish user reference manual )O.'6' #ublish user guide )O.'7' #ublish technical reference manual )O.'8' #ublish system management guide 7. "usiness *ystem Testing 9T : ; A process of validating the setupAs and functionality by BA>functional consultant? to certify status. T .'(' )efine testing requirements and strategy T .'+' )evelop unit test script T .'-' )evelop lin= test script T .'0' )evelop system test script T .'1' )evelop systems integration test script T .'2' #repare testing environments T .'6' #erform unit test T .'7' #erform lin= test T .'8' perform installation test T .('' #repare =ey users for testing T .((' #erform system test T .(+' #erform systems integration test T .(-' #erform Acceptance test 8. #erformance Testing 9#T: 4 #erformance testing is the evaluation of transactions saving time@ transaction retrieval times@ wor=flow bac=ground process@ database performance@ etc #T.'(' ; )efine #erformance Testing *trategy #T.'+' ; Identify #erformance Test

*cenarios #T.'-' ; Identify #erformance Test Transaction #T.'0' ; $reate #erformance Test *cripts #T.'1' ; )esign #erformance Test Transaction #rograms #T.'2' ; )esign #erformance Test )ata #T.'6' ; )esign Test )atabase %oad #rograms #T.'7' ; $reate #erformance Test Transaction#rograms #T.'8' ; $reate Test )atabase %oad #rograms #T.('' ; $onstruct #erformance Test )atabase #T.((' ; #repare #erformance Test nvironment #T.(+' ; !ecute #erformance Test ('. Adoption and %earning 9A#: ; This phase e!plains the removal of the legacy system and oracle application roll out enterprise wide. A#.'(' ; )efine !ecutive #roject *trategy A#.'+' ; $onduct Initial #roject Team Orientation A#.'-' ; )evelop #roject Team %earning #lan A#.'0' ; #repare #roject Team %earning nvironment A#.'1' ; $onduct #roject Team %earning vents A#.'2' ; )evelop "usiness Cnit ManagersA/eadiness #lan A#.'6' ; )evelop #roject /eadiness /oadmap A#.'7' ; )evelop and !ecute $ommunication$ampaign A#.'8' ; )evelop ManagersA /eadiness #lan A#.('' ; Identify "usiness #rocess Impact onOrgani,ation A#.((' ; Align 3uman #erformance *upport*ystems A#.(+' ; Align Information Technology .roups A#.(-' ; $onduct Cser %earning <eeds Analysis A#.(0' ; )evelop Cser %earning #lan A#.(1' ; )evelop Cser %earningware A#.(2' ; #repare Cser %earning nvironment A#.(6' ; $onduct Cser %earning vents A#.(7' ; $onduct ffectiveness Assessment ((. #roduction Migration 9#M: ; The process of DdecommissioningE of legacy system and the usage>adoption? of oracle application system. #M.'(' ; )efine Transition *trategy #M.'+' ; )esign #roduction *upport Infrastructure #M.'-' ; )evelop Transition and $ontingency #lan #M.'0' ; #repare #roduction nvironment #M.'1' ; *et Cp Applications #M.'2' ; Implement #roduction *upport Infrastructure #M.'6' ; 5erify #roduction /eadiness #M.'7' ; "egin #roduction #M.'8' ; Measure *ystem #erformance #M.('' ; Maintain *ystem #M.((' ; /efine #roduction *ystem #M.(+' ; )ecommission &ormer *ystems #M.(-' ; #ropose &uture "usiness )irection #M.(0' ; #ropose &uture Technical )irection