Logical Data Modeling Training Course – ORA110
This course introduces the principles of relational databases and the use of data modeling for design. It explains how to incorporate business requirements into a logical data model. The components of a logical data model are defined and how to represent this model as an entity relationship diagram. The normalization of data and how to handle complex relationships are also included.
Logical Data Modeling Programming Course – ORA110
Logical Data Modeling Training Course – ORA110 Request a Class Date
This course introduces the principles of relational databases and the use of data modeling for design. It explains how to incorporate business requirements into a logical data model. The
Course ID: ORA110
Duration: 2 days
Audience: This seminar is designed for systems analysts, application developers/analysts, business analysts, project leaders, data, and database administrators.
Topics Covered in Logical Data Modeling Training Course:
Definitions
- Benefits of logical data modeling
- Data modeling vs. physical database design
- Roles involved in data modeling
- Steps in the data modeling process
- Example data model
- Business Requirements
Business statements
- Business definitions
- Policies, goals and strategies
- Business rules
- Gathering business requirements
Entities
- Identifying entities
- Validating entities
- Documenting “instances” of entities
- Distinguishing entities from attributes
- Naming entities
- Starting an Entity/Relationship (E/R) diagram
- Relationships
Identifying significant relationships
- Determining the “cardinality” or “degree” of a relationship
- One-to-one
- One-to-Many
- Many-to-Many
- Determining whether a relationship is optional or mandatory
- Giving a relationship a name
- Documenting the relationships in the E/R diagram
- Walking people through an E/R diagram
- Attributes and Normalization
Defining and categorizing attributes
- Domains and integrity rules
- Unique identifiers/primary keys
- Foreign keys
- Occurrence population
- Normalization: validating the placement of each attribute
- Attribute does not repeat (first normal form)
- Attribute is dependent on its entire UID (second normal form)
- Attribute is dependent only on its UID (third normal form)
- Resolving Many-to-Many Relationships
Real-world examples of many-to-many relationships
- Why many-to-many relationships are broken down into simpler relationships
- Identifying “association” or “intersection” entities
- Documenting the new relationships in the E/R diagram
- Recursive Relationships
Real-world examples of recursive relationships
- Discovering recursive relationships
- Determining whether the relationships are optional or mandatory
- Documenting the new relationships in the E/R diagram
- “Structure” entities: fifth normal form