Application Implementation Methodology

What is AIM
Definition:
Application Implementation Methodology (AIM), is defined as a set of organized and flexible process steps that guides a project team through the Application Implementation process, which includes:
1.Phases 2.Processes 3.Tasks

4.Key Deliverables

Why AIM
AIM itself is part of Oracle MethodSM, Oracles integrated approach to solution delivery.
AIM is provided to assist in expediting and standardizing

all of the tasks executed and deliverables produced in an Application Implementation project. plan, conduct, and control project steps to successfully implement new business systems. application implementations, providing information on processes and tasks. managed in several ways that application implementation project. guides

AIM provides the tools needed to effectively and efficiently

AIM is a complete guide for planning and executing

detailed

AIM is comprised of well-defined processes that can be

through

the

Why AIM
Aim includes a description of tasks and deliverables, in addition to:
Guidelines Approach Roles

on prerequisites

and techniques

and responsibilities

Deliverable
Component Audience Distribution Usage Completion Deliverable

components
descriptions

criteria template information

Phases and Process

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, the project team will simultaneously be executing tasks from several processes.
The figure below illustrates the phases

AIM Phases and Processes

Definition Phase
Determines the high-level business and information system requirements necessary to meet a set of defined business objectives. The Definition phase results in a clear definition of a projects functional scope.

Definition Phase
Main Processes: 1. Business Requirement Definition
1. Identify current financial and structure. 2. Conduct current business baseline. operating

1. RD.020: which is the main deliverable of this phase.

2. 3. 4. 5.

Data Conversion
1. CV.010

Documentation Business System Testing Adoption and Learning

Operations Analysis Phase

The goal of the Operations Analysis phase is to determine the high-level business and information system requirements necessary to meet a set of defined business objectives. The Operations Analysis phase results in a clear definition of a projects functional scope.

Operations Analysis Phase

Main Processes: 1. Business Process Architecture
1. Develop future process model.

2.

Business Requirement Definition

1. 2. 3. 4.

1. BP.080: which is the main deliverable of this phase.

Gather business volumes and metrics. Gather business requirements. Determine audit and control requirements. Identify reporting and information access requirements.

Operations Analysis Phase

Main Processes: 3. Business Requirements Mapping
1. 2. 3. 4.
4.

Analyze high-level gaps. Prepare mapping environment. Map business requirements. Map business data.

Adoption and Learning

Solution Design Phase

The goal of Solution Design is to use the requirements created during Operations Analysis and finalize the system design and proposed applications setups.

Solution Design Phase

Main Processes: 1. Business Requirements Mapping
1. Define application setup. 1. BR.100 2. Design security profile. 1. BR.110

2.

Business System Testing

1. Develop unit test script. 2. Develop link test script. 3. Develop system test script. 1. TE.040

Solution Design Phase

Main Processes: 3. Adoption and Learning
1. 2. 3. Identify business process impact on organization. Conduct user learning needs analysis. Develop user learning plan.

Build Phase
The goal of Build phase is to formulate the detailed requirements for the computer application system and to propose a solution.

Build Phase
Main Processes: 1. Business System Testing
1. 2. 3. 4. 5.
2.

Prepare testing environment. Perform unit test. Perform link test. Perform system test. Perform systems integration test. Develop the special database load, transaction programs and construct the test database. Develop the user learning ware (AP.150) and prepare the user learning environment(AP.160).

Performance Testing
1.

3.

Adoption and learning

1.

Transition Phase
The goal of the Transition phase is to install the new system, prepare client personnel, establish the system administration function, and then cut over to the new system.

Transition Phase
Main Processes: 1. Business System Testing
2.

Adoption and Learning

1. Performance acceptance test. 1. Conduct user learning events. 1. Prepare production environment. 2. Setup applications. 3. Verify production readiness. 1. PM.070 4. Begin production.

3.

Production Migration

Production Phase
The goal of Production is to monitor and confirm that the application is performing adequately and to plan for future functional enhancements.

Production Phase
Main Processes: 1. Adoption and Learning
1.
2.

Conduct effectiveness assessment. Measure system performance. Maintain system.

Production Migration
1. 2.