0% found this document useful (0 votes)
23 views9 pages

DEMAND

Copyright
© © All Rights Reserved
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
0% found this document useful (0 votes)
23 views9 pages

DEMAND

Copyright
© © All Rights Reserved
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/ 9

Bank Management system-

NAME: Sayandeep Ghosh

ROLL NO.: 32201222068

STREAM: BCA [batch-1]

SUBJECT CODE: BCAC401


SUBJECT-NAME: DBMS

COLLEGE: Asansol Engineering College

CA-2
Abstract: The main aim of Bank Management Mini DBMS project is to keep
record of customer transactions in the bank. We aim to demonstrate the
use of create, read, update and delete MySQL operations through this
project. Firstly, employee registration is done in the concern bank branch.
Branch employee creates customer account in the bank, then customer can
credit amount, debit amount and check balance.Customer can even use
different services like insurance, loan, bill payments etc.

Modules:

Bank Management Mini DBMS Project contains 4 modules:

1. Account Holder: As the name suggests, a record of customer details.


2. Transaction: Transactions to be made by the customer (credit
amount, debit etc).
3. Services: Additional services that customer may want like (insurance,
loan etc.).
4. Branch/Employee : Manager/Employee details of the concern bank.

SOFTWARE REQUIREMENTS:

• Operating system : Windows XP/7/10.

• Language : Java ( Install JDK 8 version)

• IDE : Netbeans 8.2 / Eclipse

• Database : MYSQL (Install XAMPP)

Technologies used:

• JavaFX

• Mysql
ER-Diagram
MySQL code:

Create database bank


CREATE TABLE `BranchTable` (
`Id` INT NOT NULL AUTO_INCREMENT,
`Name` VARCHAR(120) NOT NULL,
`BCode` VARCHAR(15) NOT NULL,
`Address` VARCHAR(200) NOT NULL,
PRIMARY KEY (`Id`));
CREATE TABLE `EmployeeTable` (
`Id` INT NOT NULL AUTO_INCREMENT,
`Name` VARCHAR(50) NOT NULL,
`Branch` VARCHAR(50) NOT NULL,
PRIMARY KEY (`Id`)) ;
CREATE TABLE `AccountTable` (
`Id` INT NOT NULL AUTO_INCREMENT,
`Account_Number` VARCHAR(15) NOT NULL,
`Account_Type` VARCHAR(15) NOT NULL,
`BCode` VARCHAR(15) NOT NULL,
`Name` VARCHAR(50) NOT NULL,
`Gender` VARCHAR(10) NOT NULL,
`DOB` Date,
`Address` VARCHAR(50) NOT NULL,
`Aadhar` VARCHAR(12) NOT NULL,
`Balance` double NOT NULL,
PRIMARY KEY (`Id`)) ;
CREATE TABLE TransactionTable(
`Id` INT NOT NULL AUTO_INCREMENT,
`Date` Date NOT NULL,
`Account_Num` Varchar(15),
`Transaction_Type` Varchar(15),
`Amount` double,
PRIMARY KEY (`Id`)) ;
CREATE TABLE ServiceTable(
`Date` Date NOT NULL,
`Account_Num` Varchar(15),
`ServiceName` Varchar(100),
`Description` Varchar(200),
`Amount` double,
`TransactionId` INT NOT NULL,
INDEX par_ind (TransactionId),
CONSTRAINT fk_tranTable FOREIGN KEY (TransactionId)
REFERENCES TransactionTable (Id)
ON DELETE CASCADE
ON UPDATE CASCADE
) ENGINE=INNODB;
SET FOREIGN_KEY_CHECKS = 0;
truncate tableName;
SET FOREIGN_KEY_CHECKS = 1;

Bank.sql
-- phpMyAdmin SQL Dump
-- version 4.8.1
-- https://www.phpmyadmin.net/
-- Host: 127.0.0.1
-- Generation Time: Sep 06, 2018 at 08:58 AM
-- Server version: 10.1.33-MariaDB
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";
-- Database: `bank`
-- --------------------------------------------------------
-- Table structure for table `accounttable`
CREATE TABLE `accounttable` (
`Id` int(11) NOT NULL,
`Account_Number` varchar(15) NOT NULL,
`Account_Type` varchar(15) NOT NULL,
`BCode` varchar(15) NOT NULL,
`Name` varchar(50) NOT NULL,
`Gender` varchar(10) NOT NULL,
`DOB` date DEFAULT NULL,
`Address` varchar(50) NOT NULL,
`Aadhar` varchar(12) NOT NULL,
`Balance` double NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- Dumping data for table `accounttable`
INSERT INTO `accounttable` (`Id`, `Account_Number`, `Account_Type`, `BCode`, `Name`,
`Gender`, `DOB`, `Address`, `Aadhar`, `Balance`) VALUES
(1, 'SBI23432310001', 'Savings', 'SBI234323', 'chandan', 'M', '2018-09-06', 'xyz xyz',
'234432234', 20500);
-- --------------------------------------------------------
-- Table structure for table `branchtable`
CREATE TABLE `branchtable` (
`Id` int(11) NOT NULL,
`Name` varchar(120) NOT NULL,
`BCode` varchar(15) NOT NULL,
`Address` varchar(200) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- Dumping data for table `branchtable`
INSERT INTO `branchtable` (`Id`, `Name`, `BCode`, `Address`) VALUES
(1, 'newjersy', 'SBI234323', 'xyz');
-- --------------------------------------------------------
-- Table structure for table `employeetable`
CREATE TABLE `employeetable` (
`Id` int(11) NOT NULL,
`Name` varchar(50) NOT NULL,
`Branch` varchar(50) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- Dumping data for table `employeetable`
INSERT INTO `employeetable` (`Id`, `Name`, `Branch`) VALUES
(1, 'arun', 'SBI234323');
-- --------------------------------------------------------
-- Table structure for table `servicetable`
CREATE TABLE `servicetable` (
`Date` date NOT NULL,
`Account_Num` varchar(15) DEFAULT NULL,
`ServiceName` varchar(100) DEFAULT NULL,
`Description` varchar(200) DEFAULT NULL,
`Amount` double DEFAULT NULL,
`TransactionId` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- Dumping data for table `servicetable`
INSERT INTO `servicetable` (`Date`, `Account_Num`, `ServiceName`, `Description`,
`Amount`, `TransactionId`) VALUES
('2018-09-06', 'SBI23432310001', 'online banking', 'done', 500, 2);
-- --------------------------------------------------------
-- Table structure for table `transactiontable`
CREATE TABLE `transactiontable` (
`Id` int(11) NOT NULL,
`Date` date NOT NULL,
`Account_Num` varchar(15) DEFAULT NULL,
`Transaction_Type` varchar(15) DEFAULT NULL,
`Amount` double DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- Dumping data for table `transactiontable`
INSERT INTO `transactiontable` (`Id`, `Date`, `Account_Num`, `Transaction_Type`,
`Amount`) VALUES
(1, '2018-09-06', 'SBI23432310001', 'Credit', 21000),
(2, '2018-09-06', 'SBI23432310001', 'Debit', 500);
-- Indexes for dumped tables
-- Indexes for table `accounttable`
ALTER TABLE `accounttable`
ADD PRIMARY KEY (`Id`);
-- Indexes for table `branchtable`
ALTER TABLE `branchtable`
ADD PRIMARY KEY (`Id`);
-- Indexes for table `employeetable`
ALTER TABLE `employeetable`
ADD PRIMARY KEY (`Id`);
-- Indexes for table `servicetable`
ALTER TABLE `servicetable`
ADD KEY `par_ind` (`TransactionId`);
-- Indexes for table `transactiontable`
ALTER TABLE `transactiontable`
ADD PRIMARY KEY (`Id`);
-- AUTO_INCREMENT for dumped tables
-- AUTO_INCREMENT for table `accounttable`
ALTER TABLE `accounttable`
MODIFY `Id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
-- AUTO_INCREMENT for table `branchtable`
ALTER TABLE `branchtable`
MODIFY `Id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
-- AUTO_INCREMENT for table `employeetable`
ALTER TABLE `employeetable`
MODIFY `Id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
-- AUTO_INCREMENT for table `transactiontable`
ALTER TABLE `transactiontable`
MODIFY `Id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
-- Constraints for dumped tables
-- Constraints for table `servicetable`
ALTER TABLE `servicetable`
ADD CONSTRAINT `fk_tranTable` FOREIGN KEY (`TransactionId`) REFERENCES
`transactiontable` (`Id`) ON DELETE CASCADE ON UPDATE CASCADE;
COMMIT;

THANK
YOU!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy