AIM

AIM Methodology

Oracle Application Implementation Methodology is a proven approach to implement Oracle Applications. AIM defines an organization’s business needs at the beginning of the project and maintains their visibility throughout the implementation.

The phases are

Definition :

The project management team plans the implementation project. The goals are to identify business and system requirements, propose the future business model, and propose the application and information technology architecture

Operations Analysis :

During the Operations Analysis phase, the project team collects management, technical, and end-user business process information and requirements. The project team develops business requirements scenarios used to assess the level of fit between the detailed business requirements and standard application functionality

Solution Design:

The goal of Solution Design is to create the optimal business process solution to meet the future business requirements. During Solution Design, project team members design application configuration options and detailed business procedure documentation

Build :

During the Build phase, the development team codes and tests all custom extensions including application enhancements, conversions, and interfaces. The team creates and executes performance, integration and business system tests

Transition :

During transition, the project team deploys the finished application into the organization. Transition depends on the Build phase for the fully tested business system. The project team fully executes data conversion and uses the developed documentation to train end users and support staff

Production :

It marks the last phase of the implementation and the beginning of system support cycle.

AIM Processes

Business process architecture (BP)
Business process architecture addresses the organization’s business processes and aligns them with the business requirement and applications to be implemented. High level process designs (BP0.070) and future process model (BP0.080) are a part of this.
Business requirements Definition (RD)
Business Requirements Definition defines the business needs that must be met by the implementation project .This is RD 0.020 which is the current business needs.
Business Requirement Mapping (BR)
Business requirement mapping compares the future business requirements to standard oracle application functionality and identifies the gaps. Business requirements scenarios (RD0.050) are then mapped to oracle functionality.
Application and Technical Architecture (TA)
During Application and Technical Architecture, the information systems are designed to reflect the business vision
Module Design and Build (MD)
Module design and build produces custom application extensions for gaps in functionality identified during BR. Custom application extensions include program modules( forms, reports, alerts and database triggers) that must be designed, built and tested before being transitioned in the new system.
Data Conversions (CV)
Data conversion defines the tasks and deliverable to convert legacy data to oracle application base tables.
Documentation (DO)
It defines the documentation requirements for the project and establishes which of the documentation tasks are required.
Business System Testing (TE)
Early in the project life-cycle, Business System Testing focuses on linking test requirements back to business requirements and securing project resources needed for testing. Business System Testing provides a formal integrated approach to Testing
Performance Testing (PT)
Performance Testing enables you to define, build, and execute a performance test. The Performance Testing team defines the scope of testing and relates it to point-in-time snapshots of the transactions expected in the real production system
Adoption and Learning (AP)
Adoption and Learning establishes a measurement system that provides an evaluation of organizational performance to help make sure that expectations are met during implementation and after production cut-over
Production Migration (PM)
Production Migration moves the company, system, and people to the new enterprise system.

MD Documents:

   Modular Designing Documents, which are is mostly done by the Technical Persons of the Implementation Team like Technical Project Leads / Project Manager. These documents are the Design Documents, which is again based on the BR 120 – Business Requirement Gathering as provided by the business.

   These MD’s are of basically discussed on any customization needs or any special behavior oracle system should work which is not the Standard Oracle Functionality. These MD’s are basically made after you all Functional Design and if there is no work around Oracle System provides for a particular Test Scenario and there is no other way other than to go for the Customization.

BR Documents

Function Activities	Documents
Definition	CR010
Operational Analysis	RD10, RD20, RD50
Solution Design	BR30, BR10
Build Set up	BR100
Transition Testing	TE40, MD50, MD70
Production User manual	GO LIVE

Doc. No	Description
CR010	Project Management Plan
RD10	Identify Current Financial and Operating Structure
RD20	Conduct Current Business Baseline
RD 50	Gather Business Requirement
BR030	Business Requirement Solutions
BR010	Gap Analysis
MD050	Gaps are to be customized and will be build Solution from Functional Design
MD070	Technical Solutions for Functional Design
BR100	Define Application Set ups (Set Up / Build)
TE020	Test - Unit level
TE040	Test Scripts
TE 050	Integration (CRP)
TE130	Bugs Identified by client will be recorded to Generate in MD 50