DBMS Concepts

DBMS Tutorial Components of DBMS. Applications of DBMS The difference between file system and DBMS. Types of DBMS DBMS Architecture DBMS Schema Three Schema Architecture. DBMS Languages.

DBMS ER Model

ER model: Entity Relationship Diagram (ERD) Components of ER Model. DBMS Generalization, Specialization and Aggregation.

DBMS Relational Model

Codd’s rule of DBMS Relational DBMS concepts Relational Integrity Constraints DBMS keys Convert ER model into Relational model Difference between DBMS and RDBMS Relational Algebra DBMS Joins

DBMS Normalization

Functional Dependency Inference Rules Multivalued Dependency Normalization in DBMS: 1NF, 2NF, 3NF, BCNF and 4NF

DBMS Transaction

What is Transaction? States of transaction ACID Properties in DBMS Concurrent execution and its problems DBMS schedule DBMS Serializability Conflict Serializability View Serializability Deadlock in DBMS Concurrency control Protocols

Difference

Difference between DFD and ERD

Misc

Advantages of DBMS Disadvantages of DBMS Data Models in DBMS Relational Algebra in DBMS Cardinality in DBMS Entity in DBMS Attributes in DBMS Data Independence in DBMS Primary Key in DBMS Foreign Key in DBMS Candidate Key in DBMS Super Key in DBMS Aggregation in DBMS Hashing in DBMS Generalization in DBMS Specialization in DBMS View in DBMS File Organization in DBMS What Is A Cloud Database What Is A Database Levels Of Locking In DBMS What is RDBMS Fragmentation in Distributed DBMS What is Advanced Database Management System Data Abstraction in DBMS Checkpoint In DBMS B Tree in DBMS BCNF in DBMS Advantages of Threaded Binary Tree in DBMS Advantages of Database Management System in DBMS Enforcing Integrity Constraints in DBMS B-Tree Insertion in DBMS B+ Tree in DBMS Advantages of B-Tree in DBMS Types of Data Abstraction in DBMS Levels of Abstraction in DBMS 3- Tier Architecture in DBMS Anomalies in Database Management System Atomicity in Database Management System Characteristics of DBMS DBMS Examples Difference between Relational and Non-Relational Databases Domain Constraints in DBMS Entity and Entity set in DBMS ER Diagram for Banking System in DBMS ER Diagram for Company Database in DBMS ER Diagram for School Management System in DBMS ER Diagram for Student Management System in DBMS ER Diagram for University Database in DBMS ER Diagram of Company Database in DBMS Er Diagram Symbols and Notations in DBMS How to draw ER-Diagram in DBMS Integrity Constraints in DBMS Red-Black Tree Deletion in DBMS Red-Black Tree Properties in DBMS Red-Black Tree Visualization in DBMS Redundancy in Database Management System Secondary Key in DBMS Structure of DBMS 2-Tier Architecture in DBMS Advantages and Disadvantages of Binary Search Tree Closure of Functional Dependency in DBMS Consistency in Database Management System Durability in Database Management System ER Diagram for Bank Management System in DBMS ER Diagram for College Management System in DBMS ER Diagram for Hotel Management System in DBMS ER Diagram for Online Shopping ER Diagram for Railway Reservation System ER Diagram for Student Management System in DBMS Isolation in DBMS Lossless Join and Dependency Preserving Decomposition in DBMS Non-Key Attributes in DBMS Data Security Requirements in DBMS DBMS functions and Components What is Homogeneous Database? DBMS Functions and Components Advantages and Disadvantages of Distributed Database

ER Diagram for Banking System in DBMS

Entity Relationship Diagram

Entity Relationship Diagrams, or ER Diagrams for short, are diagrams that show the relationships among entity sets that are stored in databases. Alternatively said, ER diagrams assist in describing the logical layout of databases. Entities, attributes, and relationships are the three fundamental ideas on which ER diagrams are based. Entities, traits, and relationships are all represented as rectangles, ovals, and diamond shapes in ER diagrams.

At first impression, a flowchart and an ER diagram are similar. The ER Diagram is a particular model, nevertheless, because of the multiple specific symbols and their associated meanings. The entity framework architecture is shown in the ER Diagram. The relationship between the entities that will be recorded in a database is shown in an entity relationship diagram (ER Diagram). The ER Diagram illustrates how a database is structured. With the aid of specialized symbols, it serves as a foundation for defining the connections between database entities. Entities, attributes, and relationships make up the core three elements of an ER diagram.

The relationship between the objects Student and Course is depicted in the diagram below. A student and a course have a many-to-many relationship since different students may choose the same course and a student may choose multiple courses. Stu Id, Stu Name, and Stu Age are characteristics of the student object. Aspects of the course object include Cou ID and Cou Name.

Entity Relationship Diagram of Bank

The ER diagram of Bank is described as follows:

  • Bank has clients.
  • Names, codes, and the main office address are used to identify banks.
  • The branches of banks.
  • Branch no., Branch name, and Branch Address are used to identify branches.
  • Name, customer ID, phone number, and address are used to identify customers.
  • One or more accounts may be open for a customer.
  • The account no., acc type, and amount are used to identify accounts.
  • Customers may apply for loans.
  • The loan id, loan type, and amount are used to identify loans.
  • Loans and accounts are connected to the bank branch.

ER Diagram for Banking System:

ER Diagram for Banking System

This bank ER diagram shows important details about the bank, including things like branches, clients, accounts, and loans. It enables us to comprehend the connections between various elements.

Entities and their Characteristics:

  • Bank entity:Bank Name, Bank Code, and Bank Address are characteristics of a bank entity.
    Code is the Bank Entity's Primary Key.
  • Customer entity:Customer id, Name, Phone Number, and Address are the attributes of a customer entity.
    The primary key for the customer entity is customer_id.
  • Branch entity:Branch id, Name, and Address are the attributes of a branch entity.
    The Branch Entity's Primary Key is Branch id.
  • Account Entity: Account number, Account Type, and Balance are its attributes.
    The primary key for the account entity is account number.
  • Loan Entity: Loan id, Loan Type, and Amount are its attributes.
    The primary key for the loan entity is loan id.

In relationships, and Branch are related one to many.

Branches of the Bank = >1: N

A branch cannot be a member of more than one bank at a time, hence the relationship between a bank and a branch is one to many.

Maintain branch accounts => 1: N

One Account cannot belong to many Branches, whereas one Branch may have numerous Accounts. As a result, the connection between a Branch and an Account is one to many.

Branch Loan Offers =>1: N

One Loan cannot belong to more than one Branch, hence the relationship between a Branch and a Loan is one to many in nature.

Customers' account balance => M: N

The relationship between an account and a customer is one of many to many since one customer may hold multiple accounts in addition to one account being held by one or more customers.

Loan taken out by the customer = >M: N (Assume loan can be jointly held by many Customers).

One customer may have multiple loans, and one loan may be used by one or more customers, hence there is a many-to-many relationship between loans and customers.

Conclusion

Entity Relationship Diagrams, or ER Diagrams for short, are diagrams that show the relationships among entity sets that are stored in databases. Alternatively said, ER diagrams assist in describing the logical layout of databases.

Entities, attributes, and relationships are the three fundamental ideas on which ER diagrams are based. Entities, traits, and relationships are all represented as rectangles, ovals, and diamond shapes in ER diagrams.