MR - PROJECT Editing

VISVESVARAYA TECHNOLOGICAL UNIVERSITY
“Jnana Sangama”, Belgaum-590014, Karnataka.
A Mini Project Report On
“BANK MANAGEMENT SYSTEM”

Submitted in the partial fulfillment of the requirements for the award of the Degree of
BACHELOR OF ENGINEERING
IN
INFORMATION SCIENCE AND ENGINEERING
Submitted by
MONICA P 1EW20IS048
RANJITHA A N 1EW20IS060
Under the Guidance of

Mrs. ANJANA H.S
Assistant Professor,
Dept of ISE, EWIT
DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING
EAST WEST INSTITUTE OF TECHNOLOGY

BENGALURU - 560 091
2022-2023
EAST WEST INSTITUTE OF TECHNOLOGY
Sy. No.63,Off.Magadi Road, Vishwaneedam Post, Bengaluru -
560091 (Affiliated To Visvesvaraya Technological
University,Belgavi)
DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING
CERTIFICATE
This is to certify that the mini project work entitled “BANK MANAGEMENT SYSTEM”
presented by MONICA P (1EW20IS048) and RANJITHA A N (1EW20IS060), bonafide students
of EAST WEST INSTITUTE OF TECHNOLOGY, Bengaluru in partial fulfillment for the award
of Bachelor of Engineering in Information Science and Engineering of Visvesvaraya
Technological University, Belagavi during the year 2022-2023. It is certified that all
corrections/suggestions indicated for Internal Assessment have been incorporated in the report
deposited in the departmental library. The mini project report has been approved as it satisfies the
academic requirements in respect of project work prescribed for the said degree.
------------------------- ------------------------------ -----------------------------

Signature of Guide Signature of HOD Signature of Principal
Mrs. ANJANA H S Dr. Suresh M B Dr. K Channakeshavalu
Assistant Professor Prof & Head Principal
Dept. of ISE Dept. of ISE EWIT, Bangalore
EWIT, Bangalore EWIT, Bangalore
External Viva
Name of the Examiners Signature with date
1.
2.
ABSTRACT
The bank management system project is a program that keeps track of a client’s bank account. This
project demonstrates the operation of a banking account system and covers the essential functions of bank
management software. It develops a project for resolving a customer’s financial applications in a banking
environment to meet the needs of an end banking user by providing multiple ways to complete banking
chores.
Additionally, this project is to provide additional features to the user’s workspace that are not
available in a traditional banking project. The project’s bank management system is built on cutting-edge
technologies. This project’s main goal is to create software for a bank account management system. The
main aim of this project is to develop software for bank account management system. This project has
been developed to carry out the processes easily and quickly, which is not possible with the manuals
systems, which are overcome by this software.
This project developed using PHP, CSS, JS language and MYSQL use for database connection.
Creating and managing requirement is a challenge of IT, systems and product development projects or
indeed for any activity where you have to manage a contractual relationship. Organization need to
effectively define and manage requirements to ensure they are meeting needs of the customer.
The project analyses the system requirements and then comes up with system specifications. The
system is then designed tin accordance with specifications to satisfy the requirements. The system design
is then implemented with MYSQL, PHP, CSS, and JS.
The system is designed as an interactive and content management system. The content management
system deals with data entry, validation confirm and updating whiles the interactive system deals with
system interaction with the administration and uses. Thus, above features of this project will save
transaction time and therefore increase the efficiency of the system.
i
ACKNOWLEDGEMENT
Any achievement, be it scholastic or otherwise does not depend solely on the individual efforts but
on the guidance, encouragement and cooperation of intellectuals, elders and friends. A number of
personalities, in their own capacities have helped us in carrying out this project work. We would like
to take this opportunity to thank them all.
First and foremost, we would like to thank Dr. K Channakeshavalu, Principal, EWIT, for his
moral support towards completing our mini project work.
We would like to thank, Dr. Suresh M B, Professor and Head of Department of ISE, EWIT, for
his valuable suggestions and expert advice.
We deeply express our sincere gratitude to our guide Mrs. ANJANA H S Assistant Professor,
Department of ISE, EWIT, for her able guidance throughout the mini project work and guiding us
to organize the report in a systematic manner.
We thank our Parents, and all the faculty members of Department of Information science &
Engineering for their constant support and encouragement.
Last, but not the least, we would like to thank our peers and friends who provided us with valuable
suggestions to improve our mini project.
MONICA P 1EW20IS048
RANJITHA AN 1EW20IS060
ii
LIST OF CONTENTS
CONTENTS PAGE NO.
ABSTRACT i
ACKNOWLEDGEMENT ii
CHAPTER 1: INTRODUCTION 1-3

1.1 Overview 1
1.2 Features of the project 2
1.3 Advantages 3
1.4 Disadvantages 3
CHAPTER 2: PROJECT DESIGN 4-5
2.1 Project Proposal 4
2.2 Project Description 4
2.3 Project Objectives
2.4 Project Scope 5
CHAPTER 3: REQUIREMENT SPECIFICATIONS 6-7
3.1 Software requirements 6
3.2 Hardware requirements 6
CHAPTER 4: SYSTEM DESIGN 8-11
4.1 Description of tables 8
4.2 ER Diagram 9
4.3 Schema Diagram 11
CHAPTER 5: IMPLEMENTATION 12-18
5.1 System development life cycle 12
5.2 Front end selection 14
5.3 Database language selection 18
5.4 Backend language selection 18
CHAPTER 6: TESTING 19-23
6.1 Levels of testing 19
CHAPTER 7: SNAPSHOTS 24-31
CONCLUSION
REFERENCES
iii
LIST OF FIGURES
Table No Description Page No.

6.1.1 Test cases for integration testing 21
6.1.2 Test cases for Input-Output 22

7.1 Home page 24
7.2 User Login Page 24
7.3 User Home Page 25
7.4 User Account Information Page 25
7.5 User Account Statement 26
7.6 Fund Transfer Page 26
7.7 Error in Funds Transfer Page 27
7.8 Successful Transfer 27
7.9 Transaction Successful 28
7.10 New Transfer Page 29
7.11 Notification Page 29
7.12 Help Card 30
7.13 Writing message into help desk 30
7.14 Manager Login 31
7.15 All Accounts 31
7.16 Staff Accounts 31
7.17 Add New Account 32
7.18 Feedback from Account Holder 32
7.19 Logout 33
7.20 Back to Home Page 33
iv
Bank Management System 2022-2023
CHAPTER 1
INTRODUCTION
1.1 Overview
Bank account system involves maintaining of account related information. This requires greater
accuracy, speed that is why the proposed system is the computerization of the existing system. The
computerization system does the job monitoring the record in easy and effective manner as stated
below:
 Efficiently handles customer, account related data.

 Monitor transaction and makes related information.
 Keeps records of customer account detail and other information.
 Generates reports.
Account system involved maintaining data related different customer and his transaction. This
required greater accuracy, speed that is why the proposed system is the computerization of the
existing system. The computerized system does the job of the monitoring the information easy
and effective manner.
1.2 Features of the project
Admin/Management side
Login Page
The page where the system users will submit their system credentials to access and manage the
data of the Bank Management System.
Home Page
The page where the system user will be redirected by default after logging into the system.
Manager Page
The page where the manager can login check the transactions send notice to the customers
Add New Account

The page where we can create a new account of the customer in account.
DEPT OF ISE, EWIT 1

Customer Side
Home Page
The page where the system user will be redirected by default after logging into the system.
User Login
Here user can login using his/her email and password and do transactions.
Transactions
Here the user can transfer the money or deposit the money.
Account Statements
In this page the customer can take his account statements that how much transactions he has done.
Feedback
Here the user can give feedback to the services provided by bank on the service improvisation etc.
1.3 Advantages
 Simplicity of Use
 Reduction in Cost of Operation
 24/7 Availability
 Multi-banking Features
 Secure Transactions
 Support for Multiple Accounts
 Simple And Quick Transactions
DEPT OF ISE, EWIT 2

1.4 Disadvantages
 Tech-Related Service Disruptions
 Concerns about Identity Theft and Security
 Deposit Restrictions
 Faster is Not Always More Convenient
 Limited service Scope
 Possibility of overspending
DEPT OF ISE, EWIT 3

CHAPTER 2
PROJECT DESIGN
DEPT OF ISE, EWIT 4

2.1 Project Proposal

The Bank Management System project proposal states the solution and the problems faced by bank
management. It should contain the project Objectives, Scope, and Description.
2.2 Project Description

The Bank Management System is a web based tool that is used to reimburse financial institutions for
services rendered to the Bureau of the Fiscal Service. In addition, Bank management system provides
services like deposit, withdraw, transfer amount from one person to another person and to check
balance.
2.3 Project Objectives
The goal of the bank management system project is to create an organic and optimal software of
interaction between the various banking components. This is to maximize the profit of the banking
mechanism. The implementation of competent bank management procedures is significantly responsible
for the successful optimization of the bank’s productivity and activities.
The project’s main goal is to create an online banking system for banks. All banking work is done
Manually in the current system. To withdraw or deposit money, the user must go to the bank.
Today, it is also hard to find account information for people who have accounts in the banking
system.
2.4 Project Scope
Depending on the bank’s policies, bank personnel and/or customers can utilize the banking
management system. It can be utilized by multiple employees at the same time if they have the
necessary permissions. Any web browser with a graphical interface can be used to access it.
CHAPTER 3
REQUIREMENT SPECIFICATIONS
DEPT OF ISE, EWIT 5

This section describes the software and hardware requirements of the system. Software
Requirements Specification (SRS) is a fundamental document, which forms the foundation of the
software development process. SRS not only lists the requirements of a system but also has
description of its major features. These recommendations extend the IEEE standards. The
recommendations would form the basis for providing clear visibility of the product to be
developed serving as baseline for execution of a contract between client and the developer.
3.1 Software requirements
 Tools used : Microsoft Visual Studio code
 Backend Design : PHP, JavaScript
 Front end design : HTML, CSS, JS
 Database : MySQL
 Operating System : Windows 8/9/10

 Software used : XAMP
3.2 Hardware Requirements
The most common set of requirements defined by any operating system or software application is
the physical computer resources, also known as hardware, A hardware requirements list is often
accompanied by a hardware compatibility list (HCL), especially in case of operating systems. An
HCL lists tested, compatible, and sometimes incompatible hardware devices for a particular
operating system or application. The following sub-sections discuss the various aspects of
hardware requirements.
Processor : Intel i5
Hard disk : 500GB
Ram : 8GB
Hard disk : 500GB
DEPT OF ISE, EWIT 6

DEPT OF ISE, EWIT 7

CHAPTER – 4
SYSTEM DESIGN
4.1 DESCRIPTION OF TABLES
TABLE NAME: branch TABLE NAME : FEEDBACK
FIELD NAME DATA TYPE FIELD NAME DATA TYPE

branchId Int (11) feedbackID Int (30)
branchNo Varchar (111) message text
branchName Varchar (111)
userId double
date timestamp
TABLE NAME: LOGIN TABLE NAME: NOTICE
FIELD NAME DATA TYPE FIELD NAME DATA TYPE

ID Int (30) ID Int (30)
email Text userId Varchar (111)
password Varchar (111) Notice Text
type Varchar (111) date Timestamp
date Timestamp
DEPT OF ISE, EWIT 8

TABLE NAME: OTHERACCOUNTS
FIELD NAME DATA TYPE

ID Int (30)
accountNo Varchar (111)
bankName Varchar (111)
holderName Varchar (111)
balance Varchar (111)
date Timestamp
TABLE NAME: TRANSACTION

transactionId Int (11)
Action Varchar (111)
beneId Varchar (111)
other Varchar (111)
userId Int (111)
date Timestamp
TABLE NAME: USERACCOUNTS
id Int (11)
email Text
password Text
name Varchar (111)
balance Varchar (111)
Aadhar Varchar (111)
Number Varchar (111)
City Varchar (111)
Address Varchar (111)
Source Varchar (111)
Accounts Varchar (111)
Branch Varchar (111)
Account type Varchar (111)
DEPT OF ISE, EWIT 9

date Varchar (111)
4.2 DATABASE DESIGN
 E-R DIAGRAM OF BANK MANAGEMENT

The entity-relationship model describes inter-related things of interest in a specific domain of
knowledge. The figure 4.1 displays the ER diagram of BANK MANAGEMENT SYSTEM. An entity-
relationship model is composed of entity types and specific relationships that can exist between
instances of those entity types.
DEPT OF ISE, EWIT 10

Figure 4.2: Representing E-R diagram

4.3 SCHEMA DIAGRAM OF BANK MANAGEMENT SYSTEM :
Schema diagram formulates all the constraints that are to be applied on the data. A database
schema defines and the relationship among them. It contains a descriptive detail of the database, which
can be depicted by means of schema diagram. A schema diagram is a diagram which contains entities
and the attributes that will define that schema. A schema diagram only shows us the database design.
Schema can be a single table or it can have more than one table which is related. The schema represents
the relation between these tables.
Figure 4.3: Representing Schema Diagram

CHAPTER 5
IMPLEMENTATION
Implementation is the phase of the project where detailed design is converted into a working system.
Thus, this is the crucial stage in accomplishing successful system which is efficient. Implementation
includes methodical planning, examination of constraints, assessment of methods and platform
selection. The term implementation has different meanings ranging from the conversation of a basic
application to a complete replacement of a computer system. The procedures however, are virtually the
same. Implementation includes all those activities that take place to convert from old system to new.
The new system may be totally new replacing an existing manual or automated system or it may be
major modification to an existing system. Proper implementation is essential to provide a reliable
system to meet organization requirement.
5.1 System Development life cycle
Systems Development Life Cycle (SDLC) is the most common process adopted to develop a project
and not surprisingly, this project is following this model too. To be precise, a waterfall model is
being applied. Waterfall model is a sequential model process where the input of a phase actually
results from the previous phase.
There are five phases in this model and the first phase is the planning stage. The planning stage
determines the objectives of the project and whether the project should be given the green light to
proceed. This is where the proposal submission comes into picture. After obtaining the approval, the
next phase is analysis. Gathering and analyzing the system and user requirements is essential for
entry to the design step.
With the user requirements gathering completed, there is a need to prepare the resources for the
project. Be it software or hardware components, careful consideration and selection is to be taken
care at this stage. The decision on the appropriate resources to be used is further elaborated under the
subsections below. The next step is to design the system and database structure.
Results from the analysis and preparation that were concluded from the previous stage are put
into action. With the user requirements in mind, the flow of the system is planned and the user
interface is designed to suit their easy navigation needs. In addition, the number of tables, attributes,

primary and unique keys of the database is listed.
After completing the design, actual coding begins. Databases are created and codes are written. Some
of the codes required amendments and improvement to it so these are being developed at this fourth
stage of the waterfall model. With the development completed, testing will begin. The codes and
database are tested to ensure the results obtained are as intended. More time is spent on both
development and testing stages because it is inevitable to have errors and issues and buffer time is
allocated for troubleshooting.

5.2 Front end selection
HTML
Hypertext Markup Language (HTML) is the standard markup language for documents designed to
be displayed in a web browser. It can be assisted by technologies such as Cascading Style Sheets
(CSS) and scripting languages such as JavaScript.
Web browsers receive HTML documents from a web server or from local storage and render the
documents into multimedia web pages. HTML describes the structure of a web page semantically
and originally included cues for the appearance of the document. HTML elements are the building
blocks of HTML pages.
With HTML constructs, images and other objects such as interactive forms may be embedded into
the rendered page. HTML provides a means to create structured documents by denoting structural
semantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML
elements are delineated by tags, written using angle brackets.
Tags such as <img /> and <input /> directly introduce content into the page. Other tags such as
<p> surround and provide information about document text and may include other tags as sub-
elements. Browsers do not display the HTML tags, but use them to interpret the content of the
page.
HTML can embed programs written in a scripting language such as JavaScript, which affects the
behavior and content of web pages. Inclusion of CSS defines the look and layout of content. The
World Wide Web Consortium (W3C), former maintainer of the HTML and current maintainer of
the CSS standards, has encouraged the use of CSS over explicit presentational HTML since 1997.
HTML documents imply a structure of nested HTML elements. These are indicated in the document
by HTML tags, enclosed in angle brackets thus:

In the simple, general case, the extent of an element is indicated by a pair of tags: a "start tag" <p> and
"end tag" </p> . The text content of the element, if any, is placed between these tags.
HTML stands for Hyper Text Markup Language. It is the standard markup language for creating
Web pages, this describes the structure of a Web page and consists of a series of elements.
A Simple HTML Document
<!DOCTYPE html>
<html>
<head>
<title>Page Title</title>
</head>
<body>
<h1>My First Heading</h1>
<p>My first paragraph</p>
</body>
</html>
Example Explained
● The <!DOCTYPE html> declaration defines that this document is an HTML5
document
● The <html> element is the root element of an HTML page
● The <head> element contains meta information about the HTML page
● The <title> element specifies a title for the HTML page (which is shown in the
browser's title bar or in the page's tab)
● The <body> element defines the document's body, and is a container for all the visible
contents, such as headings, paragraphs, images, hyperlinks, tables, lists, etc.
● The <h1> element defines a large heading
● The <p> element defines a paragraph
What is an HTML Element?

An HTML element is defined by a start tag, some content, and an end tag: <tagname>Content goes
here...</tagname>The HTML element is everything from the start tag to the end tag:
● <h1>My First Heading</h1>
● <p>My first paragraph</p>

CSS
CSS stands for Cascading Style Sheets. It describes how HTML elements are to be displayed on
screen, paper, or in other media. CSS saves a lot of work. It can control the layout of multiple web
pages all at once. External stylesheets are stored in CSS files. Cascading Style Sheets (CSS) is a
style sheet language used for describing the presentation of a document written in a markup
language like HTML.CSS is a cornerstone technology of the World Wide Web, alongside HTML
and JavaScript.CSS is designed to enable the separation of presentation and content, including
layout, colors, and fonts. This separation can improve content accessibility, provide more
flexibility and control in the specification of presentation characteristics, enable multiple web
pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce
complexity and repetition in the structural content.
CSS information can be provided from various sources. These sources can be the web browser,
the user and the author. The information from the author can be further classified into inline,
media type, importance, selector specificity, rule order, inheritance and property definition. CSS
style information can be in a separate document or it can be embedded into an HTML document.
Multiple style sheets can be imported. Different styles can be applied depending on the output
device being used; for example, the screen version can be quite different from the printed version,
so that authors can tailor the presentation appropriately for each medium.
The style sheet with the highest priority controls the content display. Declarations not set in the
highest priority source are passed on to a source of lower priority, such as the user agent style.
The process is called cascading. One of the goals of CSS is to allow users greater control over
presentation. Someone who finds red italic headings difficult to read may apply a different style
sheet. Depending on the browser and the web site, a user may choose from various style sheets
provided by the designers, or may remove all added styles and view the site using the browser's
default styling, or may override just the red italic heading style without altering other attributes
Why Use CSS?

 CSS is used to define styles for your web pages, including the design, layout and variations in
display for different devices and screen sizes.

Javascript
JavaScript is a high-level, interpreted scripting language that conforms to the ECMAScript

specification. JavaScript has curly-bracket syntax, dynamic typing, prototype-based object
orientation, and first-class functions. Alongside HTML and CSS, JavaScript is one of the core
technologies of the World Wide Web. JavaScript enables interactive web pages and is an essential
part of web applications. The vast majority of websites use it, and major web browsers have a
dedicated JavaScript engine to execute it. As a multi-paradigm language, JavaScript supports
event-driven, functional, and imperative (including object-oriented and prototype based)
programming styles. It has APIs for working with text, arrays, dates, regular expressions, and the
DOM, but the language itself does not include any I/O, such as networking, storage, or graphics
facilities.
It relies upon the host environment in which it is embedded to provide these features.
Initially only implemented client-side in web browsers, JavaScript engines are now embedded in
many other types of host software, including server-side in web servers and databases, and in non-
web programs such as word processors and PDF software, and in runtime environments that make
JavaScript available for writing mobile and desktop applications, including desktop widgets. The
terms Vanilla JavaScript and Vanilla JS refer to JavaScript not extended by any frameworks or
additional libraries. Scripts written in Vanilla JS are plain JavaScript code. Google’s Chrome
extensions, Opera's extensions, Apple's Safari 5 extensions, Apple's Dashboard Widgets,
Microsoft's Gadgets, Yahoo! Widgets, Google Desktop Gadgets, and Serence Klipfolio are
implemented using JavaScript.
I. Advantages of JavaScript
Speed: Client-side JavaScript is very fast because it can be run immediately within the client-
side browser. Unless outside resources are required, JavaScript is unhindered by network
calls to a backend server.
• Simplicity: JavaScript is relatively simple to learn and implement.
• Popularity: JavaScript is used everywhere on the web.
• Interoperability: JavaScript plays nicely with other languages and can be used in a huge

variety of applications.

5.3 Database language selection
● SQL is a standard language for accessing and manipulating databases.

● What is SQL?
SQL stands for Structured Query Language and lets you access and manipulate databases. It became a standard
of the American National Standards Institute (ANSI) in 1986, and of the International Organization for
Standardization (ISO) in 1987.
● What Can SQL do?
SQL can execute queries against a database and can retrieve data from a database, can insert records
in a database, can update records in a database, can delete records from a database, can create new
databases, can create new tables in a database, can create stored procedures in a database, can create
views in a database, also can set permissions on tables, procedures, and views.
5.4 Backend Language Selection (PHP)
PHP is one of the good backend development technologies that provide robust CMS opportunities. In
2015, PHP was updated to its 7th version. The well-organized documentation of PHP backend makes it
peculiar among other backend development languages. PHP features are:
 Simplicity
Compared to other scripting languages PHP is very simple and easy to use. The official PHP resource
covers comprehensive information about all the features of the language. The provided ready-made PHP
solutions, in their turn, simplify the coding process. Thanks to the intuitive logic and syntax of PHP,
developers who have at least some experience in coding write their first code in PHP just having a few
days of practice.
 Interpretation
PHP is an interpreted language. For example, there is no need for compilation. The most widely used
PHP implementation is powered by the Zend Engine and known simply as PHP. Zend Engine compiles
PHP source into a format that it can execute, thus the Zend engine works as an interpreter.
 Speed
PHP is faster and it restarts the application every time the web request starts. However, as on every
request PHP sets up then tears down the entire application, sharing resources may be difficult.
 Open Source
No kind of payment is required for using PHP. This language is possible to download and use for free
PHP code is run on any platform, including Linux, Mac OS X, Unix, Windows.
 Case Sensitivity
At the time of variable declaration, PHP is a case sensitive scripting language. All the keywords (such
as if, else, while, echo, and many more), classes, user-defined functions, as well as functions are NOT .

CHAPTER 6
TESTING
The testing phase is an important part of software development. It is the process of finding errors
and missing operations and also completing verifications to determine whether the objectives and
requirements are satisfied. Software testing is carried out in three steps.
The first step includes unit testing where in each module is tested to provide its correctness, to
determine any missing operations and to verify whether the objectives have been met. Errors are
noted down and corrected immediately. Unit testing is the important and major part of the project.
So, errors are rectified easily in particular modules and program quality is increased. In this project,
entire system is divided into several modules.
Second step include integration testing. If we need not be the case that software whose modules
when run individually and showing perfect result with also show perfect result as whole. The
individual modules are clipped under this major module and tested again and verified the results. A
module can have inadvertent, adverse effect on any other on the global data structure causing
serious problems. Levels in testing:
 Unit testing
 Integration testing
 Validation testing
6.1 Levels of Testing
Unit Testing
Unit testing is a method by which individual units of source code, sets of one or more computer
program modules together with associated control data, usage procedures, and operating procedures,
are tested to determine if they are fit for use. Intuitively, one can view a unit as the smallest testable
part of an application. In object-oriented programming a unit is often an entire interface, such as a
class, but could be an individual method. For unit testing first we adopted the code testing strategy,
which examined the logic of program. During the development process itself all the syntax errors
etc. got rooted out. For this developed test case that result in executing every instruction in the
program or module i.e., every path through program was tested. Test cases are data chosen at

random to check every possible branch after all the loops.
User Input
User will input all the data from using a web browser.
Error Handling
In this system, we have tried to handle all the errors that occurred while running the application. the
common errors we saw were reading a tuple with an attribute set to null and database connection
getting lost. For Testing we used Top-Down design a decomposition process which focuses as the
flow of control, at latter strategies concern itself with code production. The first step is to study the
overall aspects of the tasks at hand and break it into a number of independent modules. The second
step is to break one of these modules further into independent sub modules
Integration Testing
Data can be lost across an interface, one module can have an adverse effect on the other sub
function, when combined may not produce the desired functions. Integrated testing is the systematic
testing to uncover the errors with an interface. This testing is done with simple data and developed
system has run successfully with this simple data. The need for integrated system is to find the
overall system performance

Steps to perform integration testing:
Step 1: Create a Test Plan
Step 2: Create Test Cases and Test Data
Step 3: Once the components have been integrated execute the test cases Step
4: Fix the bugs if any and re test the code
Step 5: Repeat the test cycle until the components have been successfully integrated
Table 6.1.1 Test cases for integration testing
Name of the Test Integration testing

Test plan To check whether the system works
properly when all the modules are
integrated.
Test Data Sample credential fill up

System testing
Ultimately, software is included with other system components and the set of system
validation and integration tests are performed. System testing is a series of different tests whose
main aim is to fully exercise the computer-based system. Although each test has a different role all
work should verify that all system elements are properly integrated and formed allocated functions.
Table 6.1.2 Test cases for Input-Output
Name of the Test System Testing

Item being tested Over all functioning of GUI with all
functions properly linked.

Sample Input Sample text files
Expected Output
The admin and user module work as
expected
Actual Output Application reacts to user inputs in
expected manner.
Remarks Successful
Validation Testing
At the culmination of black box testing, software is completely assembled is as a package.

Interfacing errors have been uncovered and the correct and final series of tests, i.e., validation tests
begin. Validation test is defined with a simple definition that validation succeeds when the software
function in a manner that can be reasonably accepted by the customer.
The process of evaluating software during the development process or at the end of the
development process to determine whether it satisfies specified business requirements. Validation
Testing ensures that the product actually meets the client's needs. It can also be defined as to
demonstrate that the product fulfils its intended use when deployed on appropriate environment
Software validation checks that the software product satisfies or fits the intended use (high-level
checking), i.e., the software meets the user requirements, not as specification artifacts or as needs of
those who will operate the software only; but, as the needs of all the stakeholders (such as users,
operators, administrators, managers, investors, etc.). There are two ways to perform software validation:
internal and external.

Output Testing
After performing validation testing, the next step is output testing of the proposed system.
Since the system cannot be useful if it does not produce the required output. Asking the user about
the format in which the system is required tests the output displayed or generated by the system is
required tests the output displayed or generated by the system under consideration. The output
format on the screen is found to be corrected as the format was designated in the system has
according to the user needs. As for the hard copy the output comes according to the specification
requested by the user. The output testing does not result in any correction in the system.
Test data and Output:

Taking various kind soft data plays a vital role in system testing. After preparing the test data
system under study is tested using the test data. While testing, errors are again uncovered and
corrected by using the above steps and corrections are also noted for future use.
User acceptance Testing:

User acceptance testing of the system is the key factor for the success of the system. A system
under consideration is tested for user acceptance by constantly keeping in touch with the
prospective system at the time of development and making change whenever required. This is done
with regard to the input screen design and output screen design.
GUI Testing:
GUI testing is use to ensure the visual clarity of the system, flexibility of the system, user
friendliness of the system. The various components which are to be tested are:
 Relative layout
 Various Links and Buttons
GUI Testing is a software testing type that checks the Graphical User Interface of the Software. The
purpose of Graphical User Interface (GUI) Testing is to ensure the functionalities of software
application work as per specifications by checking screens and controls like menus, buttons, icons, etc.

CHAPTER 7 SNAPSHOTS
Figure: 7.1 Home page
 Here there are two logins one is user and the other one is manager
Figure:7.2 User login page
 Here user can login to bank by using his email and password

Figure 7.3: User Home Page

 Where user can see his account summary, transfer money, check notification and
contact bank for any issues
Fig:7.4 User Account Information

 Here user can se his account information like account no, branch, branch code account
type and account created.

Figure:7.5 User Account Statement

 Here user can see the number of transactions made by him.
Figure: 7.6 Fund Transfer Page

 Here user can send/transfer the money to other account

Figure:7.7 Error in funds transfer page

 When the user enter a wrong account number
Figure:7.8 Successful Transfer

 Here the user had successful transaction by entering correct account credentials
and had a successful transaction.

Figure: 7.9 Transaction Successful

 After the user transfers the money bank notifies the status of the transaction
Figure:7.10 New Transfer page

 Here the user can initiate the new transaction

Figure:7.11 Notification Page

 Here the customer gets notification from the page
Figure:7.12 Help Card

 Here the user can write his issues faced during transaction to bank

Figure:7.13 Writing message into help desk

 Here the user is writing the issues into the help card
MANAGER SIDE SNAPSHOTS
Figure:7.14 Manager Login

 Here only manager can login by using his email and password

Figure:7.15 All Accounts

 Here manager can see all the accounts that are active in the bank
Figure:7.16 Staff Account

 Here all the accounts of staff working in the bank can be created and displayed

Figure:7.17 Add New Account

 Here manager can add new account of the customer
Figure: 7.18 Feedback From Account Holder

 Here the manager can see the feedback given by the Customers

Figure: 7.19 Logout

 Manager can logout from the manager login
Figure:7.20 Home Page

 After logging out from the manager login he will come back to home page of the
bank


-
CONCLUSION
 The project include following main modules:

 · Login of the User and Manager
 · Registration of user.
 · Accounting description.
 · User profile information.
 · Report generation.
 · Brief description of the all modules.
Login of the Art Gallery -applicant and administrator
 This module is considered with login of new user and administrator. Every user must enter his
some details about itself for login the home page and after submitted he can Cart and ship Art
online. The administrator can also login from this module. He can insert, delete or update the
user login name and password. this module check the authenticity of the person accessing the
project. The main objective behind this module is to provide security to the project so that access
is restricted to the authorized users.
 Input is taken as login and password that the user Enters.
 This login id and password sent back to the activeX exe through DLL to check the information
in the database.
 If the login id and password entered by the user matches those of the database file then it will
return and redirected to respective control panel, otherwise give an Error massage “login
denied”.
Registration of user
 It takes the information the user and enter it into the database. This module uses the table
‘Documentations for its operation
 This table has following sub module.
 Add
 Edit
 Save
 Delete
Art description
 It takes the information form the Art and enters it into database. This module user the table ‘Art’
for its operation.
 This table has following sub module.
 Add
 Edit
 Update
 Delete
-
REFERENCES
 https://www.tutorialspoint.com/java/
 https://www.sourcecodester.com/
 https://www.phptpoint.com/php-tutorial
 http://www.github.com/
 Google and YouTube tutorials.
 Wikipedia source

MR - PROJECT Editing

Uploaded by

Copyright:

Available Formats

MR - PROJECT Editing

Uploaded by

Document Information

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

MR - PROJECT Editing

Uploaded by

Copyright:

Available Formats

VISVESVARAYA TECHNOLOGICAL UNIVERSITY

“Jnana Sangama”, Belgaum-590014, Karnataka.

A Mini Project Report On

“BANK MANAGEMENT SYSTEM”

Under the Guidance of

DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

EAST WEST INSTITUTE OF TECHNOLOGY

DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

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

Name of the Examiners Signature with date

CHAPTER 1: INTRODUCTION 1-3

Table No Description Page No.

6.1.2 Test cases for Input-Output 22

7.20 Back to Home Page 33

 Efficiently handles customer, account related data.

1.2 Features of the project

Add New Account

DEPT OF ISE, EWIT 1

 Reduction in Cost of Operation

 Support for Multiple Accounts

 Simple And Quick Transactions

DEPT OF ISE, EWIT 2

 Tech-Related Service Disruptions

 Concerns about Identity Theft and Security

 Faster is Not Always More Convenient

 Limited service Scope

DEPT OF ISE, EWIT 3

DEPT OF ISE, EWIT 4

2.1 Project Proposal

2.2 Project Description

2.3 Project Objectives

2.4 Project Scope

DEPT OF ISE, EWIT 5

3.1 Software requirements

 Tools used : Microsoft Visual Studio code

 Backend Design : PHP, JavaScript

 Front end design : HTML, CSS, JS

 Operating System : Windows 8/9/10

3.2 Hardware Requirements

Hard disk : 500GB

Hard disk : 500GB

DEPT OF ISE, EWIT 6

DEPT OF ISE, EWIT 7

TABLE NAME: branch TABLE NAME : FEEDBACK

FIELD NAME DATA TYPE FIELD NAME DATA TYPE

TABLE NAME: LOGIN TABLE NAME: NOTICE

FIELD NAME DATA TYPE FIELD NAME DATA TYPE

DEPT OF ISE, EWIT 8

TABLE NAME: OTHERACCOUNTS

FIELD NAME DATA TYPE

TABLE NAME: TRANSACTION

FIELD NAME DATA TYPE

TABLE NAME: USERACCOUNTS

FIELD NAME DATA TYPE

DEPT OF ISE, EWIT 9

date Varchar (111)

4.2 DATABASE DESIGN

 E-R DIAGRAM OF BANK MANAGEMENT

DEPT OF ISE, EWIT 10