Dbms Report

ONLINE BANKING MANAGEMENT SYSTEM
VISVESVARAYA TECHNOLOGICAL UNIVERSITY

BELGAVI
DATABASE MANAGEMENT SYSTEM

LABORATORY MINI-PROJECT REPORT
ON
SUBMITTED BY
RAJAT SHARMA NILESH

1AT17CS059 1AT17CS043
Submitted in partial fulfilment of the requirement for the Degree of Bachelor of

Engineering
In
Computer Science & Engineering
Under the Guidance of

Mr. Rajendra M Mrs. Deeksha Satish
Asst. Professor Visiting Professor
Computer Science and Engineering Department
Atria Institute of Technology
BY: RAJAT SHARMA and NILESH

USN: 1AT17CS059 and 1AT17CS043 Page 1
Atria Institute of Technology

Ananda Nagar, Bengaluru-560024
CERTIFICATE
This is to certify that the project entitled ONLINE BANKING MANAGEMENT SYSTEM
has been successfully completed by
RAJAT SHARMA NILESH

1AT17CS059 1AT17CS043
In partial fulfilment for the data base management system laboratory with mini-project report
[17CSL58] - V semester, B.E. Computer Science during 2019-2020.
Signature of guide 1 Signature of guide 2 Signature of HOD

Prof. Rajendra M Prof .Deeksha Satish Dr.P Aishwarya
EXTERNAL VIVA:
(Names of Internal/External Examiners with Signature & Date)
Examiner 1:
Examiner 2:

DECLARATION
We, RAJAT SHARMA and NILESH, Students of 5th Semester B.E. in Computer Science and
Engineering at Atria Institute of Technology, hereby declare that the project work entitled
“ONLINE BANKING MANAGEMENT SYSTEM” has been carried out by me under the
supervision of Prof. Rajendra M and Prof. Deeksha Satish, Dept. of CS&E, Atria Institute of
Technology and submitted in partial fulfilment of the course requirements for the award of
degree in B.E. in Computer Science and Engineering of Visvesvaraya Technological
University Belgavi during the year 2019-2020. I further declare that the report has not been
submitted to any other university for the award of any other degree.
Place: Bangalore RAJAT SHARMA(1AT17CS059)
Date: NILESH(1AT17CS043)

ACKNOWLEDGEMENT
I have spent my full effort and dedication upon completion of this project, however this
would not been possible and successful without the invaluable Support and Guidance of
Prof. Rajendra M, Prof. Deeksha Satish , Prof. Sathisha G and Prof. Nagesh V.
My sincere gratitude to all my Mentors. I would like to thank beloved Principal Dr. K V
Narayanaswamy for providing a congenial environment and surrounding to work in.
I would also like to thank my HOD Dr. Aishwarya P for giving me this opportunity to do
this project and prove my skills and for continuous support and encouragement. I also thank
to my classmates who every time helped me out and encouraged me for carrying out the
project. I fall short of words to thank my family, who stood beside me while completion of
my project.
RAJAT SHARMA NILESH

1AT17CS059 1AT17CS043

ABSTRACT
Online banking system can be considered as the one of the great tool supporting many
customers as well as banks and financial institutions to make may banking activities through
online. Every day banks need to perform many activities related to users which needs huge
infrastructure with more staff members etc.
But the online banking system allows the banks to perform these activities in a simpler way
without involving the employees for example consider online banking, mobile banking and
ATM banking. But banking system needs to be more secure and reliable because each and
every task performed is related to customer’s money. Especially authentication and validation
of user access is the major task in the banking systems.

TABLE OF CONTENTS
i. Certificate
ii. Declaration
iii. Acknowledgement
iv. Abstract
CHAPTERS
1. Introduction
1.1. Introduction to DBMS………………………………………………………………..7
1.2. Introduction to Online Banking Management System………………………………..8
1.2.1. Project Objective………………………………………………………………8
1.2.2. Project Scope…………………………………………………………………..9
2. Requirement Specifications
2.1. Functional Requirements………………………………………………………….10
2.2. Performance Requirements…………………………………………………………10
2.3. Software Requirements……………………………………………………………10
2.4. Hardware Requirements……………………………………………………………10
3. System Design
3.1. ER Diagram…………………………………………………………………………11
3.2. Normalization………………………………………………………………………12
3.3. User Interface Design………………………………………………………………13
4. Detailed Design
4.1. Database Creation…………………………………………………………………13
4.1.1. Data Definition…………………………………………………………….14
4.2. Stored Procedure…………………………………………………………………14-15
4.3. Triggers…………………………………………………………………………15-16
5. Table and values………………………………………………………16-18
6. Code……………………………………………………………………18-32
7. Output Screens………………………………………………………..33-35
8. Bibliography……………………………………………………………36-37

1. INTRODUCTION
1.1. INTRODUCTION TO DBMS

Database is a collection of related data. DBMS came into existence in 1960 by Charles.
Again in 1960 IBM brought IMS-Information management system. In 1970 Edgor Codd at
IBM came with new database called RDBMS. In 1980 then came SQL Architecture-
Structure Query Language. In 1980 to 1990 there were advances in DBMS e.g. DB2,
ORACLE. A database has the following implicit properties:
❖ A database represents some aspect of the real world, sometimes called the miniworld or
the Universe of Discourse (UoD). Changes to the miniworld are reflected in the database.
❖ A database is a logically coherent collection of data with some inherent meaning. A
random assortment of data cannot correctly be referred to as a database.
❖ A database is designed, built, and populated with data for a specific purpose. It has an
intended group of users and some preconceived applications in which these users are
interested.
In other words, a database has some source from which data is derived, some degree of
interaction with events in the real world, and an audience that is actively interested in its
contents.
Metadata (meta data, or sometimes meta information) is "data about data", of any sort in
any media. An item of metadata may describe a collection of data including multiple content
items and hierarchical levels, for example a database schema. In data processing, metadata is
definitional data that provides information about or documentation of other data managed
within an application or environment. The term should be used with caution as all data is
about something, and is therefore metadata.
A database management system (DBMS) is a collection of programs that enables
users to create and maintain database. The DBMS is a general purpose software system that
facilitates the process of defining, constructing, manipulating and sharing databases among
various users and applications.
Defining a database specifying the database involves specifying the data types, constraints
and structures of the data to be stored in the database. The descriptive information is also
stored in the database in the form database catalogue or dictionary; it is called meta-data.
Manipulating the data includes the querying the database to retrieve the specific data. An
application program accesses the database by sending the queries or requests for data to
DBMS. The important function provided by the DBMS includes protecting the database and
maintain the database.

1.2. INTRODUCTION TO ONLINE BANKING MANAGEMENT

SYSTEM
The project entitled “Online Banking " is a computerized telecommunications device that
provides the customers of a financial institution with access to financial transactions in a
public space without the need for a human clerk or bank teller.
Thousands of banks performs millions of transactions every day and thousands of users
follow the almost the same banking system. As we know that if number of users increases
we need more banks and more staff it means we have to put more money in this system. If we
developed advanced computerized based banking system so there is no need to open new
branches in remote areas or same branch provides services to other banking system e.g ATM
system.
Banking system requires authenticity and validity if a system provides these basic logics that
mean we can develop a new system that authenticate and validate the user and user
can do any type of virtual transaction any time anywhere in minimum amount of time. One of
the most authentic codes for recognition of any person is signature. It always appears on
almost all types of documents, such as property documents, bank cheques, and credit slips,
thus signature has a great importance in our daily life, therefore automatic signature
verification is important in the field of document analysis and processing for which a lot of
work has been done in the past
Online transactions:. An online transaction is the execution of a program that performs an

administrative or real-time function, often by accessing shared data sources, usually on behalf
of an online user (although some transactions are run offline in batch). This transaction
program contains the steps involved in the business transaction. This definition of an online
transaction is important because it makes it clear that there is far more to this topic than
database transactions
1.2.1. OBJECTIVE OF PROJECT

The banking management system will serve us a useful approach to database
and a dialog box to withdraw and deposit the money for the person. It serves us
a helpful server for the users. It serves a easy way to deposit and withdraw the money.
It reduces the time taken by the user to serve money.

1.2.2. PROJECT SCOPE
From an end-user perspective, the Online Banking System Project consists of two
functional elements: Customer transaction module and Employee transaction module.
Customer Transaction Module An enhanced atomized system is developed to maintain
customer transaction. Features includes
Creation of new banking customer
Customer type – Current Account, Savings Account, Fixed Account
Customer Creation form
Existing customer details
Customer Access Form
Each customer login identified by Access Code and Account No.
Banking Main menu option like.
Transaction – Debit, Credit,
Transfer Customer Detail – Modify Details,
Lock Customer.
Freeze/Unfreeze Account
Help – User Manual.
Transaction Summary
Account Closing
Employee Transaction Module An enhanced atomized system is developed to
maintain employee transaction. Features includes
Customer Details
Transaction Report

2. REQUIREMENT SPECIFICATION
2.1. FUNCTIONAL REQUIREMENTS

A functional requirement document defines the functionality of a system or one of its
subsystems. It also depends upon the type of software, expected users and the type of system
where the software is used.
Functional user requirements may be high-level statements of what the system should do but
functional system requirements should also describe clearly about the system services in
detail.
2.2. PERFORMANCE REQUIREMENTS

Performance requirements define how well the system performs certain functions under
specific conditions. Examples are speed of response, throughput, execution time and storage
capacity. The service levels comprising performance requirements are often based on
supporting end-user tasks. Like most quality attributes, performance requirements are key
elements when designing and testing the product.
Performance requirements need to be considered along with other types of quality attributes
(e.g., reliability, robustness, security and usability as well as availability, interoperability,
safety, efficiency and flexibility). Some quality attributes can conflict with one another and
require the business to make tradeoffs. One example is among different types of performance
requirements: High throughput performance (ability to process a large volume of transitions
within a timeframe) can degrade response time. Or, battery life on a hardware device (another
performance requirement) can impact strength of the lighting on a visual display, potentially
degrading usability.
2.3. SOFTWARE REQUIREMETS

VB 6
MS Access
2.4. HARDWARE REQUIREMENTS

Processor: Preferably 2.0 GHz or Greater.
RAM: 512 MB or Greater .

3. SYSTEM DESIGN
3.1. ER DIAGRAM

3.2. NORMALIZATION
A Database is a collection of interrelated data stored with a minimum of redundancy to

serve many applications. The database design is used to group data into a number of
tables and minimizes the artificiality embedded in using separate files. The tables are
organized to:
o Reduced duplication of data.

o Simplify functions like adding, deleting, modifying data etc..,
o Retrieving data
o Clarity and ease of use
o More information at low cost
Normalization
Normalization is built around the concept of normal forms. A relation is said to be in a
particular normal form if it satisfies a certain specified set of constraints on the kind of
functional dependencies that could be associated with the relation. The normal forms are used
to ensure that various types of anomalies and inconsistencies are not introduced into the
database.
First Normal Form:

A relation R is in first normal form if and only if all underlying domains contained atomic
values only.
Second Normal Form:

A relation R is said to be in second normal form if and only if it is in first normal form and
every non-key attribute is fully dependent on the primary key.
Third Normal Form:

A relation R is said to be in third normal form if and only if it is in second normal form and
every non key attribute is non transitively depend on the primary key.

3.3. USER INTERFACE DESIGN
User interface design or UI design generally refers to the visual layout of the elements that a
user might interact with in a website, or technological product. This could be the control
buttons of a radio, or the visual layout of a webpage. User interface designs must not only be
attractive to potential users, but must also be functional and created with users in mind.
User interface design can dramatically affect the usability and user experience of an
application. If a user interface design is too complex or not adapted to targeted users, the user
may not be able to find the information or service they are looking for. In website design, this
can affect conversion rates. The layout of a user interface design should also be clearly set
out for users so that elements can be found in a logical position by the user.
4. DETAILED DESIGN
4.1. DATABASE CREATION

A database is a data structure that stores organized information. Most databases contain
multiple tables, which may each include several different fields. For example, a company
database may include tables for products, employees, and financial records. Each of these
tables would have different fields that are relevant to the information stored in the table.
Nearly all e-commerce sites uses databases to store product inventory and customer
information. These sites use a database management system (or DBMS), such as Microsoft
Access, FileMaker Pro, or MySQL as the "back end" to the website. By storing website data
in a database, the data can be easily searched, sorted, and updated. This flexibility is
important for e-commerce sites and other types of dynamic websites.
Early databases were relatively "flat," which means they were limited to simple rows and
columns, like a spreadsheet. (See also "flat file database"). However, today's relational
databases allow users to access, update, and search information based on the relationship of
data stored in different tables. Relational databases can also run queries that involve multiple
databases. While early databases could only store text or numeric data, modern databases also
let users store other data types such as sound clips, pictures, and videos.

4.1.1. DATA DEFINITION

Data, in the context of databases, refers to all the single items that are stored in a
database, either individually or as a set. Data in a database is primarily stored in database
tables, which are organized into columns that dictate the data types stored therein. So, if
the “Customers” table has a column titled “Telephone Number,” whose data type is
defined as “Number,” then only numerals can be stored in that column.
Data, even in a database, is rarely useful in its raw form. For example, in a banking
application, data is the whole collection of bank account numbers; bank customers’
names, addresses, and ages; bank transactions and so on. Being presented with this mass
of numbers will simply overwhelm the average human -- an individual simply cannot
process it all. However, when data is arranged relationally, it then becomes information,
which is much more useful to users. For example, if the mass of numbers stored in the
banking database above is used to extract the names and addresses of the top 100 clients
by size of deposit, then the data has been used to provide useful information.
4.2. STORED PROCEDURE

A stored procedure (also termed proc, storp, sproc, StoPro, StoredProc, StoreProc, sp,
or SP) is a subroutine available to applications that access a relational database management
system (RDBMS). Such procedures are stored in the database data dictionary.
Uses for stored procedures include data-validation (integrated into the database) or access-
control mechanisms. Furthermore, stored procedures can consolidate and centralize logic that
was originally implemented in applications. To save time and memory, extensive or complex
processing that requires execution of several SQL statements can be saved into stored
procedures, and all applications call the procedures. One can use nested stored procedures by
executing one stored procedure from within another.
Stored procedures may return result sets, i.e., the results of a SELECT statement. Such result
sets can be processed using cursors, by other stored procedures, by associating a result-set
locator, or by applications. Stored procedures may also contain declared variables for
processing data and cursors that allow it to loop through multiple rows in a table. Stored-
procedure flow-control statements typically include IF , WHILE , LOOP , REPEAT ,
and CASE statements, and more. Stored procedures can receive variables, return results or
modify variables and return them, depending on how and where the variable is declared.

Main Parts of a Stored Procedure
Stored procedures can be thought of having three main parts:
Inputs
Store procedure can accept parameter values as inputs. Depending on how the parameters are
defined, modified values can be passed back to the calling program
Execution
Stored procedures can execute SQL statements, utilize conditional logic such as IF THEN or
CASE statements and lopping constructs to perform tasks.
A stored procedure is able to call another stored procedure.
Stored procedure can become very handy as they can manipulate results of SQL queries via
cursors. Cursors allow the procedure to access results row by row. In essence you can use
cursors to loop through a SQL statement’s result. This can slow down database performance,
so be intelligent about your use of cursors!
Outputs
A stored procedure can return a single values such as a number or text value or a result set
(set of rows). Also, as mentioned, depending on how the inputs are defined, changed values
to inputs can be propagated back to the calling procedure.
4.3. TRIGGERS
A trigger is a stored procedure in database which automatically invokes whenever a special

event in the database occurs. For example, a trigger can be invoked when a row is inserted
into a specified table or when certain table columns are being updated.
Syntax:
create trigger [trigger_name]
[before | after]
{insert | update | delete}
on [table_name]
[for each row]
[trigger_body]
5. TABLE AND VALUES
Admin Table:
Id Int(5)
Name Varchar(255)
Gender Char(1)
Date of birth Date
Relationship Varchar(255)
Department Varchar(255)
Address Varchar(255)
Mobile Varchar(11)
Login id Varchar(255)
Password Varchar(32)
Last login Datetime

Customer Table:
Id Int(5)
Name Varchar(255)
Gender Char(1)
Date of birth Date
Nominee Varchar(255)
Account Varchar(255)
Mobile Varchar(11)
Email Varchar(255)
Branch Varchar(255)
Ifsc Varchar(255)
Last login Datetime
Account status Varchar(255)
Staff Table:
Id Int(5)
Name Varchar(255)
Gender Char(1)
Date of birth Date
Department Varchar(255)
Date of joining Date
Mobile Varchar(11)
Email Varchar(255)
Branch Varchar(255)
Last login Datetime
Relationship Varchar(255)
Passbook Table:
Transaction id Int(5)
Transaction date Date
Name Varchar(255)
Branch Varchar(255)
Ifsc Varchar(255)
Credit Int(10)
Debit Int(10)
Amount Float(10,2)
Narration Varchar(255)

ATM Table:
Id Int(10)
Customer name Varchar(255)
Account no. Int(10)
Atm status Varchar(50)
Beneficiary Table:
Id Int(10)
Sender id Int(10)
Sender name Varchar(255)
Receiver id Int(10)
Receiver name Varchar(255)
Status Varchar(15)
Chequebook Table:
Id Int(10)
Customer name Varchar(255)
Account no. Int(10)
Cheque book status Varchar(25)
6. CODE
Staff Login:
<?php
session_start();
if(isset($_SESSION['staff_login']))
header('location:staff_homepage.php');
?>
<!DOCTYPE html>
<html>
<head>
<noscript><meta http-equiv="refresh" content="0;url=no-js.php"></noscript>
<meta charset="UTF-8">
<title>Staff Login - Online Banking</title>
<link rel="stylesheet" href="newcss.css">

</head>

<?php
include 'header.php'; ?>
<div class='content'>
<div class="user_login">
<form action='' method='POST'>
<table align="center">
<tr><td><span class="caption">Staff Login</span></td></tr>
<tr><td colspan="2"><hr></td></tr>
<tr><td>Username:</td></tr>
<tr><td><input type="text" name="uname"></td></tr>
<tr><td>Password:</td></tr>
<tr><td><input type="password" name="pwd"></td></tr>
<tr><td class="button1"><input type="submit" name="submitBtn" value="Log In"
class="button"></td></tr>
</table>
</form>
</div>
</div>
<?php include 'footer.php';

?>
<?php
if(isset($_REQUEST['submitBtn'])){
include '_inc/dbconn.php';
$username=$_REQUEST['uname'];
$password=$_REQUEST['pwd'];
$sql="SELECT email,pwd FROM staff WHERE email='$username' AND

pwd='$password'";
$result=mysql_query($sql) or die(mysql_error());
$rws= mysql_fetch_array($result);
if($rws[0]==$username && $rws[1]==$password){

session_start();
$_SESSION['staff_login']=1;
$_SESSION['staff_id']=$username;
header('location:staff_homepage.php');
}
else
echo "fail";
}
?>
SQL Code:

-- phpMyAdmin SQL Dump

-- version 4.2.7.1
-- http://www.phpmyadmin.net
--
-- Host: 127.0.0.1
-- Generation Time: Jan 11, 2015 at 10:35 AM
-- Server version: 5.6.20
-- PHP Version: 5.5.15
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

SET time_zone = "+00:00";
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT

*/;
/*!40101 SET
@OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION
*/;
/*!40101 SET NAMES utf8 */;
--
-- Database: `bank_db`
--
-- --------------------------------------------------------
--
-- Table structure for table àdmin`
--
DROP TABLE IF EXISTS àdmin`;

CREATE TABLE IF NOT EXISTS àdmin` (
ìd` int(5) NOT NULL,
`name` varchar(255) NOT NULL,
`gender` char(1) NOT NULL,
`dob` date NOT NULL,
`relationship` varchar(255) NOT NULL,
`department` varchar(255) NOT NULL,
àddress` varchar(255) NOT NULL,
`mobile` varchar(11) NOT NULL,
`login_id` varchar(255) NOT NULL,
`pwd` varchar(32) NOT NULL,
`lastlogin` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;
--
-- Dumping data for table àdmin`

--
INSERT INTO àdmin` (ìd`, `name`, `gender`, `dob`, `relationship`, `department`, àddress`,
`mobile`, `login_id`, `pwd`, `lastlogin`) VALUES
(1, 'admin', 'M', '1994-01-01', 'unmarried', 'developer', 'globsyn kolkata', '18003004000',
'admin', 'admin', '0000-00-00 00:00:00');
-- --------------------------------------------------------
--
-- Table structure for table àtm`
--
DROP TABLE IF EXISTS àtm`;

CREATE TABLE IF NOT EXISTS àtm` (
`cust_name` varchar(255) NOT NULL,
àccount_no` int(10) NOT NULL,
àtm_status` varchar(50) NOT NULL
--
-- Dumping data for table àtm`
--
INSERT INTO àtm` (ìd`, `cust_name`, àccount_no`, àtm_status`) VALUES

(15, 'Rajat sharma', 34, 'PENDING');
-- --------------------------------------------------------
--
-- Table structure for table `beneficiary1`
--
DROP TABLE IF EXISTS `beneficiary1`;

CREATE TABLE IF NOT EXISTS `beneficiary1` (
`sender_id` int(10) NOT NULL,
`sender_name` varchar(255) NOT NULL,
`reciever_id` int(10) NOT NULL,
`reciever_name` varchar(255) NOT NULL,
`status` varchar(15) NOT NULL
--
-- Dumping data for table `beneficiary1`
--

INSERT INTO `beneficiary1` (ìd`, `sender_id`, `sender_name`, `reciever_id`,

`reciever_name`, `status`) VALUES
(21, 34, 'Rajat sharma', 35, 'Aditya abrol', 'ACTIVE'),
(22, 34, 'Rajat sharma', 36, 'Anshuman giri', 'ACTIVE'),
(23, 36, 'Anshuman giri', 34, 'Rajat sharma', 'ACTIVE'),
(24, 35, 'Aditya abrol', 34, 'Rajat sharma', 'ACTIVE'),
(25, 34, 'Rajat sharma', 38, 'Somya', 'PENDING');
-- --------------------------------------------------------
--
-- Table structure for table `cheque_book`
--
DROP TABLE IF EXISTS `cheque_book`;

CREATE TABLE IF NOT EXISTS `cheque_book` (
`cust_name` varchar(255) NOT NULL,
àccount_no` int(10) NOT NULL,
`cheque_book_status` varchar(25) NOT NULL
--
-- Dumping data for table `cheque_book`
--
INSERT INTO `cheque_book` (ìd`, `cust_name`, àccount_no`, `cheque_book_status`)

VALUES
(8, 'Rajat sharma', 34, 'PENDING');
-- --------------------------------------------------------
--
-- Table structure for table `customer`
--
DROP TABLE IF EXISTS `customer`;

CREATE TABLE IF NOT EXISTS `customer` (
`nominee` varchar(255) NOT NULL,
àccount` varchar(255) NOT NULL,
èmail` varchar(255) NOT NULL,
`password` varchar(255) NOT NULL,
`branch` varchar(255) NOT NULL,

ìfsc` varchar(255) NOT NULL,

`lastlogin` datetime NOT NULL,
àccstatus` varchar(255) NOT NULL
--
-- Dumping data for table `customer`
--
INSERT INTO `customer` (ìd`, `name`, `gender`, `dob`, `nominee`, àccount`, àddress`,
`mobile`, èmail`, `password`, `branch`, ìfsc`, `lastlogin`, àccstatus`) VALUES
(34, 'Rajat sharma', 'M', '1993-12-30', 'ramu', 'savings', 'agapara', '9999955555',
'rajatind98@gmail.com', '28a1b310b43643306f560bb161ff6b67f763c576', 'KOLKATA',
'K421A', '2015-01-11 10:29:30', 'ACTIVE'),
(35, 'Aditya abrol', 'M', '1990-12-26', 'ramu', 'savings', 'agarpara', '9999955556',
'aditya@gmail.com', '28a1b310b43643306f560bb161ff6b67f763c576', 'DELHI', 'D30AC',
'2015-01-11 10:11:07', 'ACTIVE'),
(36, 'Anshuman giri', 'M', '1993-06-26', 'ramu', 'savings', 'sodepur', '9999955556',
'anshuman@gmail.com', '28a1b310b43643306f560bb161ff6b67f763c576', 'BANGALORE',
'B6A9E', '0000-00-00 00:00:00', 'ACTIVE'),
(37, 'Nilesh', 'M', '0000-00-00', 'ramu', 'savings', 'durgapur', '9999955556',
'nilesh@gmail.com', '28a1b310b43643306f560bb161ff6b67f763c576', 'DELHI', 'D30AC',
'2015-01-11 10:18:57', 'ACTIVE'),
(38, 'Somya', 'F', '1990-12-26', 'ramu', 'savings', 'agarpara', '9999955556',
'somya@gmail.com', '28a1b310b43643306f560bb161ff6b67f763c576', 'KOLKATA',
'K421A', '0000-00-00 00:00:00', 'ACTIVE'),
(39, 'Prakash kumar', 'M', '2015-01-14', 'ramu', 'savings', 'agarpara', '9804381248',
'prakash@gmail.com', '28a1b310b43643306f560bb161ff6b67f763c576', 'DELHI', 'D30AC',
'2015-01-11 10:09:36', 'ACTIVE'),
(40, 'Ashar nawab', 'M', '1996-02-18', 'aditya', 'savings', 'agarpara', '8956231245',
'ashar@gmail.com', '28a1b310b43643306f560bb161ff6b67f763c576', 'DELHI', 'D30AC',
'2015-01-11 09:42:43', 'ACTIVE'),
(41, 'Ritesh kumar', 'M', '1993-12-26', 'ramu', 'savings', 'sodepur', '8956231245',
'ritesh@gmail.com', 'b638866443ed874cd5a9449a090cb8dce66e4a3a', 'KOLKATA',
'K421A', '2015-01-11 10:27:48', 'ACTIVE');
-- --------------------------------------------------------
--
-- Table structure for table `passbook34`
--
DROP TABLE IF EXISTS `passbook34`;

CREATE TABLE IF NOT EXISTS `passbook34` (
`transactionid` int(5) NOT NULL,
`transactiondate` date DEFAULT NULL,
`name` varchar(255) DEFAULT NULL,
`branch` varchar(255) DEFAULT NULL,
ìfsc` varchar(255) DEFAULT NULL,

`credit` int(10) DEFAULT NULL,

`debit` int(10) DEFAULT NULL,
àmount` float(10,2) DEFAULT NULL,
`narration` varchar(255) NOT NULL
--
-- Dumping data for table `passbook34`
--
INSERT INTO `passbook34` (`transactionid`, `transactiondate`, `name`, `branch`, ìfsc`,

`credit`, `debit`, àmount`, `narration`) VALUES
(1, '2015-01-08', 'Rajat sharma', 'KOLKATA', 'K421A', 13000, 0, 13000.00, 'Account Open'),
(9, '2015-01-09', 'Rajat sharma', 'KOLKATA', 'K421A', 0, 500, 12500.00, 'TO Aditya abrol'),
(10, '2015-01-10', 'Rajat sharma', 'KOLKATA', 'K421A', 100, 0, 12600.00, 'BY Aditya
abrol'),
(11, '2015-01-10', 'Rajat sharma', 'KOLKATA', 'K421A', 2593, 0, 15193.00, 'BY Aditya
abrol');
-- --------------------------------------------------------
--
--

--
--

(1, '2015-01-09', 'Aditya abrol', 'DELHI', 'D30AC', 10002, 0, 10002.00, 'Account Open'),
(7, '2015-01-09', 'Aditya abrol', 'DELHI', 'D30AC', 500, 0, 10502.00, 'BY Rajat sharma'),
(8, '2015-01-10', 'Aditya abrol', 'DELHI', 'D30AC', 0, 100, 10402.00, 'TO Rajat sharma'),
(9, '2015-01-10', 'Aditya abrol', 'DELHI', 'D30AC', 0, 2593, 7809.00, 'TO Rajat sharma');

-- --------------------------------------------------------
--
--

--
--

(1, '2015-01-09', 'Anshuman giri', 'BANGALORE', 'B6A9E', 95621, 0, 95621.00, 'Account
Open');
-- --------------------------------------------------------
--
--

--

--

(1, '2015-01-09', 'Nilesh', 'DELHI', 'D30AC', 9000, 0, 9000.00, 'Account Open');
-- --------------------------------------------------------
--
--

`narration` varchar(255) DEFAULT NULL
--
--

(1, '2015-01-09', 'Somya', 'KOLKATA', 'K421A', 10000, 0, 10000.00, 'Account Open');
-- --------------------------------------------------------
--
--



--
--

(1, '2015-01-10', 'Prakash kumar', 'DELHI', 'D30AC', 1000, 0, 1000.00, 'Account Open');
-- --------------------------------------------------------
--
--

--
--

(1, '2015-01-11', 'Ashar nawab', 'DELHI', 'D30AC', 1000, 0, 1000.00, 'Account Open');
-- --------------------------------------------------------
--
--



--
--

(1, '2015-01-11', 'Ritesh kumar', 'KOLKATA', 'K421A', 1000, 0, 1000.00, 'Account Open');
-- --------------------------------------------------------
--
-- Table structure for table `staff`
--
DROP TABLE IF EXISTS `staff`;

CREATE TABLE IF NOT EXISTS `staff` (
`relationship` varchar(255) NOT NULL,
`department` varchar(255) NOT NULL,
`doj` date NOT NULL,
èmail` varchar(255) NOT NULL,
`pwd` varchar(32) NOT NULL,
`lastlogin` datetime NOT NULL
--
-- Dumping data for table `staff`
--
INSERT INTO `staff` (ìd`, `name`, `dob`, `relationship`, `department`, `doj`, àddress`,
`mobile`, èmail`, `pwd`, `gender`, `lastlogin`) VALUES
(1, 'sunil', '1990-05-05', 'married', 'revenue', '1999-11-11', 'kestopur12', '8892212466',
'sunil@gmail.com', 'kul', 'M', '2015-01-11 10:29:48'),
(2, 'akash', '1998-08-21', 'unmarried', 'revenue', '2013-08-03', 'kolkata', '9635722546',
'akash@gmail.com', 'aka', 'M', '2015-01-10 21:22:59'),

(4, 'shivam', '1989-05-31', 'married', 'revenue', '2015-01-04', 'bhagalpur13', '8755058486',

'shivam@gmail.com', 'shi', 'M', '0000-00-00 00:00:00'),
(5, 'sharma', '1980-04-21', 'married', 'revenue', '1991-01-01', 'khidirpur', '9876543210',
'sharma@gmail.com', 'sha', 'M', '0000-00-00 00:00:00');
--
-- Indexes for dumped tables
--
--
-- Indexes for table àdmin`
--
ALTER TABLE àdmin`
ADD PRIMARY KEY (ìd`), ADD UNIQUE KEY èmail` (`login_id`);
--
-- Indexes for table àtm`
--
ALTER TABLE àtm`
ADD PRIMARY KEY (ìd`);
--
-- Indexes for table `beneficiary1`
--
ALTER TABLE `beneficiary1`
--
-- Indexes for table `cheque_book`
--
ALTER TABLE `cheque_book`
--
-- Indexes for table `customer`
--
ALTER TABLE `customer`
ADD PRIMARY KEY (ìd`), ADD UNIQUE KEY èmail` (èmail`);
--
-- Indexes for table `passbook34`
--
ALTER TABLE `passbook34`
ADD PRIMARY KEY (`transactionid`);
--
--

--
--
--
--
--
--
--
--
--
--
--
--
--
-- Indexes for table `staff`
--
ALTER TABLE `staff`
ADD PRIMARY KEY (ìd`), ADD UNIQUE KEY èmail` (èmail`);
--
-- AUTO_INCREMENT for dumped tables
--
--

-- AUTO_INCREMENT for table àdmin`

--
ALTER TABLE àdmin`
MODIFY ìd` int(5) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=2;
--
-- AUTO_INCREMENT for table àtm`
--
ALTER TABLE àtm`
--
-- AUTO_INCREMENT for table `beneficiary1`
--
ALTER TABLE `beneficiary1`
--
-- AUTO_INCREMENT for table `cheque_book`
--
ALTER TABLE `cheque_book`
--
-- AUTO_INCREMENT for table `customer`
--
ALTER TABLE `customer`
--
-- AUTO_INCREMENT for table `passbook34`
--
MODIFY `transactionid` int(5) NOT NULL
AUTO_INCREMENT,AUTO_INCREMENT=12;
--
--
--
--
--
--
--


--
--
--
--
--
--
--
--
-- AUTO_INCREMENT for table `staff`
--
ALTER TABLE `staff`
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

7. OUTPUT SCREENS
Admin page
Description: This is the screenshot showing where the admin can login onto to the
Online bank database and can have access to the Users and Staff members.
User login page

Description: This is the screenshot showing where the Users login themselves onto
the Bank database and can view their status.
User homepage
Description: This is the screenshot showing a user’s homepage.
STAFF HOMEPAGE
Description: This is the screenshot showing a staff’s homepage.

ACTIVE CUSTOMERS
Description: This is the screenshot showing information of each customers having

their account in the bank.
TABLES USED
Description: This is the screenshot showing all tables used in the database.

8. BIBLIOGRAPHY
Electronic Documents
E-books
[1] L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, 2nd ed.
Reading, MA: Addison Wesley, 2003. [E-book] Available: Safari e-book.
Article in Online Encyclopedia

[2] D. Ince, “Acoustic coupler,” in A Dictionary of the Internet. Oxford University Press,
[online document], 2001. Available: Oxford Reference Online,
http://www.oxfordreference.com [Accessed: May 24, 2007].
Journal Article Abstract (accessed from online database)

[1] M. T. Kimour and D. Meslati, “Deriving objects from use cases in real-time embedded
systems,” Information and Software Technology, vol. 47, no. 8, p. 533, June 2005.
[Abstract]. Ava ilable: ProQuest, http://www.umi.com/proquest/. [Accessed November 12,
2007].
Journal Article in Scholarly Journal (published free of charge on the Internet)

[2] A. Altun, “Understanding hypertext in the context of reading on the web: Language
learners’ experience,” Current Issues in Education, vol. 6, no. 12, July, 2005. [Online serial].
Available: http://cie.ed.asu.edu/volume6/number12/. [Accessed Dec. 2, 2007].
Newspaper Article from the Internet

[3] C. Wilson-Clark, “Computers ranked as key literacy,” The Atlanta Journal Constitution,
para. 3, March 29, 2007. [Online], Available: http://www.thewest.com.au. [Accessed Sept.
18, 2007].
Internet Documents
Professional Internet Site
[1] European Telecommunications Standards Institute, “Digital Video Broadcasting (DVB):
Implementation guide for DVB terrestrial services; transmission aspects,” European
Telecommunications Standards Institute, ETSI-TR-101, 2007. [Online]. Available:
http://www.etsi.org. [Accessed: Nov. 12, 2007].
Journal Articles
Article in Journal (paginated by annual volume)
[8] K. A. Nelson, R. J. Davis, D. R. Lutz, and W. Smith, “Optical generation of tunable
ultrasonic waves,” Journal of Applied Physics, vol. 53, no. 2, Feb., pp. 1144-1149, 2002.
Books
Single Author
[1] W. K. Chen, Linear Networks and Systems. Belmont, CA: Wadsworth Press, 2003.
Edited Book

[2] J. L. Spudich and B. H. Satir, Eds., Sensory Receptors and Signal Transduction. New
York: Wiley-Liss, 2001.
Selection in an Edited Book
[3] E. D. Lipson and B. D. Horwitz, “Photosensory reception and transduction,” in Sensory
Receptors and Signal Transduction, J. L. Spudich and B. H. Satir, Eds. New York: Wiley-
Liss, 2001, pp-1-64.
Three or More Authors
[4] R. Hayes, G. Pisano, and S. Wheelwright, Operations, Strategy, and Technical
Knowledge. Hoboken, NJ: Wiley, 2007.
Manual
[6] Bell Telephone Laboratories Technical Staff, Transmission System for Communication,
Bell Telephone Lab, 2005.
Technical Report
[8] K. E. Elliott and C. M. Greene, “A local adaptive protocol,” Argonne National
Laboratory, Argonne, France, Tech. Report. 916-1010-BB, 7 Apr. 2007.



Dbms Report

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dbms Report

Uploaded by

Copyright:

Available Formats

ONLINE BANKING MANAGEMENT SYSTEM

VISVESVARAYA TECHNOLOGICAL UNIVERSITY

DATABASE MANAGEMENT SYSTEM

RAJAT SHARMA NILESH

Submitted in partial fulfilment of the requirement for the Degree of Bachelor of

Under the Guidance of

BY: RAJAT SHARMA and NILESH

Atria Institute of Technology

RAJAT SHARMA NILESH

Signature of guide 1 Signature of guide 2 Signature of HOD

BY: RAJAT SHARMA and NILESH

Place: Bangalore RAJAT SHARMA(1AT17CS059)

BY: RAJAT SHARMA and NILESH

RAJAT SHARMA NILESH

BY: RAJAT SHARMA and NILESH

BY: RAJAT SHARMA and NILESH

BY: RAJAT SHARMA and NILESH

1.1. INTRODUCTION TO DBMS

BY: RAJAT SHARMA and NILESH

1.2. INTRODUCTION TO ONLINE BANKING MANAGEMENT

Online transactions:. An online transaction is the execution of a program that performs an

1.2.1. OBJECTIVE OF PROJECT

BY: RAJAT SHARMA and NILESH

1.2.2. PROJECT SCOPE

BY: RAJAT SHARMA and NILESH

2.1. FUNCTIONAL REQUIREMENTS

2.2. PERFORMANCE REQUIREMENTS

2.3. SOFTWARE REQUIREMETS

2.4. HARDWARE REQUIREMENTS

BY: RAJAT SHARMA and NILESH

BY: RAJAT SHARMA and NILESH

A Database is a collection of interrelated data stored with a minimum of redundancy to

o Reduced duplication of data.

First Normal Form:

Second Normal Form:

Third Normal Form:

BY: RAJAT SHARMA and NILESH

3.3. USER INTERFACE DESIGN

4.1. DATABASE CREATION

BY: RAJAT SHARMA and NILESH

4.1.1. DATA DEFINITION

4.2. STORED PROCEDURE

BY: RAJAT SHARMA and NILESH

Main Parts of a Stored Procedure

Stored procedures can be thought of having three main parts:

A trigger is a stored procedure in database which automatically invokes whenever a special

5. TABLE AND VALUES

BY: RAJAT SHARMA and NILESH

BY: RAJAT SHARMA and NILESH

<link rel="stylesheet" href="newcss.css">

BY: RAJAT SHARMA and NILESH

<?php include 'footer.php';

$sql="SELECT email,pwd FROM staff WHERE email='$username' AND

if($rws[0]==$username && $rws[1]==$password){

BY: RAJAT SHARMA and NILESH

-- phpMyAdmin SQL Dump

SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT

DROP TABLE IF EXISTS `admin`;

BY: RAJAT SHARMA and NILESH

DROP TABLE IF EXISTS `atm`;

INSERT INTO àtm` (ìd`, `cust_name`, àccount_no`, àtm_status`) VALUES