Professional Documents
Culture Documents
Oracle AIM Methodology: An Overview
Oracle AIM Methodology: An Overview
An Overview
Presented By:-
Shivmohan Purohit
Agenda
Oracle Methodologies
Oracle AIM 3.1 ( Application Implementation Methodology)
Oracle EMM ( Easy Migration Methodology)
Oracle Unified Method ( OUM)
Definitions
Operation Analysis
Solution Design
Build
Transition
Production
Operations Analysis
Project team develops Business Requirements
Assess the level of fit between the business requirements
and standard application functionality.
Gaps are identified and corresponding solutions developed.
Solutions for gaps evolve into detailed designs during
Solution Design.
Build
coding and testing of all customizations and other custom software
Coding & testing of enhancements, data conversions, and interfaces
Policy and procedure changes relating to business process modifications are
developed.
Business system testing is performed to validate that the developed solutions
meet business requirements.
Production
It marks the last phase of the implementation, and the beginning of the system
support cycle.
The Information Systems (IS) personnel work quickly to stabilise the system and
begin regular maintenance.
Provide the ongoing support to the organisation for the remaining life of the
system.
Compare actual results to project objectives.
Project Management
Business Process architecture
Business Requirement Definition
Business requirement Mapping
Application & technical architecture
Module Design & Build
Data Conversion
Documentation
Business System Testing
Performance Testing
Adoption & Learning
Production migration.
Task
ID
CR: Control & Reporting , WM: Work Management, RM: Resource Management
QM: Quality Management, CM: Configuration Management
Data Conversion
Task Code/ ID: CV
Convert and test all necessary legacy
data for the operation of the new
system
Conversion Approaches
Manual Conversions
Programmatic Conversion with or w/o
tools
Automated Data Entry
Three main aspects of Business Testing Planning, Early Introduction of Testing & CRP
Business System Testing does not address performance testing or the testing of
data conversion programs
Executives
Implementation project teams
Functional managers
Users
Information technology groups
CRP Session I
BP080 Future Business Model
BR010 GAP Analysis
CRP Session II
Some Recommendations
1. Follow the documentation principle like Preparer, reviewer with dates
and approvers with version controls details in all documents.
2. Try to avoid Word, Excel, PPT attachments to the templates.
3. Collect enough details from client to prepare the process flow.
4. Stick on to the Project schedule to submit the documents on time.
5. Ensure to fill the open and closed issues on all updates if any.
6. Follow the uniformity in using templates across all modules.
7. Avoid providing internal intranet URL etc for reference.
8. Follow the Oracle Custom standards while preparing Technical Docs.
9. Documents prepared by one person must be reviewed by another
before submitting to Client.
10.Get a sign off from client and as well as from PM on all docs.
Questions ?
Presented By:-
Shivmohan Purohit