AIM

AIM is comprised of well-defined processes that can be managed in several ways to

guide you through an application implementation project. AIM provides the tools needed
to effectively and efficiently plan, conduct, and control project steps to successfully
implement new business systems.
Definition
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.
Operations Analysis
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.
Solution Design
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).
Build
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.
Transition
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. During Transition, users perform an
acceptance test of the new system
Production
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.

BUSINESS SYSTEM TESTING

The objective of Business System Testing is to test the quality of all of the elements of
the application system. Business System Testing emphasizes a common planning
approach for all types of testing and advocates the reuse of deliverable components to test
successively larger aspects of the application system.
TE.040 - Develop System Test Script (Core)
In this task, you develop the script to test the integration of application extensions with
Oracle Applications modules. A system test script contains detailed steps which testers
follow to verify the system setup and the integrity of custom application extensions for
supporting business processes.
Deliverable: The deliverable for this task is the System Test Script. It identifies the
system tests to be performed to verify that custom application extensions and standard
Oracle Applications modules adequately support the organizations business processes.
Prerequisites
. Confirmed Business Solutions (BR.090) Use the Confirmed Business Solutions to
establish the business processes that will be tested during Perform System Test (TE.110).
. Conversion Data Mapping (CV.040) The Conversion Data Mapping document records
the detailed mapping of legacy data to the new system. This information may be useful
when completing the data profile component of the System Test Scripts. If Perform
Conversion Data Mapping was not performed, this deliverable will not exist. (See the
task description for CV.040 for more information on when this task should be
performed.)
. Link Test Script (TE.030) Group the Link Test Script into more comprehensive system
test sequences. If Develop Link Test Script was not performed, this deliverable will not
exist. (See the task description for TE.030 task description for more information on when
this task should be performed.)
. Oracle Applications Documentation Library Use information found in the standard
Oracle Applications documentation to gain knowledge about the functionality of the
standard Oracle Applications.
Module Design and Build
The objective of Module Design and Build is to focus on the design and development of
customizations to satisfy functionality gaps identified during Business Requirements
Mapping (BR).
MD.050 - Create Application Extensions Functional Design (Optional)
In this task, you document the functional features, use, and behavior of required
customizations. The Application Extensions Functional Design confirms that you
understand user requirements, and allows users to evaluate and approve the resulting
features that the new modules will provide.
Deliverable: The deliverable for this task is the Application Extensions Functional
Design. It describes each customization in business and user terms. Users and business
analysts are the audience for this deliverable; therefore, it must communicate all the
features provided by the customization in non-technical terms.

Prerequisites
You need the following input for this task:
. Business Procedure Documentation (BP.090)
The Business Procedure Documentation includes the detailed process steps that users will
follow to perform their jobs. You only need the narratives corresponding to the processes
that have functionality gaps. They should already incorporate steps that correspond to
custom modules identified in the Application Extension Definition and Estimates
(MD.020).
. Business Requirements Scenarios (RD.050)
The Business Requirements Scenarios describe requirements in the context of business
flows.
. Mapped Business Requirements (BR.030)
The Mapped Business Requirements provide detailed business requirements for
functionality gaps.
. Application Setup Documents (BR.100)
The Application Setup Documents define setups that may affect the logic and business
rules you define. You also need to know what options will be available for list of values
in custom forms and standard report submission parameters.
. Application Extension Definition and Estimates (MD.020)
The Application Extension Definition and Estimates describes the highlevel approach to
satisfying a business issue and required custom components to solve each functionality
gap. If Define and Estimate Application Extensions was not performed, this deliverable
will not exist. (See the task description for MD.020 for more information on when this
task should be performed.)
. Design Standards (MD.030)
Design Standards define the format and content of design deliverables, plus cosmetic and
interface standards for forms and reports. If Define Design Standards was not performed,
this deliverable will not exist. (See the task description for MD.030 for more information
on when this task should be performed.)
Business Requirements Definition
The objective of Business Requirements Definition is to define the business requirements
of the new applications system. These requirements are used as input to the Future
Process Model (BP.080). The Business Requirements Scenarios (RD.050) list the
necessary steps for executing a business function within a business process; some of the
steps may be application-specific, and some may be manual. To confirm that business
needs are met, you will later map these requirements against application functions and
features in Business Requirements Mapping (BR)
RD.020 - Conduct Current Business Baseline (Core)
In this task, you examine current processes and practices to understand and document the
main activities that keep the organization operating today.
Deliverable: The deliverable for this task is Current Business Baseline. It provides an
analysis of the current business processes, activities, and functions.