• Skip to main content
  • Skip to primary sidebar
  • Skip to secondary sidebar
  • Skip to footer

Computer Notes

Library
    • Computer Fundamental
    • Computer Memory
    • DBMS Tutorial
    • Operating System
    • Computer Networking
    • C Programming
    • C++ Programming
    • Java Programming
    • C# Programming
    • SQL Tutorial
    • Management Tutorial
    • Computer Graphics
    • Compiler Design
    • Style Sheet
    • JavaScript Tutorial
    • Html Tutorial
    • Wordpress Tutorial
    • Python Tutorial
    • PHP Tutorial
    • JSP Tutorial
    • AngularJS Tutorial
    • Data Structures
    • E Commerce Tutorial
    • Visual Basic
    • Structs2 Tutorial
    • Digital Electronics
    • Internet Terms
    • Servlet Tutorial
    • Software Engineering
    • Interviews Questions
    • Basic Terms
    • Troubleshooting
Menu

Header Right

Home » Fundamental » database » What are the Problems with E-R Model?
Next →
← Prev

What are the Problems with E-R Model?

By Dinesh Thakur

The E-R model can result problems due to limitations in the way the entities are related in the relational databases. These problems are called connection traps. These problems often occur due to a misinterpretation of the meaning of certain relationships.

Two main types of connection traps are called fan traps and chasm traps.

 Fan Trap. It occurs when a model represents a relationship between entity types, but pathway between certain entity occurrences is ambiguous.

Chasm Trap. It occurs when a model suggests the existence of a relationship between entity types, but pathway does not exist between certain entity occurrences.

Now, we will discuss the each trap in detail address)

We’ll be covering the following topics in this tutorial:

  • Fan Trap
  • Chasm Trap

Fan Trap

A fan trap occurs when one to many relationships fan out from a single entity.

For example: Consider a database of Department, Site and Staff, where one site can contain number of department, but a department is situated only at a single site. There are multiple staff members working at a single site and a staff member can work from a single site. The above case is represented in e-r diagram shown.E-R diagram with Fan Trap problem

The problem of above e-r diagram is that, which staff works in a particular department remain answered. The solution is to restructure the original E-R model to’ represent the correct association as shown.

Solution of Fan Trap with restructuring the e-r diagram

In other words the two entities should have a direct relationship between them to provide the necessary information.

There is one another way to solve the problem of e-r diagram of figure, by introducing direct relationship between DEPT and STAFF as shown in figure.

Solution of Fan Trap with introduction of new relationship

Another example: Let us consider another case, where one branch contains multiple staff members and cars, which are represented.

E-R diagram with Fan Trap problems

The problem of above E-R diagram is that, it is unable to tell which member of staff uses a particular, which is represented. It is not possible tell which member of staff uses’ car SH34.

Instances with Fan Trap problem

The solution is to shown the relationship between STAFF and CAR as shown.

Solution of Fan Trap with the introduction of new relationship

With this relationship the fan rap is resolved and now it is possible to tell car SH34 is used by S1500 as shown in figure. It means it is now possible to tell which car is used by which staff.

Instances after removal of Fan Trap problem

Chasm Trap

As discussed earlier, a chasm trap occurs when a model suggests the existence of a relationship between entity types, but the pathway does not exist between certain entity occurrences.

It occurs where there is a relationship with partial participation, which forms part of the pathway between entities that are related.

For example: Let us consider a database where, a single branch is allocated many staff who handles the management of properties for rent. Not all staff members handle the property and not all property is managed by a member of staff. The above case is represented in the e-r diagram.

E-R diagram with chasm Trap ProblemNow, the above e-r diagram is not able to represent what properties are available at a branch. The partial participation of Staff and Property in the SP relation means that some properties cannot be associated with a branch office through a member of staff.

We need to add the missing relationship which is called BP between the Branch and the Property entities as shown.

Solution of Chasm Trap with the introduction of new relationship

Another example: Consider another case, where a branch has multiple cars but a car can be associated with a single branch. The car is handles by a single staff and a staff can use only a single cat. Some of staff members have no car available for their use. The above case is represented in E-R diagram with appropriate connectivity and cardinality.

E-R diagram with chasm Trap ProblemsThe problem of the above E-R diagram is that, it is not possible tell in which branch staff member S0003 works at as shown.                              Instances with Chasm Trap problem

It means the above e-r diagram is not able to represent the relationship between the BRANCH and STAFF due the partial participation of CAR and STAFF entities. We need to add the missing relationship which is called BS between the Branch and STAFF entities as shown.

Solution of Chasm Trap with the introduction of new relationships

With this relationship the Chasm trap resolved and now it is possible to represent to which branch each member of staff works at, as for our example of staff S003 as shown.

Instances after removal of Chasm Trap problem

You’ll also like:

  1. What is ER-Model?Advantages and Disadvantages of E-R Model.
  2. Explain Classical Life Cycle Model or linear sequential model
  3. Incremental Model or iterative enhancement model in software engineering
  4. What is build and fix model or ad hoc model? and Explaini its Advantages and Disadvantages
  5. Problems in Implementing MIS
Next →
← Prev
Like/Subscribe us for latest updates     

About Dinesh Thakur
Dinesh ThakurDinesh Thakur holds an B.C.A, MCDBA, MCSD certifications. Dinesh authors the hugely popular Computer Notes blog. Where he writes how-to guides around Computer fundamental , computer software, Computer programming, and web apps.

Dinesh Thakur is a Freelance Writer who helps different clients from all over the globe. Dinesh has written over 500+ blogs, 30+ eBooks, and 10000+ Posts for all types of clients.


For any type of query or something that you think is missing, please feel free to Contact us.


Primary Sidebar

DBMS

Database Management System

    • DBMS - Home
    • DBMS - Definition
    • DBMS - What is
    • DBMS - Entity Sets
    • DBMS - Components
    • DBMS - Languages
    • DBMS - Normalization
    • DBMS - Data Models
    • DBMS - Processing System
    • DBMS - Advantages
    • DBMS - ER-Model
    • DBMS - Functional Dependence
    • DBMS - Relational Model
    • DBMS - Architecture
    • DBMS - Network Model
    • DBMS - Approach
    • DBMS - Data Independence
    • DBMS - Relational Schema
    • DBMS - Instance
    • DBMS - Functions and Service
    • DBMS - Server
    • DBMS - DBA
    • DBMS - Instance & Schemas
    • DBMS - System Type
    • DBMS - DDL, DML and DCL
    • DBMS - Users
    • DBMS - Model
    • DBMS - System Structure
    • DBMS - Role of DBA
    • DBMS - Metadata
    • DBMS - ER-Diagram
    • DBMS - E-R Model Problems
    • DBMS - DBMS Vs.RDBMS
    • DBMS - Basic Construction of E-R
    • DBMS - E-R Notation
    • DBMS - Database View
    • DBMS - Concurrency Control
    • DBMS - Schema
    • DBMS - Procedure for Access
    • DBMS - Object
    • DBMS - dBase
    • DBMS - Relational Algebra
    • DBMS - Deadlock
    • DBMS - Relational Database
    • DBMS - Query
    • DBMS - Schema

DBMS Normal Forms

    • Database - CODD’S Rules
    • Database - 1NF
    • Database - 2NF
    • Database - 3NF
    • Database - 4NF
    • Database - 5NF
    • Database - BCNF

Advance Database

    • Database - File Organization
    • Database - Type Lock
    • Database - Transaction
    • Database - Key Type
    • Database - Relational Algebra
    • Database - Components
    • Database - Deadlock Detect
    • Database - Design Methodology
    • Database - Relational Operators
    • Database - Relational Calculus
    • Database - Lock Granularity
    • Database - Deadlocks Handling
    • Database - Concurrent Control
    • Database - Denormalization
    • Database - Starvation
    • Database - OODB
    • Database - Data Warehouse
    • Database - Fragmentation
    • Database - Data Replication
    • Database - Distributed
    • Database - Transparences
    • Database - ORDBMSS
    • Database - Data Mining
    • Database - Security
    • Database - DBTG
    • Database - OLAP
    • Database - Integrity
    • Database - Data Encryption
    • Database - Recover
    • Database - Data Protection

Some Other Advance Articls

  • Adv of Distributed DBMS
  • Homogeneous and Heterogeneous
  • Causes for Database Failure
  • DBMS Architecture
  • Features for Any DBMS
  • OLTP Systems Vs Data Warehousing
  • Data Warehousing Architecture

Other Links

  • DBMS - PDF Version

Footer

Basic Course

  • Computer Fundamental
  • Computer Networking
  • Operating System
  • Database System
  • Computer Graphics
  • Management System
  • Software Engineering
  • Digital Electronics
  • Electronic Commerce
  • Compiler Design
  • Troubleshooting

Programming

  • Java Programming
  • Structured Query (SQL)
  • C Programming
  • C++ Programming
  • Visual Basic
  • Data Structures
  • Struts 2
  • Java Servlet
  • C# Programming
  • Basic Terms
  • Interviews

World Wide Web

  • Internet
  • Java Script
  • HTML Language
  • Cascading Style Sheet
  • Java Server Pages
  • Wordpress
  • PHP
  • Python Tutorial
  • AngularJS
  • Troubleshooting

 About Us |  Contact Us |  FAQ

Dinesh Thakur is a Technology Columinist and founder of Computer Notes.

Copyright © 2023. All Rights Reserved.