Oracle Process (AIM) Engineering

Bahwan Cybertek

Document Name Oracle Process

Document ID Oracle-SEP
Version Number 1.0
Release Date 29\09\04

All rights reserved. No part of this work can be reproduced or used in any form or by any means without the prior
written permission of BCT.

Path Page 1 of 11 Ver #

 Oracle Process (AIM) Engineering

Document Release Log Sheet

Ver. No. Date Prepared Reviewed By Approved Changes made

By By (affected sections)
1.0 29 Oct 04 PMO PMO PMO Initial Version

Path Page 2 of 11 Ver #

 Oracle Process (AIM) Engineering

Table Of Contents

1. Abstract.....................................................................................................................................4
2. References to Models...............................................................................................................4
3. Acronyms..................................................................................................................................4
4. Roles & Responsibilities..........................................................................................................5
4.1 Resources.........................................................................................................................................................5
4.2 Tools.................................................................................................................................................................5
4.3 Training............................................................................................................................................................5
5. Entry Criteria...........................................................................................................................6
6. Tasks..........................................................................................................................................6
6.1 Plan for the process (PM, FC)..........................................................................................................................6
6.2 Operational Analysis phase..............................................................................................................................6
6.3 Solution Design Phase......................................................................................................................................6
6.4 Build Phase.......................................................................................................................................................7
6.5 Transition Phase...............................................................................................................................................8
6.6 Production Phase..............................................................................................................................................8
6.7 Manage & Control Changes.............................................................................................................................8
7. Verification and validation......................................................................................................9
8. Deliverables...............................................................................................................................9
9. Measurement............................................................................................................................9
10. Exit Criteria..............................................................................................................................9
11. Guidelines.................................................................................................................................9
12. Templates................................................................................................................................10
13. Reference to QMS....................................................................................................................10

Path Page 3 of 11 Ver #

 Oracle Process (AIM) Engineering

1. Abstract

This process defines the procedure and necessary resources for ORACLE implementation using
Application Implementation Method (AIM). Aim involves six implementation phases, such as
Definition, Operational Analysis, Solution Design, Build, Transition and Production.

Definition phase being a project management phase has a different process of its own, in this process
other five phases are covered.

Basically implementation involves customization of functionalities present in ORACLE (ERP) as

per client’s requirement. ORACLE implementation involves most of the custom engineering phases.
In case of a requirement requested by client which is not existing functionality in the ORACLE
(ERP), an application extension is required, if necessary custom objects will be built.

This is the general mapping of AIM to CUSTOM development

Sl.No ORACLE CUSTOM Development

1 Definition Project Management
2 Operational Analysis Requirements Phase
3 Solution Design Design Phase
4 Build Coding and Internal Testing
5 Transition User Acceptance Testing
6 Production Post Production Phase

2. References to Models

Oracle Process addresses the following process areas of CMMI Software Staged Representation.
This process represents five Process Areas of CMMI Model and belongs to Software Engineering
Category.

 CMMI model Level 2 Process Area: Requirements Management Process

 CMMI model Level 3 Process Area: Requirements Development Process
 CMMI model Level 3 Process Area: Technical Solution
 CMMI model Level 3 Process Area: Validation

3. Acronyms

Abbreviations Description
PMP (CR010) Project Management Plan
FC Functional Consultant

Path Page 4 of 11 Ver #

 Oracle Process (AIM) Engineering

TC Technical Consultant
DBA Data Base Administrator
PM Project Manager

4. Roles & Responsibilities

Resources

Members Responsibilities
Business Analyst The business analyst will be familiar with the
business area that the system covers and the
terminology and practices and provides knowledge
and guidance regarding application functionality.

Configuration Controller
Data Base Administrator
The database administrator installs and configures
database software for the development environment,
creates the various databases required during the
development life-cycle (for example, the data
dictionary, unit testing, system testing, training) and
maintains database access controls. Additionally, this
project role provides consultation on performance
monitors growth and fragmentation of the
development database, and provides database backup
and recovery.

Functional Consultant A functional consultant is responsible for identifying

the business requirements of the client as functional
requirements and involved in preparing relevant
functional documents
Technical Consultant Responsible for application extensions such as table
creations, coding and unit testing also involved in
preparing relevant technical documents
Project Manager Responsible for the entire project,

Tools

Tools Functionality
CVS (Concurrent Version System) Maintaining versions of all Project Related Artifacts,
Documents and codes.

Training

Training Name Remarks

Path Page 5 of 11 Ver #

 Oracle Process (AIM) Engineering

Application Domain Training Technology, Platform and Domain Training

Requirements Management Tools Training on usage of CVS
Process Training Training on usage of the process

5. Entry Criteria

 Draft Project Management Plan

6. Tasks

Plan for the process (PM)

6.1.1. Refer to the Project Management Plan and its WBS.

Operational Analysis phase

6.2.1. Study and understand the Request for Proposal (RFP)/Contract/Proposal or the
tender document to understand the high level requirements of the client. (PM)
6.2.2. Perform Organizational study of the client and document it in the
Current_Financial_and_Operating_Structure template (RD010). (PM, FC)
6.2.3. Conduct a Technical Review of the RD.010 and update the same as per the review
comments. (FC/PM/FH)
6.2.4. Prepare Process Questionnaire, with specific to each module/domain. (FC)
6.2.5. Schedule necessary meetings with the client and end users for eliciting requirements
and prepare MOM sheets. (PM, FC)
6.2.6. Study current system and requirements of the users in the context of organization’s
Business objectives, business processes, and various roles performed by its users.
(FC)
6.2.7. Identify the current practices of the client in terms of processes (and process events),
and prepare the current process flow diagram and document it in the Current
Business Baseline (RD020). This can be done module wise where required. (FC)
6.2.8. Study and analyze the requirements to define the To-Be processes. (PM, FC)
6.2.9. Compile the system requirements as per the Business Requirements Scenario
(RD050) template and develop the proposed process model. (To-Be Processes) (FC)
6.2.10. Conduct a technical review of the document and update it if required. (Refer to
Technical Review Process) (PM)
6.2.11. Get the client’s sign off on RD050 Document. (PM)
6.2.12. Prepare Bi-Directional Traceability Matrix. (PM)

Solution Design Phase

6.3.1. Study and understand the requirements of the client from the deliverables from the
above phase. (FC)

Path Page 6 of 11 Ver #

 Oracle Process (AIM) Engineering

6.3.2. Draft the requirements of the client as business processes and events and document
it in the Mapped Business Requirements (BR030) template. In case the requirement
can be supported using more than one module choice, use DAR process to select the
module option. (FC)
6.3.3. Develop the solution for the processes and events and document it in the Mapped
Business Requirements (BR030) template as proposed processes. Categorize the
solution to be straight fit, workaround, drop or gap. (FC)
6.3.4. Conduct a technical review of the document and update it if necessary. (PM)
6.3.5. Get the Client’s sign off on the BR030 document. (PM)
6.3.6. Update the Bi-Directional Trace ability matrix. (FC)
6.3.7. Develop solutions for identified gaps and draft the High Level Gap Analysis
(BR010) document. (PM)
6.3.8. Conduct a technical review of the document and update it if necessary. (Refer to
Technical Review Process) (PM)
6.3.9. If necessary perform standard product demo to verify and validate the availability of
the requirements in the standard products.

Implementations involving Application Extensions.

6.3.10. Identify the Functional requirements that affect the Forms and database for closure
of the gaps. (PM)
6.3.11. Decide upon make or buy (including use of re-usable components) analysis for
custom components. (Refer DAR process) (Supplier Agreement Management
Process) (PM)
6.3.12. Use modeling artifacts to understand the requirements for custom development.
(FC)
6.3.13. Decide upon the required form wise changes and inclusions and Document the
required form wise extensions in application extensions functional design (MD050)
document. (PM, FC)
6.3.14. Conduct a technical review of the document and update it if necessary. (Refer to
Technical Review Process) (PM)
6.3.15. Develop Prototypes for custom build forms to validate requirements and conduct a
technical review of the same. (If Required) (PM, FC)
6.3.16. Update the Bi-Directional Trace ability Matrix. (PM)
6.3.17. Identify design alternatives, wherever possible, and justify the decision to choose a
potential choice using DAR process. (Refer to Decision analysis and resolution
process) (PM, TC)
6.3.18. Decide upon database changes and inclusions and document the application
extension technical design document (MD070) and conduct a technical review of
the document. (PM, TC)
6.3.19. Update the Bi-Directional Trace ability Matrix. (PM)
6.3.20. Define the data package for the project based on PMP. (Refer Guidelines) (PM)

Build Phase

6.4.1. Build Actions

Path Page 7 of 11 Ver #

 Oracle Process (AIM) Engineering

6.4.1.1. Study and understand the deliverables of the above phases.

6.4.1.2. Identify the application\Build set up sequence in the application setup
(BR100) document for each module as applicable for the project. Refer to
guideline 11.2. (PM, FC)
6.4.1.3. Perform the application setup by enabling and disabling of required fields as
required for the module. (FC)
6.4.1.4. Build custom and extension as per the functional (MD050) and technical
design (MD 070) documents prepared to address gaps. (TC)
6.4.1.5. Develop or re-use User Manual, Installation Manual for the solution
implemented. (Technical Writer)
6.4.2. Test Actions
6.4.2.1. Prepare the System Integration Test Plan. (TE.120). (TE/FC)
6.4.2.2. Develop the unit level test script and document it in Unit Test Script
(TE020) for custom feature identified in MD070 and conduct a technical
review of the document. (TE, FC, PM)
6.4.2.3. Update the document as per the review comments. (FC)
6.4.2.4. Execute the Unit Test Script and log the defects if any in Defect Log
Template. (TE, FC)
6.4.2.5. Fix the logged defects. (FC, TC)
6.4.2.6. Perform re-testing if necessary. (FC)
6.4.2.7. Develop system integration test script covering the business requirements of
the client and conduct a technical review of the document. (TE050) (TE,
PM)
6.4.2.8. Update the document as per the review comments. (FC)
6.4.2.9. Execute the System Integration Test Script and log the defects if any in
Defect Log Template. (FC)
6.4.2.10. Fix the logged defects. (FC, TC)
6.4.2.11. Perform re-testing if necessary. (FC)

Transition Phase:

6.5.1. Conduct client-training programs as planned in PMP. (Refer to Training Process)

(PM, FC)
6.5.2. Perform the minimum required data conversion for CRP and UAT. (FC)
6.5.3. Conduct Conference Room Piloting as per the PMP. (FC)
6.5.4. Execute User Acceptance Test using TE050 document. (FC)
6.5.5. Prepare User Acceptance Test plan. (FC/TE)
6.5.6. Conduct a technical review of the document and update the same. (PM/FH)
6.5.7. Generate the User Acceptance Test report. (TE130) (FC)
6.5.8. Fix the identified defects during the UAT/CRP. (FC)
6.5.9. Get the client’s sign off on UAT. (PM)
6.5.10. Perform final data migration. (DBA, FC)

Production Phase.

6.6.1. Create Production Instance and deploy the system in the client’s environment. (FC,
PM)

Path Page 8 of 11 Ver #

 Oracle Process (AIM) Engineering

6.6.2. Get the client’s sign off on the Acceptance Certificate. (CR080) (PM)
6.6.3. Follow formalities for live run support if applicable. (PM)

Manage & Control Changes

6.7.1. Change requests have to be raised to support the changes. The CC has to ensure this
request is Raised and tracked. (Refer ‘software configuration management process.’)
6.7.2. Analyze and categorize the change requested as follows:
 New requirement
 Change/Enhancement to an existing requirement
 Deletion of an existing requirement
6.7.3. Perform an Impact Analysis of the change request on schedule, estimates and
resources incase of change in requirements.
6.7.4. The change request has to be approved before it is implemented as per guidelines
mentioned in this document.
6.7.5. Once approved, update all the project assets and necessary documents.
6.7.6. Derive commitment from various stakeholders to reflect these changes
6.7.7. Update the Bi-directional trace ability matrix.

7. Verification and validation

 Technical review of all deliverables

 Client’s Sign off on RD050, BR030, CRP and UAT

8. Deliverables

 Current _Operating and Financial _Structure (RD010)

 Current_ Business_Baseline (RD020)
 Business_Requirement_Scenario (RD050)
 Bussiness_Requirements_Mapping (BR030)
 High_Level_Gap_Analysis (BR010)
 Application_Extension_Functional_Design (MD050)
 Application Extension_Technical_Design (MD070)
 Module specific Application_Set_Up_Document (BR100)
 System_Integration_Test_Plan (TE120)
 Unit_Level_Test_Script (TE020)
 System_Integration_Test_Script (TE050)
 User_Acceptance_Test_Plan
 Test_Report_For_Acceptence_Testing (TE130)
 Defect Logs

Path Page 9 of 11 Ver #

 Oracle Process (AIM) Engineering

9. Measurement

 Requirements stability
 Phase wise Effort and Effort Variance
 Phase wise Schedule and Schedule Variance
 Review efforts
 Defect density and Residual defect density

10. Exit Criteria

 Client’s approval on the system or Contract closure

11. Guidelines

Technical Data Package

 User_Guide
 Technical_Reference_Manual
 System_Management_Guide
 MD050 and MD070 Documents
 Installation_Manuals
 Training

Writing application set up documents.

 The application set up has to be written separately for each module in BR100 document.
Suggested criteria for application set up\build sequence is to follow the sequence suggested
by the product vendor.

12. Tailoring guidelines

S.No Process Tailor-able Range of Consideration Approval

Element attribute Alternatives
1 6.2.6 and 6.2.8 RD.020 and Merging of the Two Client’s Request PMO
RD.050 Documents
2 6.3.13 and MD.050 and Documents can be No Application PMO
6.3.18 MD.070 excluded Extensions

Path Page 10 of 11 Ver #

 Oracle Process (AIM) Engineering

13. Templates

S.No Template Name Location/Link

1 RD010 - Current_Financial_and_Operating_Structure
2 RD020 - Current_Business_Baseline
3 Process Questionnaire
4 RD050 - Business_Requirements_Scenario
5 BR030 - Bussiness_Requirements_Mapping_Form
6 BR010 - High_Level_Analysis
7 BR100 - Application_Set_Up
8 MD050 - Application_Extension_Functional Design
9 MD070 - Application_Extension_Technical_Design
10 TE020 - Unit_Test_Script
11 TE120 - Test_Report_for_Systems_Integration_Test
12 TE050 - Systems_Integration_Test_Script
13 TE130 - Test_Report_for_Acceptance_Test
14 Defect Log Template
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates
BCTPAL/Process Templates/Templates

14. Reference to QMS

 Technical Review Process

 Configuration Management Process
 Decision Analysis and resolution process
 Training Process

Path Page 11 of 11 Ver #