Different Documents Used at Different Levels in Application Implementation Methodology ::

Different Documents Used at Different Levels in Application Implementation Methodology ::

1. Business Process Architecture [BP] –

This Document Addresses ::

• 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.

Application Implementation Methodology

Application Implementation Methodology::

AIM consists of a project management methodology together with the underlying documentation templates that support the tasks you perform within this methodology. This combination of a methodology together with documentation templates makes AIM a powerful tool for assisting implementation participants in running and managing projects successfully.

There are 6 phases in AIM

1. Definition ::
1. Establish the business objectives and related Requirements,
2. Define the Project Plan

2. Operations Analysis :
1. Analyze the operations and identify the fit between Organizational requirements and Standard Applications Functionality

3. Design :
1. Develop detailed design for the optimal Solutions to meet the future business requirements

4. Build : (Implementation)
1. Physical Software system Build and testing

5. Transition:
1. Deploying the Finished solution in to Organization

6. Production Go live

** Each Phase has Number of tasks to be followed.

** There are more than 150 templates, which can be used through out the AIM Process.

There are two types of AIM Documentation template:

-        Project management related (Project plan, Change Orders, Quality control document. Etc.)

-        Oracle Applications Implementation related Docs (RD50, BR100, MD200 etc.)