Scribd
Upload
338 views3 pages

The Following Are The Different Phases Involved in A ETL Project Development Life Cycle

The document outlines the phases of an ETL project development lifecycle: 1) Requirement gathering involves collecting business and system requirements. 2) Design phase produces high and low level design documents. 3) Development phase includes mapping design, code review, testing unit/integration tests. 4) Testing involves unit, integration and user acceptance testing in test environments. 5) Production phase migrates the code to the production environment.

Uploaded by

Shiva CH
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
338 views3 pages

The Following Are The Different Phases Involved in A ETL Project Development Life Cycle

The document outlines the phases of an ETL project development lifecycle: 1) Requirement gathering involves collecting business and system requirements. 2) Design phase produces high and low level design documents. 3) Development phase includes mapping design, code review, testing unit/integration tests. 4) Testing involves unit, integration and user acceptance testing in test environments. 5) Production phase migrates the code to the production environment.

Uploaded by

Shiva CH
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

The following are the different phases involved in an ETL project development life cycle.

1) Requirement Gathering a) usiness Requirement !ollection " R# ) $) %ystem Requirement !ollection " %R# ) &) #esign 'hase a) (igh Level #esign #ocument " (R# ) $) Low level #esign #ocument " LL# ) )) #evelopment 'hase a) *apping #esign $) !ode Review c) 'eer Review +) Testing a) ,nit Testing $) %ystem -ntegration Testing. c) ,%er .cceptance Testing " ,.T ) /) 're 0 'roduction 1) 'roduction " Go0Live ) Requirement Gathering: 000000000000000000000000000000000000000000000 Business Requirement Collection ( BRD ): 02 The $usiness requirement gathering start $y $usiness .nalyst3 onsite technical lead and client $usiness users. 02 -n this phase3a usiness .nalyst prepares usiness Requirement #ocument " R# ) "or) usiness Requirement %pecifications " R% ) 02 R collection ta4es place at client location. 02 The o5p from R .nalysis are 02 R% usiness Requirement %pecifications 02 %R% %ystem Requirement %pecifications System Requirement Collection ( SRD ): %enior technical people "or) ETL architect will prepare the %R% which contains s5w and h5w details The %R% will includes a) 65% to $e used " windows or uni7 ) $) R# *% required to $uild data$ase " oracle3 Teradata etc ) c) ETL tools required " -nformatica3#atastage ) d) 6L.' tools required " !ognos 3 6 ) The %R% is also called as Technical Requirement %pecifications " TR% ) Design Phase: 000000000000000000000000000000000000000 02 The o5p from design and planning phase is a) (L# " (igh Level #esign ) #ocument $)LL# " Low Level #esign ) #ocument HLD ( High Level Design ) Document : -

.n ETL .rchitect and #8( .rchitect participate in designing a solution to $uild a #8(. .n (L# document is prepared $ased on usiness Requirement. LLD (Lo Level Design) Document: ased on (L#3 senior ETL developer prepares Low Level #esign #ocument The LL# contains more technical details of an ETL %ystem. .n LL# contains data flow diagram "#9#)3 details of source and targets of each mapping. .n LL# also contains information a$out full and incremental load. .fter LL# then #evelopment 'hase will start Develo!ment Phase : 00000000000000000000000000000000000000000000000000 "a!!ing: 02 ased an LL#3 the ETL team will create mapping " ETL !ode ) 02 .fter designing the mappings3 the code " *appings ) will $e reviewed $y developers. Co#e Revie :02 !ode Review will $e done $y developer. 02 -n code review3the developer will review the code and the logic $ut not the data. 02 The following activities ta4es place in code review 02 :ou have to chec4 the naming standards of transformation3mappings of data etc. 02 %ource and target mapping " 'laced the correct logic or not in mapping ) Peer Revie :02 The code will reviewed $y your team mem$er " third party developer ) $esting: 000000000000000 The following various types testing carried out in testing environment. 1) ,nit Testing &) #evelopment -ntegration Testing )) %ystem -ntegration Testing +) ,ser .cceptance Testing %nit $esting :02 . unit test for the #8( is a white o7 testing3-t should chec4 the ETL procedure and *appings. 02 The following are the test cases can $e e7ecuted $y an ETL developer. 1) ;erify data loss &) <o.of records in the source and target )) #ataload5-nsert +) #ataload5,pdate /) -ncremental load 1) #ata accuracy =) verify <aming standards. >) ;erify column *apping 02 The ,nit Test will $e carried $y ETL developer in development phase. 02 ETL developer has to do the data validations also in this phase.

Develo!ment &ntegration $esting 02 Run all the mappings in the sequence order. 02 9irst Run the source to stage mappings. 02 Then run the mappings related to dimensions and facts. System &ntegration $esting :02 .fter development phase3we have to move our code to ?. environment. 02 -n this environment3we are giving read0only permission to testing people. 02 They will test all the wor4flows. 02 .nd they will test our code according to their standards. %ser 'cce!tance $esting ( %'$ ) :02 This test is carried out in the presence of client side technical users to verify the data migration from source to destination. Pro#uction (nvironment:000000000000000000000000000000000 02 *igrate the code into the Go0Live environment from test environment " ?. Environment ).

You might also like