Oracle AIM Methodology
Oracle AIM Methodology
- Oracle AIM Methodology provides the Project Management methodology to be followed while implementing Oracle application.
- AIM provides the Basic Outline with which the whole Implementation Process needs to be handled after the Contract to Implement the solution is signed with the Customer
- This has so many steps, documents and Templates and the Implementing Company can decide on which are the steps, documents and Templates to be used
- There is No Hard and Fast rule you have to use all the documents mentioned in AIM Methodology.
AIM projects are conducted in phases. These phases provide quality and control checkpoints to coordinate project activities that have a common goal. During a project phase, your project team will simultaneously be executing tasks from several processes.
During Definition, you plan the project, review the organizations business objectives, understand the business processes, and evaluate the feasibility of meeting those objectives under time, resource, and budget constraints.
During Operations Analysis, the project team develops the Business Requirements Scenarios (RD.050) based on deliverables from Definition that are used to assess the level of fit between the detailed business requirements and standard application functionality.
The purpose of Solution Design is to develop the detailed designs for the new system to meet the future business requirements. During this phase, project team members create detailed Business Procedure Documentation (BP.090).
The coding and testing of all customizations and other custom software, including application extensions, data conversions, and interfaces, is done during the Build phase. Business system testing is performed to validate that the functionality meets business requirements.
During Transition, the project team deploys the new system into the organization. All the elements of the implementation must come together to transition successfully to actual production. The project team trains the users while the technical team configures the Production Environment and converts data.
Production begins immediately with the production cutover. It marks the last phase of the implementation and the beginning of the system support cycle. A series of refinements and performance measurement steps is included in this final phase.
AIM tasks are organized into processes. Each process represents a related set of objectives, resource skill requirements, inputs, and deliverable outputs. A task can belong to only one process. Project team members are usually assigned to a process according to their specialization and background.
Business Process Architecture
Business Process Architecture addresses understanding of the organization’s business processes and aligns them with the business requirements and applications to be implemented.
Business Requirements Definition
Business Requirements Definition defines the business needs that must be met by the implementation project. Document business processes by identifying business events and describing the steps that respond to these events, and then organize processes into scenarios that reflect the business requirements.
Business Requirements Mapping
Business Requirements Mapping compares the future business requirements to standard application software functionality and identifies gaps that must be addressed to fully meet business needs. Mapping teams are assigned groups of future business processes, usually related by business function. Business Requirements Scenarios (RD.050) is then mapped to application functionality.
Application and Technical Architecture
During Application and Technical Architecture, you design an information systems architecture that reflects your business vision.
Module Design and Build
Module Design and Build produces custom application extensions for gaps in functionality identified during Business Requirements Mapping (BR). Custom application extensions include program modules (forms, reports, alerts, and database triggers) that must be designed, built, and tested before they can be incorporated into the new system.
Data Conversion defines the tasks and deliverables required to convert legacy data to the Oracle Applications tables. The converted data may be needed for system testing, training, and acceptance testing, as well as for production cutover.
The amount and level of detail of documentation varies by project. The Documentation Requirements and Strategy (DO.010) defines the documentation requirements for the project and establishes which of the optional Documentation tasks are required. Implementation complexity and documentation requirements are closely correlated.
Business System Testing
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. It supports utilizing common test information, including data profiles, to promote testing coordination and to minimize duplication of test preparation and execution effort.
Performance Testing enables you to define, build, and execute a performance test. It does not assume a particular scope for the performance test. You can use the same process to define a complex test on an entire system, or a simpler test on a component or subset of the system. You may also initiate the process more than once on a project with differing scope and objectives to test the performance of different aspects of your system. The specific goals of each process and the relative timing within a project may be different, but the method you use may be the same.
Adoption and Learning
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 cutover.
Production Migration moves the company, system, and people to the new enterprise system. Following production cutover, it monitors and refines the production system and plans for the future. The Production Migration process encompasses transition to production readiness, production cutover, and post-production support.