Oracle AIM Methodology
Oracle AIM Methodology
Oracle AIM Methodology
An Overview
Presented By:-
Shivmohan Purohit
Agenda
What is Oracle AIM Oracle AIM Structure Oracle AIM Phases Oracle AIM Processes Oracle AIM Preview / Demo Recommendations Questions
Before moving ahead, Lets capture the Answers for some AIM Related Questions !!
Oracle Methodologies
Oracle AIM 3.1 ( Application Implementation Methodology) Oracle EMM ( Easy Migration Methodology) Oracle Unified Method ( OUM)
Oracle AIM provides templates for all the tasks that require them. Oracle AIM is a methodology showing what tasks are required, what order they should be completed in, and what resources are required The methodology is purpose built for Oracle Applications and the detailed deliverables produced are designed with the Oracle Application products in mind.
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.
Establishing scope early in the implementation gives the team a common reference point and an effective way to communicate.
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.
Task ID
CR: Control & Reporting , WM: Work Management, RM: Resource Management QM: Quality Management, CM: Configuration Management
MD020- Analysis and select best approach. Effort Estimation. Review & Approval.
MD050 & MD070 Functional & Technical Design. One customization may include multiple modules
TE020 Technical Analyst prepare unit test script for each module
MD110 Code- Developer create Module Code i.e. procedure, form, alerts etc TE070 Testers perform a unit test
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
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