Implementation Documents.docx

5
Implementation Documents 1. Business Process Architecture [BP] – This phase outlines: Existing Business Practices Catalog change practices Leading practices Future practices BP.010 Define Business and Process StrategyBP.020 Catalog and Analyze Potential Changes BP.030 Determine Data Gathering Requirements BP.040 Develop Current Process Model BP.050 Review Leading Practices BP.060 Develop High-Level Process Vision BP.070 Develop High-Level Process Design BP.080 Develop Future Process Model BP.090 Document Business Procedure 2. Business Requirement Definition [RD] This phase explains about the initial baseline questionnaire and gathering of requirements. RD.010 Identify Current Financial and Operating Structure RD.020 Conduct Current Business Baseline RD.030 Establish Process and Mapping Summary RD.040 Gather Business Volumes and Metrics RD.050 Gather Business Requirements RD.060 Determine Audit and Control Requirements RD.070 Identify Business Availability Requirements RD.080 Identify Reporting and Information Access Requirements 3. Business Requirement Mapping [BR] In this phase the requirements of business are matched with the standard functionality of the oracle applications. BR.010 Analyze High-Level GapsBR.020 Prepare mapping environment BR.030 Map Business requirements BR.040 Map Business Data BR.050 Conduct Integration Fit Analysis BR.060 Create Information Model BR.070 Create Reporting Fit Analysis

Transcript of Implementation Documents.docx

Implementation Documents1. Business Process Architecture [BP] This phase outlines: Existing Business Practices Catalog change practices Leading practices Future practicesBP.010 Defne Business and Process StrategyBP.020 Catalog and Analyze Potential ChangesBP.030 Determine Data Gathering e!uirementsBP.0"0 De#elo$ Current Process %odelBP.0&0 e#ie' (eading PracticesBP.0)0 De#elo$ *igh+(e#el Process ,isionBP.0-0 De#elo$ *igh+(e#el Process DesignBP.0.0 De#elo$ /uture Process %odelBP.000 Document Business Procedure2. Business e!uirement Defnition 1D2 This phase explains about the initial baseline questionnaire and gathering of requirements.D.010 Identif Current Financial and !perating "tructure D.020 Conduct Current Business Baseline D.030 Establish Process and #apping "ummar D.0"0 $ather Business %olumes and #etrics D.0&0 $ather Business &equirements D.0)0 'etermine (udit and Control &equirements D.0-0 Identif Business ()ailabilit &equirementsD.0.0 Identif &eporting and Information (ccess &equirements3. Business e!uirement %a$$ing 1B2 In this phase the requirements of business are matched *ith the standard functionalit of the oracle applications.B.010 (nal+e ,igh-Le)el Ga$sB.020 Prepare mapping en)ironmentB.030 #ap Business requirementsB.0"0 #ap Business 'ataB.0&0 Conduct Integration Fit (nalsisB.0)0 Create Information #odelB.0-0 Create &eporting Fit (nalsisB&../. Test Business "olutionsB&..0. Confirm Integrated Business "olutionsB&.1.. 'efine (pplications "etupB.110 'efine securit Profiles". A$$lication and 3echnical Architecture 13A2 This outlines the infrastructure requirements to implement oracle applications.3A.010 'efine (rchitecture &equirements and Strategy3A.020 Identif Current Technical (rchitecture3A.030 'e)elop Preliminar Conceptual (rchitecture3A.0"0 'efine (pplication (rchitecture3A.0&0 'efine "stem ()ailabilit "trateg3A.0)0 'efine &eporting and Information (ccess "trateg3A.0-0 &e)ise Conceptual (rchitectureT(../. 'efine (pplication "ecurit (rchitectureT(..0. 'efine (pplication and 'atabase "er)er (rchitectureT(.1.. 'efine and Propose (rchitecture "ubsstemsT(.11. 'efine "stem Capacit PlanT(.12. 'efine Platform and 3et*or4 (rchitectureT(.15. 'efine (pplication 'eploment PlanT(.16. (ssess Performance &is4s3A.1&0 'efine "stem #anagement Procedures&. Build and %odule Design 1%D2 This phase emphasi+es the de)elopment of ne* functionalit 7customi+ation8 required b the client. It mainl details ho* to design the required forms9 database and reports.%D.010 'efine (pplication Extension Strategy%D.020 'efine and estimate application extensions%D.030 'efine design standards%D.0"0 'efine Build "tandards%D.0&0 Create (pplication extensions functional design%D.0)0 'esign 'atabase extensions%D.0-0 Create (pplication extensions technical design#'../. &e)ie* functional and Technical designs#'..0. Prepare 'e)elopment en)ironment#'.1.. Create 'atabase extensions#'.11. Create (pplication extension modules%D.120 Create Installation routines). Data Con#ersion 1C,2 'ata Con)ersion is the process of con)erting or transferring the data from legac sstem to oracle applications. Ex. Transferring customer records from the legac to the Customer #aster.C,.010 'efine data con)ersion requirements and strategyC,.020 'efine Con)ersion standardsC,.030 Prepare con)ersion en)ironmentC,.0"0 Perform con)ersion data mappingC,.0&0 'efine manual con)ersion proceduresC,.0)0 'esign con)ersion programsC,.0-0 Prepare con)ersion test plansC%../. 'e)elop con)ersion programsC%..0. Perform con)ersion unit testsC%.1.. Perform con)ersion business ob:ectsC%.11. Perform con)ersion )alidation testsC%.12. Install con)ersion programsC,.130 Con)ert and )erif data-. Documentation 1D42 'ocumentation prepared per module that includes user guides and implementation manuals.D4.010 'efine documentation requirements and strategyD4.020 'efine 'ocumentation standards and proceduresD4.030 Prepare glossarD4.0"0 Prepare documentation en)ironmentD4.0&0 Produce documentation prototpes and templatesD4.0)0 Publish user reference manualD4.0-0 Publish user guide'!../. Publish technical reference manualD4.000 Publish sstem management guide.. Business System 3esting 1352 ( process of )alidating the setup;s and functionalit b