Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 9

ETL Design Page: 1 of 9

Telecom Case Study –


ETL Design Document

Issue: 1.0

Date: 03/05/2007

____________________________________________________________________________________________________________________
ETL Design Page: 2 of 9

INDEX
1 OVERVIEW.......................................................................................................................................................................................................3

2 INTRODUCTION.............................................................................................................................................................................................3

3 REQUIREMENTS............................................................................................................................................................................................3

4 PRE-REQUISITES/DEPENDENCIES/ASSUMPTIONS/RISKS................................................................................................................5
4.1 Pre-Requisites – H/w & S/w..................................................................................................................................................................5
4.1.1 Hardware........................................................................................................................................................................................5
4.1.2 Software...........................................................................................................................................................................................6
5 MAPPING DETAILS........................................................................................................................................................................................6

6 DATABASE DESIGN.......................................................................................................................................................................................6
6.1.1 Conceptual Data Model:.................................................................................................................................................................6
6.1.2 Data Structures:..............................................................................................................................................................................6
6.1.2.1 Partitioned table.................................................................................................................................6
6.1.2.2 Indexes...............................................................................................................................................6
6.1.2.3 Stored Packages.................................................................................................................................6
6.1.2.4 Extract Files.......................................................................................................................................6
7 DEVELOPMENT METHOD USED...............................................................................................................................................................7

8 ADMINISTRATIVE ACTIVITIES.................................................................................................................................................................7

9 RELATED DOCS/REFERENCES/GLOSSARY/BIBLIOGRAPHY/TERMINOLOGY..........................................................................7
9.1.............................................................................................................................................................................................................................7
9.2.............................................................................................................................................................................................................................7
9.2.1 OLAP Data Structure......................................................................................................................................................................7
9.2.2 OLTP Data Structure......................................................................................................................................................................8
9.3.............................................................................................................................................................................................................................8
9.3.1.....................................................................................................................................................................................................................8
9.3.2.....................................................................................................................................................................................................................8
9.3.3.....................................................................................................................................................................................................................8
9.3.4.....................................................................................................................................................................................................................8
9.3.5.....................................................................................................................................................................................................................8
9.3.6.....................................................................................................................................................................................................................8
9.3.7.....................................................................................................................................................................................................................9
9.4.............................................................................................................................................................................................................................9
10 CONFIGURATION MANAGEMENT......................................................................................................................................................9

AUTHORISATION:.....................................................................................................................................................................................................9

____________________________________________________________________________________________________________________
ETL Design Page: 3 of 9

1 Overview

The Objective of the assignment is to create a case study for complete data warehouse life cycle.
It includes identification of source and target objects, ETL process design and development
along with creation of sample reports.

This assignment can be used across centers for DWH trainings. People who are undergoing
Informatica trainings can use this as an assignment after completion of their training program.

2 Introduction

The assignment is based on the processes involved in Prepaid Recharge and Billing of typical
GSM service provider organization. Customer, Product, Services, Invoice, Calls and Payment
data is picked from OLTP system and summarized according to needs of business analysts and
populated in Data Mart which is further used to generate reports to study existing business and
prepare future strategies.

3 Requirements
The requirements can be listed as follows:

Requirement Tracking Requirement Description Related Requirements


ID (optional)

R1 Analysis of Source System

R2 Design, Build, Unit Test of


transformation processes
for generation of
Dim_Customer table from
OLTP_TELECOM
schema.

R3 Design, Build, Unit Test of


transformation processes
for generation of
Dim_Time table from
OLTP_TELECOM
schema.

R4 Design, Build, Unit Test of


transformation processes
for generation of
Dim_Product table from
____________________________________________________________________________________________________________________
ETL Design Page: 4 of 9

OLTP_TELECOM
schema.

R5 Design, Build, Unit Test of


transformation processes
for generation of
Dim_Service table from
OLTP_TELECOM
schema.

R6 Design, Build, Unit Test of


transformation processes
for generation of
Dim_Company_Shops
table from
OLTP_TELECOM
schema.

R7 Design, Build, Unit Test of


transformation processes
for generation of
Dim_Geography table
from OLTP_TELECOM
schema.

R8 Design, Build, Unit Test of


transformation processes
for generation of
Dim_Salesmen table from
OLTP_TELECOM
schema.

R9 Design, Build, Unit Test of


transformation processes
for generation of
Fact_Calls table from
OLTP_TELECOM
schema.

R10 Design, Build, Unit Test of


transformation processes
for generation of
Fact_Invoices table from
OLTP_TELECOM
schema.

____________________________________________________________________________________________________________________
ETL Design Page: 5 of 9

R11 Design, Build, Unit Test of


transformation processes
for generation of
Fact_Payments table from
OLTP_TELECOM
schema.

R12 Design, Build, Unit Test of


transformation processes
for generation of
Fact_Prepaid_Balance
table from
OLTP_TELECOM
schema.

R13 Design, Build, Unit Test of


transformation processes
for generation of
Fact_Sales table from
OLTP_TELECOM
schema.

4 Pre-requisites/Dependencies/Assumptions/Risks
 Individual has basic understating on relational database, Data Warehouse concepts and ETL tool
(Informatica).

 Data coming from OLTP sources is meaningful.

 Team has some knowledge about telecom billing concepts.

4.1 Pre-Requisites – H/w & S/w

4.1.1 Hardware

Desktop with at least 512 MB RAM (Preferably 1GB) and 30-40 hard disk space with 1.2 GHz
or high processor with standard Accenture image.

____________________________________________________________________________________________________________________
ETL Design Page: 6 of 9

4.1.2 Software

Database (Preferably Oracle10g)


Informatica Power Centre (8.1)

5 Mapping Details

Informatica mappings are developed to load data in data mart. Please refer to section 9.3 for
further details.

6 Database Design
6.1.1 Conceptual Data Model:

Please refer to section 9.1

6.1.2 Data Structures:

Please refer to section 9.2


6.1.2.1 Partitioned table

NA

6.1.2.2 Indexes
NA

6.1.2.3 Stored Packages

NA
6.1.2.4 Extract Files

Extract Format
The file will be comma separated delimited file.

File Name:
Cdr_Data.dat

File Header

NA
____________________________________________________________________________________________________________________
ETL Design Page: 7 of 9

File Body

Field Name Character Position


CustId 1-10
Call_Date 11-19
CustomerName 20-49
CLI 50-69
DialedNo 70-89
ProductId 90-99
ServiceId 100-109
Duration 110-115
Amount 116-128

File Trailer

NA

7 Development Method Used


Please refer to section 9.4

8 Administrative Activities
NA

9 Related Docs/References/Glossary/Bibliography/Terminology
9.1

Telecom_Case_Stud
y-Dimension Model

9.2
9.2.1 OLAP Data Structure

Olap_Schema_Objec
ts

____________________________________________________________________________________________________________________
ETL Design Page: 8 of 9

9.2.2 OLTP Data Structure

Oltp_Schema_Object
s

9.3
This section is having links to Mapping design documents.

9.3.1

M_OLAP_Dimension_
Load

9.3.2

M_OLAP_Fact_Invoic
es

9.3.3

M_OLAP_Fact_Paym
ents

9.3.4

M_OLAP_Dim_time

9.3.5

M_OLAP_Fact_Calls

9.3.6
____________________________________________________________________________________________________________________
ETL Design Page: 9 of 9

M_OLAP_Fact_Prepa
id_Balance

9.3.7

M_OLAP_Fact_Sales

9.4

Deployment_Steps

10 Configuration Management
DOCUMENT NAME: ETL_Design
ABSTRACT: This document briefs about design of ETL process for loading Telecom data mart.

AUTHORISATION:
Prepared By Reviewed By Authorized By
Name: Vikas Mittal Name: Deepali Dodamani Name:
Signature: Signature: Signature:

VERSION HISTORY:

Issue Date Description


1.0 03/05/2007 First Version

____________________________________________________________________________________________________________________

You might also like