
- •Contents
- •Intended Audience
- •Typographical Conventions
- •Benefits of Data Modeling
- •Data Modeling Sessions
- •Session Roles
- •Sample IDEF1X Modeling Methodology
- •Logical Models
- •The Entity Relationship Diagram
- •The Key-Based Model
- •The Fully-Attributed (FA) Model
- •Physical Models
- •The Transformation Model
- •The DBMS Model
- •Benefits of Data Modeling in ERwin
- •The Entity-Relationship Diagram
- •Defining Entities and Attributes
- •Logical Relationships
- •Many-to-Many Relationships
- •Validating the Design of the Logical Model
- •Data Model Example
- •Identifying Types of Keys
- •Selecting a Primary Key
- •Designating Alternate Key Attributes
- •Designating Inversion Entry Attributes
- •Relationships and Foreign Key Attributes
- •Dependent and Independent Entities
- •Identifying Relationships
- •Non-Identifying Relationships
- •Rolenames
- •Naming Entities and Attributes
- •Synonyms, Homonyms, and Aliases
- •Entity Definitions
- •Definition References and Circularity
- •Constructing a Business Glossary
- •Attribute Definitions
- •Rolenames
- •Definitions and Business Rules
- •Relationship Cardinality
- •Cardinality in Non-Identifying Relationships
- •Referential Integrity
- •Reading Referential Integrity Options
- •RI, Cardinality, and Identifying Relationships
- •RI, Cardinality, and Non-Identifying Relationships
- •Additional Relationship Types
- •Many-to-Many Relationships
- •N-ary Relationships
- •Recursive Relationships
- •Subtype Relationships
- •Complete Versus Incomplete Subtype Structures
- •Inclusive and Exclusive Relationships
- •When to Create a Subtype Relationship
- •Overview of the Normal Forms
- •Functional Dependence (FD)
- •Full Functional Dependence
- •First Normal Form (1NF)
- •Second Normal Form (2NF)
- •Third Normal Form (3NF)
- •Common Design Problems
- •Repeating Data Groups
- •Multiple Use of the Same Attribute
- •Multiple Occurrences of the Same Fact
- •Conflicting Facts
- •Derived Attributes
- •Missing Information
- •Unification
- •How Much Normalization Is Enough?
- •ERwin Support for Normalization
- •First Normal Form Support
- •Second and Third Normal Form Support
- •Creating a Physical Model
- •Summary of Logical and Physical Model Components
- •Denormalization
- •Classification of Dependent Entities
- •Glossary
- •Index

Creating a Physical Model
Creating a Physical Model
The following table summarizes the relationship between objects in a logical and physical model.
Summary of Logical and Physical Model Components
Logical Model |
Physical Model |
|
|
Entity |
Table |
|
|
Dependent entity |
FK is part of child table’s PK |
|
|
Independent entity |
Parent table or, if child table, FK is |
|
NOT part of child table’s PK |
|
|
Attribute |
Column |
|
|
Logical datatype (text, number, |
Physical datatype (valid example varies |
datetime, blob) |
depending on the target server |
|
selected) |
|
|
Domain (logical) |
Domain (physical) |
|
|
Primary key |
Primary key, PK Index |
|
|
Foreign key |
Foreign key, FK Index |
|
|
Alternate key (AK) |
AK Index—a unique, non-primary |
|
index |
|
|
Inversion entry (IE) |
IE Index—a non-unique index created |
|
to search table information by a non- |
|
unique value, such as customer last |
|
name. |
|
|
Key group |
Index |
|
|
Business rule |
Trigger or stored procedure |
|
|
Validation rule |
Constraint |
|
|
Relationship |
Relationship implemented using FKs |
|
|
Identifying |
FK is part of child table’s PK (above the |
|
line) |
|
|
Non-Identifying |
FK is NOT part of child table’s PK |
|
(below the line) |
|
|
Subtype |
Denormalized tables |
|
|
Many-to-many |
Associative table |
|
|
8–2 ERwin Methods Guide