A.I.M. Introduction
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.
The A.I.M. methodology can actually be used for any type IT software implementations however the value of A.I.M is within the documentation template. The software includes the documentation templates, manuals and an html website to manage these templates.
This is a depiction of the A.I.M. methodology life cycle:
Here is a link for download:
Download A.I.M.
Posted in
A.I.M. Methodology |
No Comments »
A.I.M. Document DeliverablesJuly 5, 2007
Business Process Architecture (BP)BP.010 Define Business and Process StrategyBP.020 Catalog and Analyze Potential ChangesBP.030 Determine Data Gathering RequirementsBP.040 Develop Current Process ModelBP.050 Review Leading PracticesBP.060 Develop High-Level Process VisionBP.070 Develop High-Level Process DesignBP.080 Develop Future Process ModelBP.090 Document Business Procedure
Business Requirements Definition (RD)RD.010 Identify Current Financial and Operating StructureRD.020 Conduct Current Business BaselineRD.030 Establish Process and Mapping SummaryRD.040 Gather Business Volumes and MetricsRD.050 Gather Business RequirementsRD.060 Determine Audit and Control RequirementsRD.070 Identify Business Availability RequirementsRD.080 Identify Reporting and Information Access Requirements
Business Requirements MappingBR.010 Analyze High-Level GapsBR.020 Prepare mapping environmentBR.030 Map Business requirementsBR.040 Map Business DataBR.050 Conduct Integration Fit AnalysisBR.060 Create Information ModelBR.070 Create Reporting Fit AnalysisBR.080 Test Business SolutionsBR.090 Confirm Integrated Business SolutionsBR.100 Define Applications SetupBR.110 Define security Profiles
Application and Technical Architecture (TA)TA.010 Define Architecture Requirements and StrategyTA.020 Identify Current Technical ArchitectureTA.030 Develop Preliminary Conceptual ArchitectureTA.040 Define Application ArchitectureTA.050 Define System Availability StrategyTA.060 Define Reporting and Information Access StrategyTA.070 Revise Conceptual ArchitectureTA.080 Define Application Security ArchitectureTA.090 Define Application and Database Server ArchitectureTA.100 Define and Propose Architecture SubsystemsTA.110 Define System Capacity PlanTA.120 Define Platform and Network ArchitectureTA.130 Define Application Deployment PlanTA.140 Assess Performance RisksTA.150 Define System Management Procedures
Module Design and Build (MD)MD.010 Define Application Extension StrategyMD.020 Define and estimate application extensionsMD.030 Define design standardsMD.040 Define Build StandardsMD.050 Create Application extensions functional designMD.060 Design Database extensionsMD.070 Create Application extensions technical designMD.080 Review functional and Technical designsMD.090 Prepare Development environmentMD.100 Create Database extensionsMD.110 Create Application extension modulesMD.120 Create Installation routines
Data Conversion (CV)CV.010 Define data conversion requirements and strategyCV.020 Define Conversion standardsCV.030 Prepare conversion environmentCV.040 Perform conversion data mappingCV.050 Define manual conversion proceduresCV.060 Design conversion programsCV.070 Prepare conversion test plansCV.080 Develop conversion programsCV.090 Perform conversion unit testsCV.100 Perform conversion business objectsCV.110 Perform conversion validation testsCV.120 Install conversion programsCV.130 Convert and verify data
Documentation (DO)DO.010 Define documentation requirements and strategyDO.020 Define Documentation standards and proceduresDO.030 Prepare glossaryDO.040 Prepare documentation environmentDO.050 Produce documentation prototypes and templatesDO.060 Publish user reference manualDO.070 Publish user guideDO.080 Publish technical reference manualDO.090 Publish system management guide
Business System Testing (TE)TE.010 Define testing requirements and strategyTE.020 Develop unit test scriptTE.030 Develop link test scriptTE.040 Develop system test scriptTE.050 Develop systems integration test scriptTE.060 Prepare testing environmentsTE.070 Perform unit testTE.080 Perform link testTE.090 perform installation testTE.100 Prepare key users for testingTE.110 Perform system testTE.120 Perform systems integration testTE.130 Perform Acceptance test
PERFORMACE TESTING(PT)PT.010 – Define Performance Testing StrategyPT.020 – Identify Performance Test ScenariosPT.030 – Identify Performance Test TransactionPT.040 – Create Performance Test ScriptsPT.050 – Design Performance Test Transaction ProgramsPT.060 – Design Performance Test DataPT.070 – Design Test Database Load ProgramsPT.080 – Create Performance Test TransactionProgramsPT.090 – Create Test Database Load ProgramsPT.100 – Construct Performance Test DatabasePT.110 – Prepare Performance Test EnvironmentPT.120 – Execute Performance Test
Adoption and Learning (AP)AP.010 – Define Executive Project StrategyAP.020 – Conduct Initial Project Team OrientationAP.030 – Develop Project Team Learning PlanAP.040 – Prepare Project Team Learning EnvironmentAP.050 – Conduct Project Team Learning EventsAP.060 – Develop Business Unit Managers’Readiness PlanAP.070 – Develop Project Readiness RoadmapAP.080 – Develop and Execute CommunicationCampaignAP.090 – Develop Managers’ Readiness PlanAP.100 – Identify Business Process Impact onOrganizationAP.110 – Align Human Performance SupportSystemsAP.120 – Align Information Technology GroupsAP.130 – Conduct User Learning Needs AnalysisAP.140 – Develop User Learning PlanAP.150 – Develop User LearningwareAP.160 – Prepare User Learning EnvironmentAP.170 – Conduct User Learning EventsAP.180 – Conduct Effectiveness Assessment
Production Migration (PM)PM.010 – Define Transition StrategyPM.020 – Design Production Support InfrastructurePM.030 – Develop Transition and Contingency PlanPM.040 – Prepare Production EnvironmentPM.050 – Set Up ApplicationsPM.060 – Implement Production Support InfrastructurePM.070 – Verify Production ReadinessPM.080 – Begin ProductionPM.090 – Measure System PerformancePM.100 – Maintain SystemPM.110 – Refine Production SystemPM.120 – Decommission Former SystemsPM.130 – Propose Future Business DirectionPM.140 – Propose Future Technical Direction
Posted in
A.I.M. Methodology |
8 Comments »
A.I.M. Methodology SummaryJuly 4, 2007
Application Implementation Method is a proven approach for all the activities required to implement oracle applications.
The scope of the AIM is focused on an enterprise as a whole.
There are eleven processes of implementation.
1. Business Process Architecture [BP]
This phase outlines:
Existing business practices
Catalog change practices
Leading practices
Future practices
2. Business Requirement Definition[RD]
This phase explains about the initial baseline questionnaire and gathering of requirements.
3. Business Requirement Mapping[BR]
In this phase the requirements of business are matched with the standard functionality of the oracle applications.
4. Application and Technical Architecture [TA]
This outlines the infrastructure requirements to implement oracle applications.
5. Build and Module Design [MD]
This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.
6. Data Conversion [CV]
Data Conversion is the process of converting or transferring the data from legacy system to oracle applications.
Ex. Transferring customer records from the legacy to the Customer Master.
7. Documentation [DO]
Documentation prepared per module that includes user guides and implementation manuals.
8. Business System Testing [TE]
A process of validating the setup’s and functionality by QA(functional consultant) to certify status.
9. Performance Testing [PT]
Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc…
10; Adoption and Learning [AP]
This phase explains the removal of the legacy system and oracle application roll out enterprise wide.
11. Production Migration [PM]
The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.
