
- •Contents
- •Preface
- •Intended Audience
- •About this Guide
- •Typographical Conventions
- •Related Documentation
- •What’s In This Chapter?
- •Chapter Contents
- •What is 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 Modeling in ERwin
- •What’s In This Chapter?
- •Chapter Contents
- •The Entity-Relationship Diagram
- •Defining Entities and Attributes
- •Logical Relationships
- •Many-to-Many Relationships
- •Validating the Design of the Logical Model
- •Data Model Example
- •What’s In This Chapter?
- •Chapter Contents
- •Understanding Keys
- •Selecting a Primary Key
- •Designating Alternate Key Attributes
- •Inversion Entry Attributes
- •Relationships and Foreign Key Attributes
- •Dependent and Independent Entities
- •Identifying Relationships
- •Non-Identifying Relationships
- •Rolenames
- •What’s In This Chapter?
- •Chapter Contents
- •Naming Entities and Attributes
- •Synonyms, Homonyms and Aliases
- •Entity Definitions
- •Descriptions
- •Business Examples
- •Comments
- •Definition References and Circularity
- •Constructing a Business Glossary
- •Attribute Definitions
- •Rolenames
- •Definitions and Business Rules
- •What’s In This Chapter?
- •Chapter Contents
- •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
- •IDEF1X and IE Subtype Notation
- •When to Create a Subtype Relationship
- •Introduction
- •Chapter Contents
- •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?
- •Conclusions
- •ERwin Support for Normalization
- •First Normal Form Support
- •Second and Third Normal Form Support
- •What’s In This Chapter?
- •Chapter Contents
- •Creating a Physical Model
- •Denormalization
- •Classification of Dependent Entities
- •Glossary of Terms
- •Index
- •Documentation Comments Form

1 |
ERwin Methods Guide |
|
|
Data Modeling Sessions
Creating a data model involves not only construction of the model, but also numerous fact-finding sessions that uncover the data and processes used by a business. Running good sessions, like running good meetings of any kind, depends on a lot of preparation, and “real-time” facilitation techniques. In general, modeling sessions should include the right mix of business and technical experts and should be facilitated. This means that they are scheduled well in advance, carefully planned to cover sets of focused material, and orchestrated in such a way that desired results are achieved.
When possible, it is highly recommended that modeling of function and data be done at the same time. This is because functional models tend to validate a data model and uncover new data requirements. This approach also ensures that the data model supports function requirements. To create both a function and data model in a single modeling session, it is important to include not only a data modeler, but also a process modeler who is responsible for capturing the functions being explored.
Session Roles
Formal, guided sessions, with defined roles for participants and agreed upon procedures and rules, are a must. The following roles seem to work well:
♦The facilitator is the session guide. This person is responsible for arranging the meetings and facilities, providing follow-up documentation, and intervening during sessions, as necessary, to keep them on track and control the scope of the session.
♦The data modeler is responsible for leading the group through the process of developing the model and validating it. The modeler develops the model, in real-time if possible, in front of the group by asking pertinent questions that bring out the important detail,and recording the resulting structure for all to see. It is often possible (although somewhat difficult) for the same individual to play both facilitator and data modeler roles.
♦The data analyst(s) functions as the scribe for the session, and records the definitions of all entities and attributes that make up the model. They can also begin to “package” entities and attributes into subject areas, manageable and meaningful subsets of the complete data model, based on information from the business experts.
12 ∙ Information Systems, Databases, and Models

ERwin Methods Guide |
1 |
|
|
♦The subject matter experts provide the business information needed to construct the model. They are “business” not “systems” people. It is their business that is being analyzed.
♦The manager, either from the “systems” or “business” community, participates in the sessions in his or her assigned role (facilitator, subject matter expert, etc.) but has the additional responsibility of making decisions as needed to keep the process moving. The manager has the responsibility of “breaking ties” but only when absolutely necessary.
Information Systems, Databases, and Models ∙ 13