Introduction to Data Modeling
                     Good Morning & 
Welcome
We'll explore the fundamentals of Data Modeling and the E-R 
Model.
Prepare for clear, actionable insights tailored for both 
technical and non-technical audiences.
Presents by: Shiva Kumar Shah
Introduction to Data 
Modeling
• Introduction to Data Modeling & E-R Model
• Data modeling is the blueprint for designing databases
• It defines how data is stored, organized, and connected
Ensures efficiency, accuracy, and scalability in complex 
sys•temDsifferent types: Hierarchical, Network, Relational
E-R Model is key for conceptual design
• Today’s focus:
• Core concepts and components of the E-R Model
• Why it's important for both developers and non-technical 
stakeholders
What is the E-R 
MThe oE-Rd Meodle?l is a high-level conceptual data model that represents real-world elements as entities and 
models their associations as relationships. Entities are objects like customers or products, while attributes 
define their properties such as names or prices. Relationships describe how entities interact or relate, and 
cardinality specifies the nature of these connections—ranging from one-to-one to many-to-many.
E-R diagrams serve as the visual language for this model, making complex data structures 
understandable at a glance, which is especially useful in early database design phases.
Entities Attributes Relationships
Real-world objects like Details that describe each How entities associate with 
customers, products, or entity, such as a product’s price each other, for example, orders 
employees. or a customer’s ID. placed by customers.
Key Components: Entities 
and Attributes
Entities = Real-world objects
Attributes = Describe details about entities
Strong Entity Weak Entity
Exists independently, e.g., Depends on strong entity, 
Customer. e.g., Order Item.
Attribute Types
• Simple and Composite
• Single-valued and Multi-valued
• Derived Attributes
Key Components: Relationships and 
CRelaatiorndshiipns ilalusltriattey associations between entities, such as a Customer placing an Order. Cardinality 
defines how many instances of one entity relate to another, critical for accurate modeling. These include 
one-to-one (a person has one passport), one-to-many (a customer places multiple orders), many-to-one, 
aPanrdt imcipaantyi-otno -imndaincayt (esst uwdheentthse er narlol loler ds oinm me uinltsiptalen cceosu rosfe asn). entity participate in a relationship, either 
totally or partially. This level of detail captures real-world constraints, ensuring the database reflects true 
business rules.
1 One-to-One (1:1) 2 One-to-Many (1:N) 3 Many-to-Many 
(N:M)
Each entity instance One entity relates to Multiple entities on both 
relates to only one multiple instances in sides relate to each other.
instance in the other set. another set.
E-R Diagram Notations & 
SReyctamnglbes o= lEsntities (things in the database)
Ovals = Attributes (details about entities)
Diamonds = Relationships (how entities are connected)
Underlined ovals = Key attributes (main identifiers)
• Double rectangles = Weak entities (depend on others)
• Lines show connections between all elements
Crow’s foot notation shows how many items are involved (cardinality)
• Makes complex data easy to see and understand quickly
Entity Attribute Relationship Key Attribute
E-R Model vs. Other Data 
DMiffeorednt emoldsels serve different needs:
Hierarchical: Tree-like, but struggles with complex links
Network: More flexible, but harder to manage
Relational: Common today, uses tables but can be less intuitive at first
Object-Oriented: Great for complex data, used in specialized cases
E-R Model stands out for its clear, easy-to-understand design
• Ideal for early planning and stakeholder communication
• Provides a strong, flexible base for building any type of database
Hierarchical Network Relational Object-Oriented
Tree-like, simple but Flexible but complex to Table-based, widely Handles complex data 
limited. manage. used. types.
Advantages of the E-R Model
The E-R model's simplicity makes it accessible for both technical teams and stakeholders, facilitating clearer communication during database 
design. It provides a strong foundation for relational database development, guiding the logical structuring of data.
Its flexibility allows for easy adaptation to changing business needs and integration with other models. This adaptability ensures that evolving 
data relationships and rules can be accommodated without redesigning the entire database.
Clarity Communication
Straightforward visualization fosters understanding. Bridges gap between technical and business teams.
Flexibility Foundation
Adapts well to evolving business requirements. Supports relational database design effectively.
Conclusion: Why Choose 
the E-R Model?
• Combines simplicity and power, making it easy to 
• uCnledaerrlyst caonmd manudn iucsaetes complex relationships, even to 
non-technical stakeholders
• Reduces misunderstandings and design errors early in the 
• pHreolcpes sasvoid costly changes later by aligning the design 
with business needs from the start
• Streamlines development and improves overall database 
planning and documentation
Thank You for Your Attention
& 
joining us today.