Data modeling.

Presentation by Anupama Vudaru, Phani Kondapalli

Content by Prathibha Madineni, Subrahmanyam Kolluri
October 2010
Preface

Agenda Basics of Data Modeling, Insurance industry and Erwin

Duration and timings 4 days x 2 hrs

Expectations In-class, hands on and post session work

Course contents Divided into slides, videos and print outs

Legends used

Post-session work Attendees are expected to do hands-on home work assigned for the day
Contents
A. Data Modeling overview
B. Data Modeling development life cycle
Day 1 C. Components of Data Modeling
D. Data Modeling notations and design standards
E. Case study CDM overview

A. Conceptual data model

B. Types of Data modeling
Day 2 C. Various tools available
D. Developing CDM using Erwin
E. Case study LDM overview

A. Logical data model

B. Developing LDM using Erwin
Day 3 C. Meta Data preservation for Design Considerations
D. Dimensional Data Modeling
E. Case study PDM overview

A. Physical data model

B. Logical Data Model vs Physical Data Model
Day 4
C. Developing PDM using Erwin
D. Advanced Features of Erwin
Day 4

A. Physical data model

B. Logical Data Model vs Physical Data Model

C. Developing PDM using Erwin

D. Advanced Features of Erwin

A. Physical Data Modeling

1. Though the PDM is the representation Example of Physical Data Model

of the underlying database
implementation, it should still depict
the entire model as a diagram /
visualization
2. Many tool vendors concentrate on
developing a tool for DDL generation /
synchronization in this layer
3. In many cases the PDM evolves from
LDM. Each entity is implemented as a
Table, each relationship as a DB
constraint etc
4. This evolution often keeps the
performance and maintenance into
consideration, specific to a database
vendor
5. Like LDM, PDM can and should be
proven in two way - by mapping the
logical entities and relationships to the
physical tables and constraints and by
physical storage for CRUD /
performance requirements
B. Logical Data Model vs Physical Data Model

Logical Data Model Physical Data Model

Represents the business requirements (entire or
part) of an organization
Identifies business information and defines
business rules including
Entities
Attributes
Key groups
Relationships
Streamlines the physical design process by clearly
defining data structures and their relationships
Key duties of logical data modeler:
Needs business requirements
Creates and maintains lookup data
Compares the versions of data model
Maintains change log
Generates reports from data model
Represents physical implementation of databases
Converts key business information to technical
details:
Tables
Columns (including properties)
Database properties
Relationships
Key parameters for physical data model:
Database performance
Indexing strategy
Physical storage
Demoralization
Key duties of physical data modeler:
To know source and target databases
To create data models from existing databases
To tune data models with referential integrity,
alternate keys and indexes
C. Developing PDM using Erwin

1. Case study
Database knowledge
Performance requirements
Convert the entities to tables/partitions
Convert the relations to constraints
Identify the entity types parent:child
Identify the properties of the columns data type:length:precision:scale:null
Identify the indexes bitmap/btree:partition/global
Other database properties storage/db parameters/etc
C. Developing PDM using Erwin

1. Case study

06. PDM
 D. Advanced Features of Erwin

1. Reverse Engineering - Reverse Engineering is a scripts to update any database while

very powerful technique for discovering the preserving existing data. Complete-Compare
structures of databases. It is particularly useful keeps the model synchronized with the
for operational databases for which no up-to- database at all times.
date documentation is available. 4. Meta Integration A feature which lets the
2. Forward Engineering - Forward Engineering is modeling and meta data to be ready for
the process that generates the physical export to and import from available popular
database schema from the data model. You BI/DW tools.
can use ERwins forward engineering feature 5. Report Wizard Generate reports and
to design and create your database without document the knowledge on the Data Model
writing underlying SQL code manually. Erwin using reporting wizard. It supports all popular
supports wide varieties of databases and and rich text based documentation and
specific features. reporting.
3. Complete Compare - Complete-Compare
provides a comprehensive comparison of all
differences between two Erwin models or
Model and Database. By highlighting any
discrepancies, changes can be migrated from
model-to-database or database-to-model.
ERwin also automatically generates alter
D. Advanced Features of Erwin

Meta Integration A feature which lets the modeling and meta data to be ready for export to and
import from available popular BI/DW tools.