Scribd
Upload
127 views3 pages

Project Life Cycle

The document outlines the typical phases in an ETL project life cycle from business requirements gathering to production deployment. It includes phases for requirements collection, design, development, testing, and production rollout. The key phases are business requirements collection, system requirements specification, high-level and low-level design, coding, unit testing, integration testing, user acceptance testing, and moving to the production environment.

Uploaded by

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

Project Life Cycle

The document outlines the typical phases in an ETL project life cycle from business requirements gathering to production deployment. It includes phases for requirements collection, design, development, testing, and production rollout. The key phases are business requirements collection, system requirements specification, high-level and low-level design, coding, unit testing, integration testing, user acceptance testing, and moving to the production environment.

Uploaded by

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

DataWareHousing - ETL Project Life Cycle ( Simple to understand )

> Data warehousing projects are categorized into 4 types. 1) Development Projects. 2) Enhancement Projects 3) Migration Projects 4) Production support Projects. -> The following are the different phases involved in a ETL project development life cycle. 1) Business Requirement Collection ( BRD ) 2) System Requirement Collection ( SRD ) 3) Design Phase a) High Level Design Document ( HRD ) b) Low level Design Document ( LLD ) c) Mapping Design 4) Code Review 5) Peer Review 6) Testing a) Unit Testing b) System Integration Testing. c) USer Acceptance Testing ( UAT ) 7) Pre - Production 8) Production ( Go-Live ) Business Requirement Collection :---------------------------------------------> The business requirement gathering start by business Analyst, onsite technica l lead and client business users. -> In this phase,a Business Analyst prepares Business Requirement Document ( BRD ) (or) Business Requirement Specifications ( BRS ) -> BR collection takes place at client location. -> The o/p from BR Analysis are -> BRS :- Business Analyst will gather the Business Requirement and document in BRS -> SRS :- Senior technical people (or) ETL architect will prepare the SRS which contains s/w and h/w requirements. The SRS will includes a) O/S to be used ( windows or unix ) b) RDBMS required to build database ( oracle, Teradata etc ) c) ETL tools required ( Informatica,Datastage ) d) OLAP tools required ( Cognos ,BO ) The SRS is also called as Technical Requirement Specifications ( TRS ) Designing and Planning the solutions :------------------------------------------------> The o/p from design and planning phase is a) HLD ( High Level Design ) Document b)LLD ( Low Level Design ) Document HLD ( High Level Design ) Document : An ETL Architect and DWH Architect participate in designing a solution to build a DWH. An HLD document is prepared based on Business Requirement. LLD ( Low Level Design ) Document : Based on HLD,a senior ETL developer prepare Low Level Design Document The LLD contains more technical details of an ETL System.

An LLD contains data flow diagram ( DFD ), details of source and targets of eac h mapping. An LLD also contains information about full and incremental load. After LLD then Development Phase will start Development Phase ( Coding ) :--------------------------------------------------> Based an LLD, the ETL team will create mapping ( ETL Code ) -> After designing the mappings, the code ( Mappings ) will be reviewed by deve lopers. Code Review :-> Code Review will be done by developer. -> In code review,the developer will review the code and the logic but not the data. -> The following activities takes place in code review -> You have to check the naming standards of transformation,mappings of data et c. -> Source and target mapping ( Placed the correct logic or not in mapping ) Peer Review :-> The code will reviewed by your team member ( third party developer ) Testing:-------------------------------The following various types testing carried out in testing environment. 1) Unit Testing 2) Development Integration Testing 3) System Integration Testing 4) User Acceptance Testing Unit Testing :-> A unit test for the DWH is a white Box testing,It should check the ETL proce dure and Mappings. -> The following are the test cases can be executed by an ETL developer. 1) Verify data loss 2) No.of records in the source and target 3) Dataload/Insert 4) Dataload/Update 5) Incremental load 6) Data accuracy 7) verify Naming standards. 8) Verify column Mapping -> The Unit Test will be carried by ETL developer in development phase. -> ETL developer has to do the data validations also in this phase. Development Integration Testing -> Run all the mappings in the sequence order. -> First Run the source to stage mappings. -> Then run the mappings related to dimensions and facts. System Integration Testing :-> After development phase,we have to move our code to QA environment. -> In this environment,we are giving read-only permission to testing people. -> They will test all the workflows. -> And they will test our code according to their standards. User Acceptance Testing ( UAT ) :-> This test is carried out in the presence of client side technical users to v erify the data migration from source to destination. Production Environment :---------------------------------> Migrate the code into the Go-Live environment from test environment ( QA Env

ironment ).

You might also like