Data Modeling and Database Design Using ERwin

[Link] 2000

PRACTICAL DATA MODELING and DATABASE DESIGN USING ERWIN

ERWIN and Its Main Features Data Modeling Using ERWIN Before Database Design Transforming Data Model To Database Design Reverse Engineering ERWIN Reports Samples
[Link] 2000

ERWIN and Its Main Features

ERWIN and Its Main Features

Erwin*; A Data Modeling and Database Design Application CASE Tool working on Windows

What is ERWIN?

* CopyRighted by Logic Works and Platinum Inc.

[Link] 2000 [Link] 2000

ERWIN and Its Main Features Main Features

Forward Engineering: Transforming Data Model into Database Reverse Engineering: Obtaining Design Info and Data Model From a Relational Database

ERWIN and Its Main Features

Main Features: Supported DBMSs

Relational Data Model

Forward Engineering Reverse Engineering

Relational Database
[Link] 2000 [Link] 2000

ERWIN and Its Main Features Main Features: ORACLE Designer Data Modeling Tool

ERWIN and Its Main Features Main Features: Importing Entities from BPwin

ORACLE Designer 2000 Compatible

BPWin is an activity (process) modeling, and data flow diagramming tool

[Link] 2000

[Link] 2000

ERWIN and Its Main Features Main Features: BPWin ve ERWin

STRATEGY ANALYSIS DESIGN
BPWin Analysis Program ERWin Data Modeling and Database Design Tool
DOCUMENTATION

ERWIN and Its Main Features Main Features: Working Levels

1. Logical (Conceptual) Level (Data Modeling) 2. Physical Level

IMPLEMENTATION

TEST
FEEDBACK

System Development Life Cycle

[Link] 2000

[Link] 2000

ERWIN and Its Main Features Main Features: Working Levels (for Version 3.5.2) 1. Logical Level (Data Modeling)

ERWIN and Its Main Features Main Features: Working Levels (For Version 4 )

1. Logical Level (Data Modeling)

Exclusive Sub-Category

Adding Entity

Adding Text

Adding Entity

Exclusive Sub-Category

Selection
Changing Attributes

Non-identifying Relationship

Non-identifying Relationship Selection

Identifying relationship

many-to-many relationship

Identifying relationship many-to-many relationship [Link] 2000 [Link] 2000

ERWIN and Its Main Features Working Levels 2. Physical Level (Version 3.5.2)

ERWIN and Its Main Features Working Levels 2. Physical Level (Version 4)

Independent Table

View

Adding Text

Independent Table

View

Selection
Changing Columns

Non-identifying Relationship

Selection Non-identifying Relationship

Identifying Relationship

View Relationship [Link] 2000

Identifying Relationship

View Relationship

[Link] 2000

ERWIN and Its Main Features Modeling and Design Stages for ERwin
PRODUCE DATA MODEL DESCRIBE DATA TYPES
SETTINGS FOR ACCESSING DATABASE

Data Modeling Using ERWIN Representing Entities and Attributes (Logical Level)
Logical Level

ENTITY NAME
Physical Level

Unique Identifier Attributes

Native or ODBC

Other Attributes
VIA SQL SCRIPTS
BY CONNECTING TO DATABASE

REVERSE ENGINEERING

Forward Engineering

Foreign KeyAttribute

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN Representing Entities and Attributes (Logical Level)

Data Modeling Using ERWIN

Composite Unique Identifiers Entity Name Key Area Composite Unique Identifier Non-Key Area Other Attributes

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN Optionality in Attributes

Click twice on any entity to open it in attribute editor

Data Modeling Using ERWIN Representing Foreign Key Attributes

Required attribute

Master Entity

Child Entity

There are two different relationships between Entity 1 and Entity 2. 1. Identifying Relationships 2. Non-Identifying Relationships
[Link] 2000

[Link] 2000

Data Modeling Using ERWIN Many-to-many Relationships

Data Modeling Using ERWIN

Representing Foreign Key Attributes

Representing Foreign Key Attributes

Non-Identifying Relationships Identifying Relationship In both relationships, Unique Identifier in master entity goes to the second (child) entity as foreign key.
[Link] 2000

Crow foot

Identifying Relationship
(Unique Identifier of Entity 1 becomes the part of unique identifier in entity 2. It is placed in key area of second entity)
[Link] 2000

Data Modeling Using ERWIN

Data Modeling Using ERWIN

Representing Foreign Key Attributes Use Different names for the attributes in key area (unique identifier)

Optionality Overwrites the attribute

Non-Identifying Relationship
(Unique Identifier of Entity 1 becomes new attribute in entity 2. It is placed in non-key area of second entity)
[Link] 2000 [Link] 2000

Data Modeling Using ERWIN

Data Modeling Using ERWIN

Use Different names for the attributes in key area (unique identifier)

Tables and Columns (Physical Representation) Table Name Unique Identifier Column Other Columns

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN

Data Modeling Using ERWIN Tables and Columns (Physical Representation)

Tables and Columns (Physical Representation)

Changing default data types for Physical level Note: All Attributes are assigned as char(18) (or any default value defined) when the level is changed to physical one.
[Link] 2000 [Link] 2000

Data Modeling Using ERWIN

Adding Icons to Entities and Attributes

Data Modeling Using ERWIN

Adding Icons to Entities and Attributes

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN Establishing Non-identifying Relationship 1. Choose Non-identifying Relationship 2. Click the master entity (DEPARTMENT in this case) 3. Click the child entity (EMPLOYEE)

Data Modeling Using ERWIN Establishing Identifying Relationship 1. Choose Identifying Relationship 2. Click the master entity (EMPLOYEE in this case) 3. Click the child entity (EMPLOYEE CHILD)

DEPARTMEN ID in DEPARTMENT comes as foreign key to the non-key area of EMPLOYEE

EMPLOYEE ID in EMPLOYEE comes as foreign key to the key area of EMPLOYEE CHILD

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

1. Many-to-one (One-to-many) Relationships (Mandatory) Child Entity

assigned to EMPLOYEE made up of DEPARTMENT

2. Many-to-one (One-to-many) Relationships (Optional) Child Entity

assigned to EMPLOYEE made up of DEPARTMENT

Parent Entity ORACLE

Parent Entity ORACLE

ERWin
Non-identifying Relationship [Link]
2000

ERWin
Non-identifying Relationship [Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

3. One-to-one Relationships (Optional) Child Entity

containing CAR installed in ENGINE

4. One-to-one Relationships (Mandatory) Parent Entity ORACLE Child Entity

containing CAR installed in ENGINE

Parent Entity ORACLE

ERWin
Non-identifying Relationship Non-identifying Relationship

ERWin

The entity covering the other entity is defined as child entity in one-to-one relationship.

[Link] 2000

The entity covering the other entity is defined as child entity in one-to-one relationship.

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

5. Many-to-many Relationships

5. Many-to-many Relationships

1. Choose many-to-many relationship in Logical Level

assigned to EMPLOYEE staffing DEPARTMENT

2. Click on both entities

ORACLE

Note: First, you have to resolve many-to-many relationships

3. If you have chosen auto-transform, then an intersection entity will be added automatically.
[Link] 2000 [Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

5. Many-to-many Relationships

5. Many-to-many Relationships

Intersection Entity Added Automatically

It becomes identifiying relationship

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

6. Obtaining Uniqueness via Relationships

ACCOUNT #* Account No * Type

ORACLE Designer
BANK #* Bank ID * Name

7. Recursive Relationships ORACLE Designer

EMPLOYEE #* employee ID * name * surname o job

opened in opening

ERwin

managed by

ERwin

manager for Represented as identifying relationship

[Link] 2000

Modeled as Non-identifying Relationship as in one-to-many relationship

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

7. Recursive Relationships

7. Recursive Relationships

1. First, identify the entity and its unique identifier

1. First, identify the entity and its unique identifier 2. Choose non-identifying relationship from toolbox

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

7. Recursive Relationships

7. Recursive Relationships

1. First, identify the entity and its unique identifier 2. Choose non-identifying relationhip from toolbox 3. Click twice on the same entity (EMPLOYEE)

1. First, identify the entity and its unique identifier 2. Choose non-identifying relationhip from toolbox 3. Click twice on the same entity (EMPLOYEE) 4. EMPLOYEE ID has not come as Foreign Key

[Link] 2000

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

7. Recursive Relationships

7. Recursive Relationships

1. First, identify the entity and its unique identifier 2. Choose non-identifying relationhip from toolbox 3. Click twice on the same entity (EMPLOYEE) 4. EMPLOYEE ID has not come yet as Foreign Key 5. Click twice on the relationship to identify rolename
[Link] 2000

MANAGER ID comes as Foreign key.

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

8. Exclusive Relationships
EMPLOYEE # * employee id * name * lastname o job assigned as
d ne sig as as

8. Exclusive Relationships
WORKER o hourly rate o overtime rate EMPLOYEE # * employee id * name * lastname o job assigned as
d ne sig as

an entity under

an entity under

WORKER o hourly rate o overtime rate

as

Transferred to ERwin for each pair of relationships

[Link] 2000

y tit en er an und

y tit en er an und

STAFF o title

STAFF o title

Transferred to ERwin for each pair of relationships

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

8. Exclusive Relationships
EMPLOYEE # * employee id * name * lastname o job assigned as
d ne sig as as

9. Supertypes and Subtypes

WORKER o hourly rate o overtime rate
EMPLOYEE # * employee id * name * surname STAFF * title WORKER * hourly rate * overtime rate member for

One betw -to-ma n and een EM y relat io DE PAR PLOY nship E TM ENT E

an entity under

ip ION nsh latio and UN y re man RKER -toO One een W betw

assigned to deploying DEPARTMENT

Transferred to ERwin for each pair of relationships

[Link] 2000

Data Modeling Using ERWIN

Representing ORACLE Designer Notations under ERwin

9. Supertypes and Subtypes

EMPLOYEE # * employee id * name * surname STAFF * title WORKER * hourly rate * overtime rate

Modeled as Identifying Relationship

y tit en er an und

STAFF o title

made up of UNION

Modeled as Identifying Relationship

[Link] 2000

Transforming Data Model To Database Design Choosing Target Database Management System Database/Choose Database for selecting target database management system

NOTE: You have to be level under

[Link] 2000

[Link] 2000

Transforming Data Model To Database Design Choosing Target Database Management System
Supported Database Management Systems

Before Transforming Data Model Making Connection Settings for Target Database Management System ODBC Settings For connecting to DBMS

Desktop SQL Dataase Management Systems DBMS

You can also access to the DBMSs not listed here via ODBC/Generic

1. IBM DB2 2. IBM AS/400 3. ORACLE 4. MS SQL Server 5. InterBase 6. SYBASE 7. PROGRESS 8. INFORMIX 9. Ingres 10. Red Brick 11. SQLBase 12. Rdb 13. WATCOM/SQL Anywhere 14. Teradata 15. Clipper 16. FoxPro 17. dBase 18. Access 19. Paradox

You can directly invoke ODBC Administrator from Run Dialog:

[Link] 2000

odbcad32

[Link] 2000

Before Transforming Data Model Making Connection Settings for Target Database Management System

Transforming Data Model To Database Design

Example; Settings for connecting to Oracle DBMS through ODBC

For adding new connection

For connecting to Oracle DBMS

[Link] 2000

[Link] 2000

Transforming Data Model To Database Design

Example; Settings for connecting to Oracle DBMS through ODBC

Transforming Data Model To Database Design

Example; MS SQL Server Connections

Connection name to connect (You can reach under ERWin ODBC Connection) Service name

Connection Name for SQL Server Optional Description

Username AI1 is the server name

ODBC Settings for each DBMS is different (like printer drivers)

[Link] 2000 [Link] 2000

10

Transforming Data Model To Database Design Forward Engineering Applying the principles of Systems Development Life Cycle (SDLC) (Going from the top to bottom in Waterfall model)

Transforming Data Model To Database Design Forward Engineering Choose Forward Engineer Under Tools

Producing the Relational Database Objects via the use of Data Models

[Link] 2000

[Link] 2000

Transforming Data Model To Database Design Forward Engineering: Settings

Transforming Data Model To Database Design Forward Engineering

1. Press 2. Give required security information and press Connect button.

Options ODBC Connection Native Connection

Filtering model Preview Print objects SQL Script SQL Script

[Link] 2000

Write SQL Script to a File

Generate Database Objects

[Link] 2000

Transforming Data Model To Database Design Produce the database objects from data model directly

Transforming Data Model To Database Design Produce the database objects from data model using SQL Script

1. Press 2.

button

SQL Script filename

[Link] 2000

[Link] 2000

11

Transforming Data Model To Database Design Produce the database objects from data model using SQL Script

Transforming Data Model To Database Design Produce the database objects from data model using SQL Script Just run the SQL Script File using tools under the DBMSs
Examples Oracle SQL*Plus for Oracle DBMS Query Analyzer for MS SQL Server

Name of Script File Oracle SQL*Plus for Oracle DBMS

[Link] 2000 [Link] 2000

Transforming Data Model To Database Design Produce the database objects from data model using SQL Script Just run the SQL Script File using tools under the DBMSs
Examples Oracle SQL*Plus for Oracle DBMS Query Analyzer for MS SQL Server

Transforming Data Model To Database Design Produce the database objects from data model using SQL Script

Query Analyzer for MS SQL Server

[Link] 2000

Interactive SQL for Interbase DBMS

[Link] 2000

Reverse Engineering Reverse Engineering Applying the principles of Systems Development Life Cycle (SDLC) in reverse order (Going from the bottom to top in Waterfall model)

Reverse Engineering Reverse Engineering Select Reverse Engineer under Tools Menu

Inferring the Data Model from Database Objects

[Link] 2000

[Link] 2000

12

Reverse Engineering Reverse Engineering: Settings As in forward engineering, connections are achieved via the native or ODBC type of connection

Reverse Engineering Reverse Engineering

Choose the Target DBMS to reverse engineer the database

[Link] 2000

[Link] 2000

Reverse Engineering Reverse Engineering Data model can be obtained from; 1. DBMS by direct connection 2. SQL Script Files

Reverse Engineering Reverse Engineering

If the database is not relational then you can infere primary keys and relationships from Indexes and the column names in tables
[Link] 2000 [Link] 2000

Reengineering Other Functions

ERwin Reports Report Generation

Reengineering: Compares the data model and physical database. You can update the data model via the database or database via the data model

For report generation

[Link] 2000

[Link] 2000

13

ERwin Reports Reports

ERwin Reports Reports: Example; Table/Physical Properties

[Link] 2000

[Link] 2000

ERwin Reports Reports: Reports are generated Using Report Templates and Output type (such as HTML)

ERwin Reports Reports: Reports are generated Using Report Templates and Output type (such as HTML)

[Link] 2000

[Link] 2000

A typical data model using ERwin

Sample data model using Oracle Designer

[Link] 2000

[Link] 2000

14

Sample data model using ERwin

[Link] 2000

15