8/17/2019 Client Introduction

1/3

8/17/2019 Client Introduction

2/3

  3roduction

Analysis and Requirement athering:

4utput: #nalysis oc( %ubject #rea

5667 in onsite(

'usiness #nalyst( project manager.

2ather the useful information for the %% and indentifying the subject areas( identify the

schema objects and all.

Design:

4utput: Technical esign oc8s( !"(9T3

&T" "ead( '# and ata #rchitect

67 onsite .- %chema design in &rwin and implement in database and preparing the technicaldesign document for &T".

067 offshore: !" ; 9T3

!":

  !igh "evel esign ocument( 'ased on the Technical specs. evelopers has

to create the !"( it will have the Informatica flow chart. What are the transformations re,uired

for that mapping. !" will cover only

8/17/2019 Client Introduction

3/3

67 offshore

based on the integration test plan testing the application and gives the bugs list to the

developer. evelopers will fi$ the bugs in the development repository and again migrated to

testing repository. #gain testing starts till the bugs free code.

067 4nsite

9#T 9ser #ccept Testing. Client will do the 9#T. This is last phase of the

&T" project.

Production:

=67 offshore =67 onsite

Work will be distributed between offshore and onsite based on the run time of the "oading.

Mapping bugs needs to fi$ by evelopment team. evelopment team will support for warranty

period based on agreement days.

In &T" projects Three 1epositories. /or each repository access permissions and location will bedifferent.

evelopment: &5

Testing: &0

3roduction: &>

*ote: &5( &0( &> are 1epository names. *othing else.

imensions:

  &mployee

  Customer   #gent

  Transaction

  ate

/acts are relation between all those tables.