AIM METHODOLOGY WITH SDLC

AIM Methodology with SDLC Application implementation methodology is a six phased implementation

methodology:Definition Phase

Operation Analysis Phase

Solution Design Phase

Build Phase

Transition Phase

Production Phase

AIM Methodology with SDLC

Definition Phase:

Plan the project Review the organization Business Objectives Understand the Business Process. Evaluate the feasibility study taking into account project resources like time,

people and budget constraints.

AIM Methodology with SDLC

Commonly Used AIM Documents(Definition Phase)

Bp.040 Develop Current Process model.

RD.010 Identify current financial and operating structure.

TA.020 Identify the Current Technical Architecture.

MD.010 Define Application extension Strategy.

CV.010 Define Data Conversion requirements and Strategy.

TE.010 Define Testing Requirements and Strategy.

AIM Methodology with SDLC

Operational Analysis.

Gaps are identified.

New Proposed solutions are developed.

Proposed Solution for Gaps.

Application Architecture is created and the technical architecture is designed.

AIM Methodology with SDLC

Commonly used AIM Documents (Operational Analysis)

BP.080 Develop future Process Model.

BP.010 Analyze high level Gaps.

BR.050 Conduct Integration Fit Analysis.

TA.040 Define Application Architecture.

.MD.020 Define and Estimate Application Extensions.

PM.010 Define Transition Strategy.

Commonly used AIM Documents (Operational Analysis)

3. Solution Design:

Develop the detailed designs for the new system to meet the future business Requirements.

Create details business process requirements, customizations and module configurations are finalized.

Create Detail Business Procedure documentation.

Building applications extensions to standard features.

Commonly used AIM Documents (Operational Analysis)

BR.100 Define Application Setups BR.110 Define Security Profile. MD.040 Define Build Standards. MD.050 Create Application Extensions Functional Design. MD.060 Design Database Extensions. MD.070 Create Application Extension Technical Design. CV.020 Define Conversion Standards. CV.040 Perform Conversion Data Mapping. CV.060 Design Conversion Programs. CV.070 Prepare Conversion Test Plan. TE.020 Develop Unit Test Script. TE.040 Develop System Test Script.

Build Phase:

Build Phase. Coding. Application Extensions Data Conversions and Interfaces. Testing of all Customizations. Business system testing is performed to validate that the Functionality Meets business requirements. Conducted as a formal Conference room pilot(CRP) Developers produce unit tested.

Commonly used AIM Documents(Build Phase)

MD.120 Create Installation Routines.

DO.060 Publish User Reference Manuals.

PM.030 Develop Transition & Contingent Plan.

Transition Phase

During Transition the Project Team deploys the new system into the organization.

Project Team trains End users.

User Performs the User Acceptance Test(UAT) of the new system.

Transition ends with the cut over to production.

Deliver finished application to the client.

Major activities in this phase are End-user training and support, management of change, and data conversions.

Commonly used AIM Documents(Transition Phase) TE.130 Perform Acceptance Test.

Production Phase

Production begins immediately with the production cutover.

Last Phase of the Implementation and Begin the System Support Cycle.

Performance measurement steps is included in this final phase.

Provide the ongoing support to the organization for the remaining life Of the system.

Commonly used AIM Documents(Production Phase) PM.090 measure System Performance.

AIM Methodology with SDLC

Advantages:- Good for complex and big projects as it reduces the risk of ERP projects.

Disadvantages:- Difficult to scale down the AIM process for small companies- Cost involved with documenting every task of project tasks- Small customers prefer custom formats to AIM formats- AIM formats are not completely required for simple processes.

THANK YOU !!! HAPPY LEARNING ORACLE