AIM Methodology Activities & Documents - 02

AIM METHODOLOGY ACTIVITIES AND DOCUMENTS

Short Notes on Oracle Documentation - BR & MD 

   Documentation is a very important process during in oracle apps implementation projects. Oracle as part of the AIM Methodology has provided certain technical language for various kinds of documents at different stages of the project

   Business Requirement Documents, which is mostly done by the Functional Persons of the Implementation Team like Functional Project Leads / Managers. These documents are the Set up Documents, which is 100% based on the BR 120 – Business Requirement Gatherings as provided by the business.

MD Documents:

   Modular Designing Documents, which are is mostly done by the Technical Persons of the Implementation Team like Technical Project Leads / Project Manager. These documents are the Design Documents, which is again based on the BR 120 – Business Requirement Gathering as provided by the business.

   These MD’s are of basically discussed on any customization needs or any special behavior oracle system should work which is not the Standard Oracle Functionality. These MD’s are basically made after you all Functional Design and if there is no work around Oracle System provides for a particular Test Scenario and there is no other way other than to go for the Customization.

   Herewith furnishing below some of the documents involved in every stage of Implementation Cycle:

	Stage	Activity	Documents Used	Process
	1	Analysis	RD120	Requirement Gathering (As Is & To Be Process)
			BR150	Fit GAP analysis (Based on the above document)
	2	Designing	BR100	Setup Document for the Functinal Consultants
			MD200	Setup Document for the Technical Consultants
	3	Build – Demo / Prototype	BR050	Conduct Integration Fit Analysis
	4	Testing	TE060	Develop Systems Integration Test Script
	5	Go Live
	6	Post Production

BR Documents

     Function Activities                                                Documents

1. Definition                                                            CR010
2. Operational Analysis As Is                                  RD10, RD20, RD50
3. Solution Design To Be                                        BR30, BR10
4. Build Set up                                                        BR100
5. Transition Testing                                               TE40, MD50, MD70
6. Production User manual                                     GO LIVE

         Doc. No       -          Description

1. CR010        -          Project Management Plan
2. RD10          -          Identify Current Financial and OperatingStructure
3. RD20          -          Conduct Current Business Baseline
4. RD 50         -          Gather Business Requirement
5. BR030        -          Business Requirement Solutions
6. BR010        -          Gap Analysis
7. MD050       -          Gaps are to be customized and will be build Solution from Functional Design
8. MD070       -          Technical Solutions for Functional Design
9. BR100        -          Define Application Set ups (Set Up / Build)
10. TE020        -          Test - Unit level
11. TE040        -          Test Scripts
12. TE 050       -          Integration (CRP)
13. TE130        -          Bugs Identified by client will be recorded to Generate in MD 50