Scribd
Upload
54 views5 pages

Database Management System

The document provides an entity relationship diagram for an integrated banking system. The diagram shows the relationships between key entities like customers, employees, accounts (including savings and current accounts), deposits, and withdrawals. The ER diagram helps conceptualize the database design before implementing an extensive database, and shows the logical structure and relationships between tables for entities like employees, customers, accounts, transactions, and more.

Uploaded by

Priyanka Aggarwal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
54 views5 pages

Database Management System

The document provides an entity relationship diagram for an integrated banking system. The diagram shows the relationships between key entities like customers, employees, accounts (including savings and current accounts), deposits, and withdrawals. The ER diagram helps conceptualize the database design before implementing an extensive database, and shows the logical structure and relationships between tables for entities like employees, customers, accounts, transactions, and more.

Uploaded by

Priyanka Aggarwal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

DATABASE MANAGEMENT SYSTEM

INTEGRATED BANKING SYSTEM

Submitted by,

NeerajBangalorekar (6)

PriyankaAggarwal (44)

Kiran Kumar Karrotu (52)

GovindDaga (58)

VishwaRajath (59)
Introduction

An Entity-Relationship (ER) diagram is a specialized graphic that


illustrates the interrelationships between entities in a database.

Entity: An entity is a “thing” or an “object” in the real world that is


distinguishable from all other objects.

Relationship: An association between the instances of one or more


entities that is of interest to the organization

The document provides an Entity Relationship diagram of a basic


banking system. It aims to shows the relationship between the
following entities:
1. Customer
2. Employee
3. Account
a. Savings
b. Current
4. Deposits
5. Withdrawals

It will help us in understanding the conceptual design of the database


before we actually start putting up an extensive database in place. It
helps in facilitating database design by allowing specification of an
enterprise schema that represents the overall logical structure of the
database.
ER DIAGRAM
Tables Used

Employee (Employee ID, First name, Last name, User name,


Password, Address, Phone Number, Branch Code)
Customer (Customer ID, First Name, Last Name, Address, Phone
Number, Account Number, Account ID, Operating Mode,
Photograph, Signature, Branch Code)
Account (Account ID, Description, Account Type, Account Name,
Interest Rate, Balance, Branch Code)
Savings (Account Number, Interest Rate, Minimum Balance,
Account ID)
Current(Account Number, Interest Rate, Minimum Balance, Account
ID)
Deposits (Transaction ID, Date, Mode, Amount Deposited, Bank
Name, Cheque Number, Branch Code, Employee ID)
Withdrawals (Transaction ID, Date, Amount Withdrawn, Employee
ID)
Relationship Schema

Conclusion

An ER Model is intended as a description of real-world entities. The


ER diagram represents the conceptual level of database design. A
relational schema is at the logical level of database design.

For each entity set and for each relationship set in database, there is a
unique table to which we can assign the name of the corresponding
entity set andrelationship set. Each table has multiple columns, each
ofwhich has a unique name. Both the E-R model and therelational-
database model are logical representationsof real-world enterprises.
-------------------------

You might also like