ETL Estimate Guidelines

Version:
Updated By: cells that can be user entered
Date Updated: Constants
Hours/Day 7.5

Application Complexity Matrix

Base Time Build Test

Modules Assessment Design Implementation Totals
ETL Application Complexity Coding Unit Test Integration QA
(in Days) (in Hours)
# % Hours % Hours % Hours % Hours % Hours % Hours % Hours % Hours Days
Very Simple 1 7.5 5 5% 1.88 30% 11.25 20% 7.50 10% 3.75 10% 3.75 20% 7.50 5% 1.88 100% 37.50 5.00
Simple 2 15 6 5% 4.50 30% 27.00 20% 18.00 10% 9.00 10% 9.00 20% 18.00 5% 4.50 100% 90.00 12.00
Medium 5 37.5 8 5% 15.00 30% 90.00 20% 60.00 10% 30.00 10% 30.00 20% 60.00 5% 15.00 100% 300.00 40.00
Complex 8 60 2 5% 6.00 30% 36.00 20% 24.00 10% 12.00 10% 12.00 20% 24.00 5% 6.00 100% 120.00 16.00
Very Complex 15 112.5 1 5% 5.63 30% 33.75 20% 22.50 10% 11.25 10% 11.25 20% 22.50 5% 5.63 100% 112.50 15.00
Totals 22 33.00 198.00 132.00 66.00 66.00 132.00 33.00 660.00 88.00

Complexity Level Table

Complexity Description Guidelines for Classification Examples

1 Very Simple . Single source. . Staging mappings.

2 Simple
3 Medium
. No table joins
. No expression transformation.
. One-to-one mapping.
. Single path in the mapping pipeline.
. Single or multiple sources, but not more than 2. . Type 1 mappings.
. Simple logic applied to or implemented in a mapping.
. Single path in the mapping pipeline, with up to 2 lookups.
. Single or multiple sources, but not more than 3. . Type 1 mappings with error handling.
. Medium complex logic applied to or implemented in a mapping. . Type 2 mappings with or without error handling.
. Single or multiple paths in the mapping pipeline, but not more than 3 paths, and . Type 2 mappings with both Type-1 and Type-2 change triggers using
with up to 5 lookups. Type 2 Plug-In Maplet.

4 Complex . Single or multiple sources, but not more than 4. . Type 2 mappings with or without error handling.
. Multiple paths in the mapping pipeline, but not more than 5 paths, and with up to . Type 2 mappings with both Type-1 and Type-2 change triggers using
10 lookups. Type 2 Plug-In Maplet.

. Complex business/ transformation rules.

. Use of mapplets, but not more than 3 implemented in a mapping.
. More significant logic applied to or implemented in a mapping.
5 Very Complex . Single or multiple sources, more than 4. . This is a very rare scenario. It is strongly recommended that when
. Very complex logic applied or implemented to a mapping. design
a very complex ETL process, the process should be broken down into
. Very complex business/ transformation rules. simple processes. However, time needed for development of the
. Complex ETL process. process(es) should be within the estimate.
. Significant data anomalies.
. Use of mapplets, more than 3 implemented in a mapping.
. Impact to all mappings batches for the application.
. Multiple paths in the mapping pipeline, with more than 5 paths, and more than 10
lookups.
Estimates (effort)
Estimates include design, development, testing

Source to Integration:
10-20 days per table

Data Mart:
Average: 35 day (summaries, light derivations)
Complex: 70 days (complex derivations, multiple events)

Catalogue:
Average: 10 days

Cubes/Reports:
Average: 15 days

Estimates (phases)
Assessment 5%
Design 30%
Development 30%
Test 30%
Implementation 5%