You are on page 1of 4

ETL Process Definitions and Deliverables

1.0 Define Requirements In this process you should understand the


business needs by gathering information from the user. You should understand
the data needed and if it is available. Resources should be identified for
information or help with the process.
o Deliverables
A logical description of how you will extract transform and load
the data.
Sign-off of the customers!.
o Standards
"ocument #$% business re&uirements specification using either
the #$% 'usiness Re&uirements Specification $emplate( your own
team-specific business re&uirements template or system( or )racle
"esigner.
o Templates
#$% 'usiness Re&uirements Specification $emplate
2.0 Create P!sical Desi"n In this process you should define your inputs
and outputs by documenting record layouts. You should also identify and define
your location of source and target( file*table si+ing information( volume
information( and how the data will be transformed.
o Deliverables
Input and output record layouts
%ocation of source and target
,ile*table si+ing information
,ile*table volume information
"ocumentation on how the data will be transformed if at all
o Standards
-omplete #$% 'usiness Re&uirements Specification using using
one of the methods documented in the previous steps.
Start #$% .apping Specification
o Templates
#$% 'usiness Re&uirements Specification $emplate
#$% .apping Specification $emplate
#.0 Desi"n Test Plan /nderstand what the data combinations are and define
what results are expected. Remember to include error chec0s. "ecide how many
test cases need to be built. %oo0 at technical ris0 and include security. $est
business re&uirements.
o Deliverables
#$% $est 1lan
#$% 1erformance $est 1lan
*var*www*apps*conversion*tmp*scratch23*454678689.doc
o Standards
"ocument #$% test plan and performance plan using either the
standard templates listed below or your own team-specific
templates!.
o Templates
#$% $est 1lan $emplate
#$% 1erformance $est 1lan $emplate
$.0 Create ETL Process Start creating the actual Informatica #$% process.
$he developer is actually doing some testing in this process.
o Deliverables
.apping Specification
.apping
:or0flow
Session
o Standards
Start the #$% )b;ect .igration ,orm
Start "atabase )b;ect .igration ,orm if applicable!
-omplete #$% .apping Specification
-omplete cleanup process for log and bad files Refer to Standard
log<bad file cleanup.doc
,ollow Informatica =aming Standards
o Templates
#$% )b;ect .igration ,orm
#$% .apping Specification $emplate
"atabase )b;ect .igration ,orm if applicable!
%.0 Test Process $he developer does the following types of tests> unit(
volume( and performance.
o Deliverables
#$% $est 1lan
#$% 1erformance $est 1lan
o Standards
-omplete #$% $est 1lan
-omplete #$% 1erformance $est 1lan
o Templates
#$% $est 1lan $emplate
#$% 1erformance $est 1lan
&.0 'al(trou" ETL Process :ithin the wal0through the following
factors should be addressed> Identify common modules reusable ob;ects!(
efficiency of the #$% code( the business logic( accuracy( and standardi+ation.
o Deliverables
#$% process that has been reviewed
*var*www*apps*conversion*tmp*scratch23*454678689.doc
o Standards
-onduct #$% 1rocess :al0through
o Templates
#$% .apping :al0through -hec0list $emplate
).0 Coordinate *ove to +, - $he developer wor0s with the "'A to
organi+e #$% 1rocess move to ?A.
o Deliverables
#$% process moved to ?A
o Standards
-omplete #$% )b;ect .igration ,orm
-omplete /nix @ob Setup Re&uest ,orm
-omplete "atabase )b;ect .igration ,orm if applicable!
o Templates
#$% )b;ect .igration ,orm
/nix @ob Setup Re&uest ,orm
"atabase )b;ect .igration ,orm
..0 Test Process At this point( the developer once again tests the process
after it has been moved to ?A.
o Deliverables
$ested #$% process
o Standards
"eveloper validates #$% $est 1lan and #$% 1erformance $est 1lan
o Templates
#$% $est 1lan $emplate
#$% 1erformance $est 1lan $emplate
/.0 0ser 1alidates Data $he user validates the data and ma0es sure it
satisfies the business re&uirements.
o Deliverables
Aalidated #$% process
o Standards
Aalidate 'usiness Re&uirement Specifications with the data
o Templates
#$% 'usiness Re&uirement Specifications $emplate
10.0 Coordinate *ove to Production 2 $he developer wor0s with the
"'A to organi+e #$% 1rocess move to 1roduction.
o Deliverables
Accurate and efficient #$% process moved to production
o Standards
-omplete #$% )b;ect .igration ,orm
-omplete /nix @ob Setup Re&uest ,orm
*var*www*apps*conversion*tmp*scratch23*454678689.doc
-omplete "atabase )b;ect .igration ,orm if applicable!
o Templates
#$% )b;ect .igration ,orm
/nix @ob Setup Re&uest ,orm
"atabase )b;ect .igration ,orm if applicable!
11.0 *aintain ETL Process - $here are a couple situations when
maintaining an #$% process. $here is maintenance when an #$% process brea0s
and there is maintenance when and #$% process needs updated.
o Deliverables
Accurate and efficient #$% process in production
o Standards
/pdated 'usiness Re&uirements Specification if needed!
/pdated .apping Specification if needed!
Revised mapping in appropriate folder
/pdated #$% )b;ect .igration ,orm
"eveloper chec0s final results in production
All monitoring finding problems! of the #$% process is the
responsibility of the pro;ect team
o Templates
'usiness Re&uirements Specification $emplate
.apping Specification $emplate
#$% )b;ect .igration ,orm
/nix @ob Setup Re&uest ,orm
"atabase )b;ect .igration ,orm if applicable!
*var*www*apps*conversion*tmp*scratch23*454678689.doc

You might also like