Scribd
Upload
114 views

Project Xplanation

The document outlines the requirements and responsibilities for two types of work received from an onsite coordinator: issues, which involve estimating tasks, writing approach documents, coding, testing, and creating root cause analysis documents; and project development, which follows a process from business requirements and design documents to coding, testing, documentation, promotion to a test environment, and general documentation like time sheets and status reports. Quality processes like reviews, audits are also described.

Uploaded by

venkata ganga dhar gorrela
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
114 views

Project Xplanation

The document outlines the requirements and responsibilities for two types of work received from an onsite coordinator: issues, which involve estimating tasks, writing approach documents, coding, testing, and creating root cause analysis documents; and project development, which follows a process from business requirements and design documents to coding, testing, documentation, promotion to a test environment, and general documentation like time sheets and status reports. Quality processes like reviews, audits are also described.

Uploaded by

venkata ganga dhar gorrela
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Requirement which we will be receiving from onsite coordinator is basically of two types

Issue

Project development

Issue:

The On-site coordinator will send you the issue details

Your Responsibility –

You have to provide estimates to complete the task by discussing with your offshore team leader.

Once the estimates are finalized, you have to prepare an approach document for that issue.

You are good to start with coding once the approach is finalized

Code changes

Example: In one of the graphs you have not captured the dropped records which are required for business.

Unit testing - You have to test against to your code changes.

And integration testing is must for the issue resolution- You have to do end to end testing.

Prepare a Root Cause Analysis document (RCA) to

Prevent/avoid from the same type of failures in future

Provide you the quick resolution if the same issue occurs in future

Project development:

The project development will start with the Business Requirement Document/Business specification Document
(BRD/BSD) which will be provided by the customer/client.

BRD will contain the below information:

1. What about the whole project is (objectives), scope of the project


2. Who are all going to access/use the result
3. Assumptions and risks
4. dependencies
5. Whether balance is required or not
6. Whether flashback is required or not while loading data into base tables.
7. backup

Your Responsibilities:

You (your entire team, most of the times the team leader and senior developers) have to do thorough analysis
on BRD and need to come up with High Level Design (HLD) document
Contents of the HLD:

Detail description of the project:

The number of graphs

The project flow diagram

High level description of each graph

Environment information

Server names and db names/schema names

Naming conventions and standards

Initial migration/load and Daily/Incremental load

If balance and flash back queries are required, how are we going to implement for our project.

Cleanup/ Close up process

Scheduling controls

Mapping Document which will consists of the mapping rules from sources to target system.

Sometimes this mapping document will be prepared from client side and in some cases by us (our team).

Then Coding and Low Level Design (LLD) documentation will go in parallel based on HLD.

Content of LLD:

Information on Predecessor & successor jobs

Parameters & description

Detailed description of each and every graph

Layout of the graph

How are you implementing the logic

Input files with dml

Output files with dml

Job scripts

Test cases

Once coding part is done and before migrating the code to QC (Testing) environment you need to make sure
that the graph is developed according to the development check list.
Once cross checked with check list, then we will be good to go with unit testing

Unit testing will have two parts

Unit Test Plan (UTP)

Unit Test Results (UTR)

Unit test plan will have test cases and expected result.

Unit test results document:

Test case

Expected result

Result

Integration testing:

ITP

ITR

Check in to EME by creating Tag and Migration form.

Migration form will have the below information:

Tag name

All the objects present in tag

Promotion to QC environment

==================================================================================

General documents/time sheets:

Every week/fort night need to submit the time sheets – Internal

- for client billing

Monthly Status Report (MSR) -- need to send to onsite coordinator

For Quality purpose:

Need to fill what u did for the week

What is your development time

Review time
How many bugs you found as part of your review..

Audit will happen on every project once in 3/4/6 months.

You might also like