Professional Documents
Culture Documents
Oracle HRMS Functional Document
Oracle HRMS Functional Document
Oracle HRMS Functional Document
By
Skylark Groups
Documents
BR
MD
TE
BP
CF
CV
RD
TA
DO
10
50
20
40
30
70
30
70
50
80
40
80
90 100 110
90 110 120
50 60 70 80 100 110 120 130
Data Migration
Business Requirement Document
Creation of Application and Technical Architecture
Documentation
10 50 60 70 80
20 50 80
10 120 140 150
50 70 90
AIM Phases:
1. Project Definition
This is the phase of project scoping; project planning, resource planning, phase planning, budgeting and
defining constraints and facilitate crucial informed project startup decisions.
This is also the phase to lay down the communication channel, design an effective infrastructure for
delegation and ensure project executive team is in place. In this phase executive team is engaged in
interactive sessions and project team is organized and oriented.
In case, business process change is applicable, then high-level process scenarios are developed.
The main tasks in this phase are:
a. Understanding the current business process and baseline current business process.
b. Develop the Preliminary Conceptual Architecture (TA.030).
c. Develop TO-BE process model, i.e. determine the high-level architectural, technological, and
configuration requirements to support the functional and information needs of the application
system (BP.080).
d. Design improved high-level business processes (BP.070).
2. Operation Analysis
This phase is mainly to drill down to the next levels of details from where it was in the previous phase. In
this phase flow of information, function and process models are captured and detailed with all possible
variants.
This is also the phase to define the detailed function, data, and operational requirements that the new
application system must support and map business requirements to application capabilities and propose
solutions to gaps. This will demonstrate that the proposed business process design is feasible for the
organization.
The technical architecture of hardware and software is refined and a transition strategy is for moving from
the current system to the new application system is drawn.
Performance testing models and scenarios should be developed and proposed.
Skylark Groups
3. Solution Design
The objectives of Solution Design are to produce a design that meets functional requirements within
business, technical, and financial constraints and document the design specifications in a way that
facilitates and supports future maintenance of the system.
In this phase functional and technical designs for custom extensions, interfaces, conversion programs and
database extensions are developed along with security architecture and application set-up and test plans.
Also unit, link, system, and system integration test scripts are developed. Test scripts, test transaction
programs and test data load programs are prepared for taking up system performance testing.
User-learning needs and User Learning Plans are developed in this phase.
4. Build
The objectives of the Build phase is to Develop, test, and accept custom software, including application
extensions, interface programs, data conversion software, custom application subsystems integrated with
Oracle Applications, temporary bridge subsystems which transaction data between legacy and new systems
during multiple
Deployments.
The Application and Database Server Architecture (TA.090), Platform and Network Architecture (TA.120)
and Development Environment (MD.090) are defined prior to start the development work.
In this phase, all documentation deliverables are developed and delivered to customer.
They may be User Reference Manual (DO.060), User Guide (DO.070), Technical Reference Manual (DO.080)
and System Management Guide (DO.090).
The database extension and installation routines are created, tested, and accepted along with performance
testing and reports.
5. Transition
The transition phase is to plan cut-over and actual scheduling of cut-over. This phase calls for preparation
of going live in terms of application, operating environment, user readiness and cut-over plans. This is the
period of end-user training, users learning and adoption plans is executed.
After the application environment is prepared for production instance and all application, database
extensions are in place, the application is loaded with initial configuration set-ups.
Once the initial configuration set-up is ready, the environment is prepared to load application set-ups for
individual modules and master data files are loaded either using loading scripts are using manual process.
The master data is then verified with users and legacy files to assess data accuracy and ensure that masters
are loaded error-free.
The dynamic data files are then extracted from the legacy and verified for their correctness and then
loaded inside application tables using loading scripts or manual process. All these data are cut-off data on a
given date. Generally, the amount of legacy data to be loaded in the new system is as per the agreed
migration strategy. However, the dynamic data needs to be validated to ensure accuracy and its reliability.
By this time all jobs and routines must have been set. Once the migration process is successful, the system
is handed over to production support.
6. Production
This is the period of hand-holding support for the system newly gone live and devote attention to
post-implementation issues like user acceptance
Skylark Groups
Skylark Groups
BR.010 Analyze High Level Gaps (C)
Compare the process as envisioned in the High-Level Process Designs (BP.070) with the
processes supported by Oracle Applications. The differences (gaps) revealed by this analysis need to be
resolved by producing alternatives that balance change in the application against change in processes and
organization.
Output: High Level Gap Analysis
BR.050 Conduct Integration Fit Analysis (O)
Identify the new integration points that you require, based on your conceptual
architecture and the mapping of the new applications onto the existing architecture.
Output: Integration Fit Analysis
BR.090 Confirm Integrated Business Solution (O)
Secure approval for proposed business alternatives.
Output: Confirmed Business Solution
BR.100 Define Application Set-up (C)
Capture the setup decisions and implement them in the appropriate environment.
Output: Application Setup Document
BR.110 Define Security Profile (O)
Gather role and function information and relate them to application security and
responsibilities. As business requirements are established and mapped to application features, you also
begin to define the user security necessary to support the selected alternative in a controlled environment.
Output: Security Profile
Skylark Groups
TA.150 Define System Management Procedures (O)
Design the procedures and specify the tools that the client staff will need to manage the
new system. After you design the procedures in this task, you need to test and refine them later in the
project, prior to incorporating them into the System Management Guide (DO.090) and conducting learning
events for the system support staff. This task focuses on the future production environment and not interim
environments to support the project activities. This includes ongoing production supporting testing and
learning environments.
Output: System Management Procedure
Skylark Groups
TE.070 - Test application extension components on an individual basis to verify that the inputs, outputs, and
processing logic of each application extension component functions without errors. Unit testing is performed
in either the development environment or a testing environment. The goal is to find errors in the smallest
unit of software before you logically link it into larger units. If successful, subsequent link testing should only
reveal errors related to the integration between application extensions.
Output: Unit-Tested Modules
TE.030/080 Develop/Perform Integrated Test Scripts (C)
TE.030 - Develop scripts to test modifications to standard Oracle Applications as well as new
application extensions as part of a business flow. This uncovers any integration problems with other
application extension components that provide or use the data manipulated by the target modules.
Output: Integrated Test Scripts
TE.080 - Test several application extension components together as part of a business flow to uncover any
integration problems with other application extension components that provide or use the data manipulated
by the target component. Link testing is performed in either the development environment or a testing
environment. The scope of each link test typically includes the set of components that support or are
affected by a single application extension. An application extension is defined for each gap identified during
requirements mapping and is described by a functional design and corresponding technical design
document.
Output: Link-Tested Modules
TE.100 Prepare Key Users for Testing (C)
Provide basic training to key users participating in Business System Testing. A test environment is
used to prepare key users for testing.
Output: Prepared Key Users
TE.040/110 Develop/ Perform System Test Scripts (C)
TE.040 - Develop the script to test the integration of application extensions with Oracle
Applications modules. A system test script contains detailed steps which testers follow to verify the system
setup and the integrity of custom application extensions for supporting business processes.
Output: System Test Scripts
TE.110 - Test the integration of all business system flows within the target application system, including all
standard and custom processes and reports. This task is equivalent to a full conference room pilot (CRP)
where the environment simulates the future production environment. The system test is performed in a test
environment.
Output: System Tested Applications
TE.050/120 Develop/ Perform System Integration Test Scripts (O)
TE.050 - Develop the test script that validates the integration between your new application
system and other third-party and legacy systems.
Output: System Integration Test Scripts
TE.120 - Test systems integration with other application systems in a production-like environment. The
systems integration test is performed in a test environment.
Output: Integration Tested System
TE.060 Develop Testing Environments (C)
Install and configure one or more testing environments to support all testing activities.
Output: Testing Environments
Skylark Groups
TE.130 Perform Acceptance Testing (C)
Support users in performing their acceptance test of the new production system. The acceptance
test is performed in the Production Environment. This task also involves scheduling the acceptance test
team, support staff, and user facilities.
Output: Acceptance Test Results
7. Data Migration
Migration
Skylark Groups
transformation, or manipulation required before moving the data to the production tables. Finally,
the interface and validation program performs validation of the data in the interface tables and
updates the data into the Oracle production tables.
Output: Conversion Programs
CV.090/100/110 Perform Conversion Unit/ Business Object / Validation Tests (C)
CV.090 - Test the conversion programs to verify that all programs work without errors and
according to the conversion testing specifications pre-defined in the conversion unit testing
components of the Conversion Test Plans (CV.070).
Output: Unit Tested Conversion Programs
CV.100 - Test the complete conversion of each business object by executing all conversion modules
for the business object in the appropriate sequence and verify that the resulting data is correct.
Output: Business-Object Tested Conversion Programs
CV.110 - Validate that the target applications function correctly with the converted business
objects. Output: Validation Tested Conversion Programs
CV.130 Convert and Verify Data (C)
Convert and migrate the production data from the old system to the new Oracle production
environment. Completion of this task provides data that is ready for production use.
Output: Converted and Verified Data
8. Documentation
Documentation