Oracle AIM ( Oracle application implementation methodology )
Application Implementation Methodology has laid out various stages available in a project.
Stage 1 - Definition of Project Management
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Description
========
The success to any project is a well thought of PROJECT PLAN at the very beginning
considering the requirements and available resources. A Normal Contention of many people is
that Project Plan should normally stage the Start Date and End Date and the Consideration, but
in real time it is actually many more that, the whole project is broken in to different phases and
for each phase a detailed plan is laid out which in turns account for the overall project plan.
Project Plan must be revised whenever there is a Change in the contract or requirement of the
client
Documentation to be Prepared
======================
Project Plan (Finalized or Draft)
Write up about the Client and the Consultant.
Stage 2 - Operational Analysis
~~~~~~~~~~~~~~~~~~~~~~
Description
========
This is the very Critical stage of the Project. One must devote the maximum possible time to this
stage. Any compromise on this stage may prove critical at later stage of the project. In this stage
a Consultant, who is a total stranger to the client so far is going to make an effort to become an
expert in understanding the client business every inch. Only when he masters the
clients business, he will be in a position to think beyond it and provide solutions considering the
impact it can have on overall business. In this stage a consultant must carryout following
activities:
-- Clearly understand the contractual obligations made between the client and the consultant
with respect to the work to be performed.
-- Detailed study on the Client business and Organization Structure
- Capture the current business process as they are following ( Also known as AS IS
documentation)
- Collect the requirements from the client, managers, end users as to what they expect from the
Oracle Product
-- Requirements with respect to Functional Side as well as Technical Side is collected
-- Document the bottlenecks faced with the existing system in place
-- Most important point is that get the document signed from the client
( Note: Normally speaking once a requirement is expressed at this stage , it will be taken care by
the consultant, however in real time, requirements gathering becomes a day to day activity in
many clients place, which is highly unprofessional way of working )
Documentation to be Prepared
======================
RD 10 --> Current Financial and Operating Structure
RD 20 --> Current Business Baseline
RD 50 --> Business Requirements Gathering
Stage 3 - Solution Design
~~~~~~~~~~~~~~~~~~~
Description
========
After making serious understanding and analysis on clients current business practices and future
requirements, consultant must begin the process of providing solutions to each and every aspect.
If an straight forward solution is not possible , think about the possibility of workaround. Enough
analysis has to be one in drafting the new business process of the client which is going to be
followed here after, it is also known as To Be Process. Once the solution is decided on, the same
must be communicated to the client seeking acceptance. when the client is satisfied with the
solution, consultant can put an end to his research work on providing alternate solutions.
Documentation to be Prepared
======================
BP 80 --> Business Process Design ( To be process )
BR 10 --> High Level Gap Analysis
BR 30 --> Business Requirements Mapping
MD 50 --> Application Extension Functional Design
MD 70 --> Application Extension Technical Design
Stage 4 - Building Stage
~~~~~~~~~~~~~~~~~~
Description
========
Only at this stage the work of performing setups and access to the instance begins. Based on the
Solutions and new business process ( To Be) designed at the previous stage, the consultant starts
performing setting up of the Application. In case of a functional requirement, it will be setups
from the front end, in case of technical requirements, SQL scripts, customizations will be
performed. Document all the setups that has been carried out at this stage, since it will be useful
when the production Instance is configured or when there is a system crash or corruption of data
or any hardware failure. After performing all required setups, the system has to be tested for its
readiness to carry out operations
Documentation to be Prepared
======================
BR 100 --> Application Setup
BR110 --> Security Profiles
TE 20 --> Unit Test Script
TE 40 --> System Test Script
TE 50 --> System Integration Test Script
TE 120 --> System Integration Test Plan
Stage 5 - Transition Stage
~~~~~~~~~~~~~~~~~~
Description
========
In this stage, client is exposed to the Applications for the first time to get the comfort level. In
order to make the client to get a feel of the system, user guides, training manuals and training
may be given in understanding how their business is completely taken care by the product. Once
the client is exposed to the Applications, they normally tend to show some interest in learning
new things, which can be used for testing the system. Once the client is satisfied with the
Solutions and the way in which the system performs, he can express his wildlings to accept the
system. In real time, acceptance will be taken up at two levels,
First Level - CRP - Conference Room Piloting - Where the consultant gives a preview of the new
system to the selected members of the client and get their feedback.
Second Level - UAT - User Acceptance Testing - Here the consultant gives detailed
demonstration on the new system to the users ( Super and End ), and get the acceptance from the
users that the new system meet their expectations.
Documentation to be Prepared
======================
TE 130 - User Acceptance Test Report
Stage 6 - Production Stage
~~~~~~~~~~~~~~~~~~
Description
========
Once CRP and UAT is approved, it is the duty of the consultant to replicate the same in a new
environment which will be used solely and exclusively for the Production purposes only. After
making the production server ready with all setups, it is advised to clone the production server to
an development or test server, so that any value addition or future testing can be carried out
separately in future. Once the production server is ready, it is given to the client to begin their
operations, which is termed as GO LIVE . In order to assist the client in adopting to the new
system, consultant will provide them with User Manuals and also a support consultant for a
short period of time if needed.
Once the production server is ready and used, the implementation gets over, and the client
should give it in writing that he is satisfied with the implementation taken place, which is termed
as sign off
Documentation to be Prepared
======================
DO 070 --> User Manuals
Client's sign off on the Acceptance Certificate
Application Implementation Methodology has laid out various stages available in a project.
Stage 1 - Definition of Project Management
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Description
========
The success to any project is a well thought of PROJECT PLAN at the very beginning
considering the requirements and available resources. A Normal Contention of many people is
that Project Plan should normally stage the Start Date and End Date and the Consideration, but
in real time it is actually many more that, the whole project is broken in to different phases and
for each phase a detailed plan is laid out which in turns account for the overall project plan.
Project Plan must be revised whenever there is a Change in the contract or requirement of the
client
Documentation to be Prepared
======================
Project Plan (Finalized or Draft)
Write up about the Client and the Consultant.
Stage 2 - Operational Analysis
~~~~~~~~~~~~~~~~~~~~~~
Description
========
This is the very Critical stage of the Project. One must devote the maximum possible time to this
stage. Any compromise on this stage may prove critical at later stage of the project. In this stage
a Consultant, who is a total stranger to the client so far is going to make an effort to become an
expert in understanding the client business every inch. Only when he masters the
clients business, he will be in a position to think beyond it and provide solutions considering the
impact it can have on overall business. In this stage a consultant must carryout following
activities:
-- Clearly understand the contractual obligations made between the client and the consultant
with respect to the work to be performed.
-- Detailed study on the Client business and Organization Structure
- Capture the current business process as they are following ( Also known as AS IS
documentation)
- Collect the requirements from the client, managers, end users as to what they expect from the
Oracle Product
-- Requirements with respect to Functional Side as well as Technical Side is collected
-- Document the bottlenecks faced with the existing system in place
-- Most important point is that get the document signed from the client
( Note: Normally speaking once a requirement is expressed at this stage , it will be taken care by
the consultant, however in real time, requirements gathering becomes a day to day activity in
many clients place, which is highly unprofessional way of working )
Documentation to be Prepared
======================
RD 10 --> Current Financial and Operating Structure
RD 20 --> Current Business Baseline
RD 50 --> Business Requirements Gathering
Stage 3 - Solution Design
~~~~~~~~~~~~~~~~~~~
Description
========
After making serious understanding and analysis on clients current business practices and future
requirements, consultant must begin the process of providing solutions to each and every aspect.
If an straight forward solution is not possible , think about the possibility of workaround. Enough
analysis has to be one in drafting the new business process of the client which is going to be
followed here after, it is also known as To Be Process. Once the solution is decided on, the same
must be communicated to the client seeking acceptance. when the client is satisfied with the
solution, consultant can put an end to his research work on providing alternate solutions.
Documentation to be Prepared
======================
BP 80 --> Business Process Design ( To be process )
BR 10 --> High Level Gap Analysis
BR 30 --> Business Requirements Mapping
MD 50 --> Application Extension Functional Design
MD 70 --> Application Extension Technical Design
Stage 4 - Building Stage
~~~~~~~~~~~~~~~~~~
Description
========
Only at this stage the work of performing setups and access to the instance begins. Based on the
Solutions and new business process ( To Be) designed at the previous stage, the consultant starts
performing setting up of the Application. In case of a functional requirement, it will be setups
from the front end, in case of technical requirements, SQL scripts, customizations will be
performed. Document all the setups that has been carried out at this stage, since it will be useful
when the production Instance is configured or when there is a system crash or corruption of data
or any hardware failure. After performing all required setups, the system has to be tested for its
readiness to carry out operations
Documentation to be Prepared
======================
BR 100 --> Application Setup
BR110 --> Security Profiles
TE 20 --> Unit Test Script
TE 40 --> System Test Script
TE 50 --> System Integration Test Script
TE 120 --> System Integration Test Plan
Stage 5 - Transition Stage
~~~~~~~~~~~~~~~~~~
Description
========
In this stage, client is exposed to the Applications for the first time to get the comfort level. In
order to make the client to get a feel of the system, user guides, training manuals and training
may be given in understanding how their business is completely taken care by the product. Once
the client is exposed to the Applications, they normally tend to show some interest in learning
new things, which can be used for testing the system. Once the client is satisfied with the
Solutions and the way in which the system performs, he can express his wildlings to accept the
system. In real time, acceptance will be taken up at two levels,
First Level - CRP - Conference Room Piloting - Where the consultant gives a preview of the new
system to the selected members of the client and get their feedback.
Second Level - UAT - User Acceptance Testing - Here the consultant gives detailed
demonstration on the new system to the users ( Super and End ), and get the acceptance from the
users that the new system meet their expectations.
Documentation to be Prepared
======================
TE 130 - User Acceptance Test Report
Stage 6 - Production Stage
~~~~~~~~~~~~~~~~~~
Description
========
Once CRP and UAT is approved, it is the duty of the consultant to replicate the same in a new
environment which will be used solely and exclusively for the Production purposes only. After
making the production server ready with all setups, it is advised to clone the production server to
an development or test server, so that any value addition or future testing can be carried out
separately in future. Once the production server is ready, it is given to the client to begin their
operations, which is termed as GO LIVE . In order to assist the client in adopting to the new
system, consultant will provide them with User Manuals and also a support consultant for a
short period of time if needed.
Once the production server is ready and used, the implementation gets over, and the client
should give it in writing that he is satisfied with the implementation taken place, which is termed
as sign off
Documentation to be Prepared
======================
DO 070 --> User Manuals
Client's sign off on the Acceptance Certificate
