Banking System

CHAPTER 1
INTRODUCTION
1.1 ABSTRACT
The bank management has become necessary which would be useful to

managing the bank in more efficiently. Using this banking system any information
can be easily searched. Administrator can view all the details of the customer.
Using this system user can create new account and maintain data efficiently and
effectively. All records of customer details are stored in separate files. Which are
maintained constantly update by system. Manage large number of customer details
with case. Particular account information can be modified a particular customer
record can be modified for one or more field’s customer name, address by
providing account number. This system more efficient, fast, reliable, user, friendly.
This system contains the staff details in the bank and customer details with
personnel profile. Account details are recorded in the system with clear
information in separate manner which are saving account, joint account, loan
account. The loan account details are maintained separately which contains the
Agriculture loan, Education loan, Housing loan, Gould loan details. The aim of this
project is to provide a solution for loan available details are send to customer
through mail in the single software. This alert mail is very useful to the customer to
continue their account and improve their security. This is very useful to the
customer to know that, what are all the new loan availability, interest reduction and
new plan details in the bank.
1
CHAPTER 2
SYSTEM ANALYSIS AND MODULE DESCRIPTION
2.1 EXISTING SYSTEM
The existing system contains the bank details but does not have the clear details
separately. It contains the all account type details in single module that was very
inconvenient to administrator. The existing system contains the loan details but not
in separate manner. The Banking system contains different loan details but does
not contain the individual details of each loan, this will very inconvenient to view
the each loan transaction details separately. And also it does not have any monthly
report of each transaction for saving account, loan accounts, this may cause burden
to administrator to view the report.
2.2 PROPSED SYSTEM
The bank management has became necessary which would be useful to

managing the bank in more efficiently. The proposed system is used to store all the
record and transaction details in bank. This system contains the staff details in the
bank and customer details with personnel profile. Account details are recorded in
the system with clear information in separate manner which are saving account,
joint account , loan account. The loan account details are maintained separately
which contains the Agriculture loan, Education loan, Housing loan, Gould loan
details. It also provide sending a mail to new loan available details in the bank to
each customer. This is very useful to the customer to know that, what are all the
new loan availability, interest reduction and new plan details in the bank.
2
2.3 MODULES DESCRIPTION
1. Bank Module
2. Employee Module
3. Account Module
4. Customer Module
5. Transfer money Module
6. Loan Entry Module
7. Reports details
Bank details:
This module describes the bank is the place where customers feel the sense for
the sense for the property. In the Bank, customers deposit and withdraw their
money. The bank management system user can manage a money from single
account. Today's world is a genuine computer world and is getting faster and faster
day-by-day. Thus, considering above necessities, the software for bank has became
necessary which would be useful in managing the bank more efficiently.
Employee details:
This module represents to the employee details to work at the bank workers.
The bank management are useful to the customer information, account details,
transfer details, etc. The bank employees can verify the account is very useful for
the customers of saving money of the security.
3
Account Details:
By using this functionality user can create a new account in any bank by
selecting bank name option. Using this functionality user view all his account
details, this can be viewed by users who are having account in any bank.
Saving account:
These accounts are designed to help the individuals (personal customers) to

inculcate the habit of saving money and to meet their future requirement of money.
Amounts can be deposited/withdrawal slips. It helps the customers to keep
minimum cash at home besides earning interest.
Closing account:
This module represents logout the banking organization. These accounts are
designed to help II: individuals to inculcate the habit of single person decision to
the system. The individual’s customer decision from our account.
Customer Details:
This module represents customers account in the banking organization. These

module represent all about of customers, by using this module any customer can do
some operation like create a new account, view the account information. Transfer
amount from one account to other account and customer can also see the
transaction reports. This module consists following functionalities.
 Create customer: By using this functionality user can create a new account
in any bank by selecting bank name option.
 Existing Customer: By using this functionality user can close a account in
any bank by selecting bank name option.
4
Transfer Money Details:
This module represents to the money transaction to the bank. Bank transfer is
when money is send form one bank to another. Transferring money from your
bank account is usually fast, free and safer to withdrawing and paying in cash.
Payments made using Faster Payment will sometimes be received immediately
after leaving your account, but cash sometimes take up to 2 hours. This option is
free, available 24 hours day and typically used in online mobile apps, over the
phone or internet. Most banks let you transfer at least l0,000,00 but some have
mush high limits.
Loan Available Details:
This module represents to the available loans from the bank.
 Education loan:
By using this functionality useful only for the studying students. This
loan available to the purpose of college students, the students mark list and
ration card, college admission fees Xerox, and Aathar card time consuming
formalities involved. Pay interest for the exact period of loan, and to the
exact number of days.
 Gold Loan:
By using this functionality only one recent ID-voter ID/ration
card/Driving license/passport.No time-consuming formalities involved. Pay
interest only the exact period of loan, and to the exact number of days.
Different schemes for different needs, to suit all income groups. Pay interest
only for the exact period of loan, and to the exact number of days.
5
 Housing loan:
By using this functionality only one recent ID-voter ID/ration
card/Driving license/passport.No time-consuming formalities involved.
 Agriculture loan:
By using this functionality useful only for the for formers. This loan
available to the purpose of garden. These are available new facilities in the
bank management.
 Reports Details:
This module contains the report for all modules which contains the
saving account, joint account, loan available details. These are help to
analyze the whole bank information with up to date report. The report for
these modules can be export to anywhere and also can take Wont of that
report.
6
CHAPTER 3
HARDWARE AND SOFTWARE REQUIREMENTS

3.1 Hardware Requirements:
Processor : Intel Duel Core
Hard Disk : 50 GB
Monitor : LCD Color
Mouse : Optical Mouse
RAM : 2GB
3.2 Software Requirements:

Operating System : Windows 8.1
Front End : Visual Studio 2010(VB.Net)
Back End : SQL Server 2008
7
3.3 About the Software
3.3.1 Vb.Net
Microsoft .NET is a set of Microsoft software technologies for rapidly
building and integrating XML Web services, Microsoft Windows-based
application and Web solutions. The .NET Framework is a language-neutral
platform for writing programs that can easily and securely inter-operate. There’s
no language barrier with .NET: there are numerous language available to the
developer including Managed C++, C#, Visual Basic and Java Script. The .NET
framework provides the foundation for components to interact seamlessly, whether
locally or remotely on different platform. It standardizes common data types and
communications protocol so that components created in different languages can
easily inter operate.
“.NET” is also the collective name given to various software components

built upon the .NET platform. These will be both products (Visual Studio.NET and
Windows.NET server, for instance) and services (like passport, .NET My Services,
and so on).
THE .NET FRAMEWORK
The .NET Framework has two main parts:
1. The Common Language Runtime(CLR)

2. A hierarchical set of class libraries.
The CLR is described as the “execute engine” of .NET. It provides the

environment within which programs run. The most important features are
conversion from a low-level assembler-style language, called Intermediate
language (IL), into code native to the platform being executed on.
8
 Memory management, notably including garbage collection.
 Checking and enforcing security restrictions on the running code.
 Loading and executing programs, with version control and other such
features.
 The following features of the .NET framework are also worth
description
Managed Code
The code that targets .NET and which contains certain extra information -
“meta data”- to describe itself. Whilst both managed and unmanaged code can run
in the runtime, only managed code contains the information that allows the CLR to
guarantee, for instance, safe execution and interoperability.
Managed Data
With Managed Code comes Managed data. CLR provides memory

allocation and deal location facilities, and garbage collection. Some .NET language
uses Managed Data by default, such as C#, Visual Basic .NET and j scrip .NET,
whereas others, namely C++, do not. Targeting CLR can depending on the
languages you’re using, impose certain constraints on the features available. As
with managed and unmanaged code, one can have both managed and unmanaged
data in .NET applications –data that does not get garbage collected but instead is
looked after by unmanaged code.
Common Type System
The CLR uses something called the Common Type System (CTS) to strictly
enforce type-safely. This ensures that all classes are compatible with each other, by
describing types in a common way. CTS define how types work within the
9
runtime, which enables types in one language to inter operate with types in another
language, including cross-language exception handling. As well as ensuring that
types are only used in appropriate ways, the runtime also ensures that code does
not attempt to access memory that has not been allocated to it.
Common Language Specification
The CLR provides built-in support for language interoperability. To ensure

that you can develop managed code that can be fully used by developers using any
programming language, a set of language features and rules for using them called
the Common Language Specification (CLS) has been defined. Components that
follow these rules and expose only CLS features are considered CLS – compliant.
THE CLASS LIBRARY
.NET provides a single-rooted hierarchy of classes, containing over 7000

types. The root of the name space is called System. This contains basic types like
Byte, Double, Boolean and String as well as object. All objects derive from
System. Object. As well as object, there are value types. Value types can be
allocated on the stack, which can provide useful flexibility. There are also efficient
means of converting value types to object types if and when necessary.
The set of classes is pretty comprehensive, providing collection, file, screen

and network I/O, threading and so on, as well as XML and database connectivity.
The class library is subdivided into a number of sets (or name spaces), each
providing distinct areas of functionality, with dependencies between the name
spaces kept to a minimum.
10
LANGUAGES SUPPORTED BY .NET
The multi-language capability of the .NET Framework and Visual Studio

.NET enables developers to use their existing programming skills to build all types
of applications and XML Web services. The .NET framework supports new
version of Microsoft’ soft favorites Visual Basic and C++(as VB.NET and
Managed C++), but there are also a number of new additions to the family.
Visual Basic .NET has been updated to include many new and improved
language features that make it a powerful object-oriented programming language.
These features include inheritance, interface and overloading among others. Visual
Basic also now supports structured exception handling, customer attributes and
also supports multi-threading. Visual Basic .NET is also CLS compliant, which
means that any CLS-compliant language can use the classes, objects and
components you create in Visual Basic .NET.
Managed Extension for C++ and attributed programming are just some of
the enhancements made to the C++ language. Managed Extension simplify the task
of migrating existing C++ applications to the new .NET Framework.
THE .NET FRAMEWORK
The .NET Framework is a now computing platform that simplifiers

application development in the highly distributed environment of the Internet.
11
OBJECTIVES OF .NET FRAMEWORK
1. To provides a consistent object-oriented programming environment

whether object code is stored and executed locally on Internet-distributed
or executed remotely.
2. To provide a code-execution environment to minimizes software
deployment and guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application such as Windows-based application and

Web based application.
3.3.2 SQL
The OLAP services feature available in SQL server version 7.0 is now called
SQL Server 2005 Analysis Services. The term OLAP services has been replaced
with the term Analysis services. Analysis services also include a new data mining
component. The Repository components available in SQL server version 7.0 is
now called Microsoft SQL server 2005 Meta Data Services. References to the
component now use the term Meta Data Services. The term repository is used only
in reference to the repository engine within Meta Data Services
SQL SERVER database consist of six types of objects,
They are
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO
12
TABLE
A database is a collection of data about a specific topic
VIEWS OF TABLE
We can work with a table in two types,
1. Design view
2. Data sheet view
DESIGN VIEW
To build or modify the structure of a table we work in the table design view.
We can specify what kind of data will be hold.
DATA SHEET VIEW
To add, edit or analyses the data itself we work in tables data sheet view
mode
QUERY
A query is a question that has to be asked the data. Access gathers data that
answer the questions from one or more table. The data that make up the answer is
either dynast (if you edit it) or a snapshot (it cannot be edited). Each time we run
query, we get latest information in the dynast. Access either displays the dynast set
or snapshot for us to view or perform and action on it, such as deleting or updating.
13
CHAPTER 4
SYSTEM DESIGN
4.1 ARCHITECTURAL DIAGRAM
Software architecture involves the high level structure of software system

abstraction, by using decomposition and composition with architectural style and
quality attributes. A software architecture design must conform to the major
functionality and performance requirements of the system, as well as satisfy the
non-functional requirements such as reliability, scalability, portability and
availability. Software architecture must describe its group of components their
connections, interactions among them and deployment configuration of all
components.
A SOFTWARE ARCHITECTURE CAN BE DEFINED IN MANY WAYS
 UML (Unified Modeling Language) - UML is one of object-oriented

solutions used in software modeling and design
 Architecture view model (4+1 view model) - Architecture view model
represents the functional and non-functional requirements of software
application
 ADL (Architecture Description language) – ADL defines the software
architecture formally and semantically.
14
ARCHITECTURE VIEW MODEL
A model is a complete, basic and simplified description of software

architecture which is composed of multiple views from a particular perspective or
viewpoint. A view is a representation of an entire system from the perspective of a
related set of concerns. It is used to describe the system from the viewpoint of
different stakeholders such as end-users, developers, project managers and testers.
ARCHITECTURE DESCRIPTION LANGUAGE (ADLs)
An ADL is a language that provides syntax and semantics for defining

software architecture. It is a notation specification which provides features for
modeling a software system’s conceptual architecture, distinguished from the
system’s implementation.
ADLs must support the architecture components their connections, interface

and configuration which are building block of architecture description. It is a
platform of expression for use in architecture and defines the interfaces of
components.
An architecture description language is a formal specification language

which describes the software features such as processes, threads, data and sub-
program as well as hardware components such as processors, devices, buses and
memory.
It is hard to classify or differentiate an ADL and a programming language or

a modeling language. However, there are following requirements for a language to
be classified as an ADL -
 It should be appropriate for communicating the architecture to all

concerned parties.
15
 It should be suitable for tasks of architecture creation, refinement
and validation
 It should provides a basic for further implementation, so it must be
able to add information to the ADL specification to enable the final
system specification to be derived from the ADL.
 It should have the ability to represent most of the common
architectural styles.
 It should support analytical capabilities or provide quick generating
prototype implementations
16
ARCHITECTURAL DIAGRAM
start
Login
Banking
system
Bank Worker Account Customer Transfer Loan

details details details details details entry
details
Loan Create Education

account customer loan
Existing Agriculture
customer loan
Housing
loan
Gold loan
Reports details
Store the
data
End
17
4.2 DATA FLOW DIAGRAM
A data flow (DFD) is a graphical representation of the “flow” of data through

an information system, modeling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system, which can later be elaborated.
DFD s can also be used for the visualization of data processing (structured design).
A DFA shows what kind of information will be input to and output from the
system, where the data will come from and go to, and where the data will be
stored. It does not show information about the timing of process or information
about whether processes will operate in sequence or in parallel.
Data flow diagrams are also know as bubble charts. DFD is a designing tool
used in the top-down approach to system design. This context-level DFD is next
“exploded”, to product a level 1 DFD that shows some of the detail of the system
being modeled. The level 1 DFD shows how the system is divided into sub-system
(process), each of which deals with one or more of the data flows to or from an
external agent, and which together provide all of the functionality of the system as
a whole. It also identifies internal data stores that must be present in order for the
system to do its job, and shows the flow of data between the various parts of the
system.
Data flow diagrams are one of the three essential perspectives of the structured
system analysis and design method SSADM. The support of a project and the end
users will need to be briefed and consulted through all stages of a system’s
evolution. With a data flow diagram users are able to visualize how the system will
operate, what the system will accomplish and how the system will be implemented.
The old system’s data flow diagram can be drawn up and compared with the new
system’s data flow diagrams to draw comparison to implement a more efficient
18
system. Data flow diagrams can be used to provide the end user with a physical
idea of where the data they input ultimately has an effect upon the structure of the
whole system from order to dispatch to report. How any system is developed can
be determined through a data flow diagram model.
In the course of developing a set of leveled data flow diagrams the

analyst/designer is forced to address how the system may be decomposed into
component sub system and to identify the transaction data in the data model. Data
flow diagrams can be used in both Analysis and Design phase of the SDLC.
PHYSICAL VS.LOGICAL DFD
A logical DFD captures the data flows that are necessary for a system to
operate. It describes the processes that are undertaken, the data required and
produced by each process and the stores needed to hold the data. On the other
hand, a physical DFD shows how the system is actually implemented either at the
moment (current physical DFD), or how the designer intends it to be in the future
(Required physical DFD). Thus a physical DFD may be used to describe the set of
data items that appear on each piece of paper that move around an office and the
fact that a particular set of pieces of paper are stored together in a filing cabinet. It
is quite possible that a physical DFD will include reference to data that are
duplication or redundant and that the data stores, if implementation as a set of
database tables, would constitute an un-normalized (or de-normalized) relational
database. In contrast a logical DFD attempts to capture the data flow aspects of a
system in a form that has neither redundancy nor duplication.
19
DATA FLOW DIAGRAM SYMBOLS
- Terminator
- Process
- Data
- Delay
- Document
- Multiple Documents
20
- Subroutine
- Preparation
- Display
- Manual Input
- Manual Loop
- Stored Data
- Database
21
- Connector
- Off Page Connector
- Or
- Summing Junction
- Collate
- Sort
- Merge
22
- Data Base
- Internal Storage
STRENGTHS AND WEAKNESS
Strengths
 DFDs have diagrams that are easy to understand, check and change
data.
 DFDs help tremendously in depicting information about how an
organization operations.
 They give a very clear and simple look at the organization of the
interfaces between an application and the people or other applications
that use it.
Weaknesses
 Modification to a data layout in DFDs may cause the entire layout to be

changed. This is because the specific changed data will bring different
data to units that it accesses. Therefore, evaluation of the possible of the
effect of the modification must be considered first.
 The number of units in a DFD in a large application is high. Therefore,
maintained is harder, more costly and error prone. This is because the
23
ability to access the data is passed explicitly from one component to the
other. This is why changes are impractical to be made on DFDs
especially in large system.
RELATIONSHIP AND RULES
The DFD may be used for any levels of data abstraction. DFD can be
partitioned into levels. Each level has more information flow and data functional
details than the previous level.
Highest Level is context Diagram. Some important points are
 1 bubble (process) represents the entire system.

 Data arrows show input and output.
 Data stores NOT shown. They are within the system.
Next level is Level 0 DFD. Some important points are
 Level 0 DFD must balance with the context diagram it describes.

 Input going into a process is different from outputs.
Next level is Level 1 DFD. Some important points are
 Level 1 DFD must balance with the level 0 it describes.

 Input going into a process is different from outputs leaving the process.
 Continue to show data stores.
RULES
 In DFDs, all arrows must be labeled. The information flow continuity,

that is all the input and the output to each refinement, must maintain the
same in order to be able to produce a consistent system.
24
DATA FLOW DIAGRAM
LEVEL 0
System
Administrator
Bank
Information
display
Bank
details
Get view
Username, password
Protected
Login
25
LEVEL 1
Worker details
database
Store the data
Store the
worker details
Get view
View the worker
Details
No
Worker
Yes
details Report
26
LEVEL 2
System
Administrator Store the database
Account store
Get the data the database
Account
details Report
27
LEVEL 3
Existing system
customer details
Create a new account Store the details

view the data in the database
Customer
details stored
Customer
details Report
28
LEVEL 4
View the loan

available detail in
the database
Get view
Loan details store

the database
Loan entry details Report

with the bank
29
4.3 TABLE DESIGN
WORKER DETAIS:
Field Name Data Type

User Name Varchar(10)
First Name Varchar(10)
Last Name Varchar(10)
Bank Name Varchar(10)
Branch Name Varchar(10)
Date of Birth Varchar(10)
Address Varchar(10)
Password Varchar(10)
Re Enter Password Varchar(10)
LOAN ACCOUNT:

Name Varchar(20)
Account product name Varchar(20)
Account status Varchar(20)
Interest amount Varchar(20)
Loan purpose Varchar(20)
30
SAVING ACCOUNT:

Account number Varchar(20)
Account type Varchar(20)
Date of deposit Varchar(20)
Branch name Varchar(20)
Cash amount Varchar(20)
Candidates sign Varchar(20)
TRANSFER MONEY DETAILS:

Name Varchar(20)
Account no Varchar(20)
Address Varchar(20)
Contact no Varchar(20)
Candidates sign Varchar(20)
31
JOINT ACCOUNT:

Date of Joining Varchar(20)
Branch name Varchar(20)
Joint customer name Varchar(20)
Purpose Varchar(20)
HOUSING LOAN:

Name Varchar(20)
Account product name Varchar(20)
Account status Varchar(20)
Interest amount Varchar(20)
Purpose Varchar(20)
CLOSE ACCOUNT:

Bank name Varchar(20)
Branch Varchar(20)
Date Varchar(20)
Address Varchar(20)
Date of closing Varchar(20)
Candidate sign Varchar(20)
32
AGRICULTURE ACCOUNT:

Bank of the name Varchar(20)
Branch Varchar(20)
Date Varchar(20)
Loan of amount Varchar(20)
Aathar id number Varchar(20)
Voter id no Varchar(20)
Email id Varchar(20)
CREATE NEW ACCOUNT:

Name Varchar(20)
sAddress Varchar(20)
Date of opening Varchar(20)
Date Varchar(20)
Account type Varchar(20)
Voter id no Varchar(20)
Aathar id no Varchar(20)
33
CHAPTER 5
SYSTEM IMPLEMENTATION
Implementation is the most crucial stage achieving a successful system and

giving the user’s confidence that the new system is workable and effective.
Implementation of a modified application is used to repltoace an existing once.
This type of conversation is relatively easy to handle, provide there are no major
changes in the system.
Easy program is test individually at time of development using the data has
certified that this program linked together in the way specified it the programs
specification. The computer system and its environment tested to the satisfaction of
the user. The system that has been developed is accepted and proved to be
satisfactory for the user. And so the system is going to be implemented very soon.
A simple operating procedure is included so that user can understand the different
functions clearly and quickly.
Initially as a first step the executable from of the application is to be created

and loaded the common server which is accessible to the entire user and the server
is to be connected to a work. The final stage is to document the entire system
which provides components and the operating procedure of the system.
Implementation is the stage of the project when the theoretical design is

turned is turned out in to a working system. Thus it can be the most critical stage in
achieving a successful new system and in giving the user, confidence that the new
system will work and be effective. The implementation stage involves careful
planning, investigation of the existing system and it’s constraints on implementing,
designing of methods to achieve changeover and evaluation of changeover and
methods
34
Implementation is the processor of converting a new system design in to
operation. It is the phase that focuses on user training, site preparation and file
conversion for installing a candidate system. The imported factor that should be
here is that the conversation should not disrupt the function of the organization.
35
CHAPTER 6
SYSTEM TESTING
6.1 ABOUT TESTING
The purpose of testing is to discover errors. Testing is the process of trying to

discover every conceivable fault or weakness in a work product. It provides a way
to check the functionality of components, sub assemblies and /or a finished product
it is the process of exercising software with the intent of ensuring that the software
system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a
specific testing requirement.
TYPES OF TESTING
UNIT TESTING
Unit testing involves the design of test cases that validate that the internal
program logic is functioning properly and that program inputs produce valid
outputs. All decision branches and internal code flow should be validated. It is the
testing of individual software units of the application. It is done after the
completion of an individual unit before integration. This is a structural testing, that
relies on knowledge of its construction and is invasive. Unit tests perform basic
tests at components level and test a specific business process, application, and/or
system configuration. Unit test ensure that each unique path of a business process
performs accurately to the documented specifications and contains clearly defined
inputs and expected results.
36
Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle. Although it is not uncommon for coding and unit
testing to be conducted as two distinct phase.
Test Strategy and approach
Field testing will be performed manually and functional tests will be written
in details
Test Objectives
 All field entries must work properly

 Pages must be activated from the identified link.
 The entry screen, message and response must not be delayed.
Features to be tested
 Verify that the entries are of the correct format

 No duplicate entries should be allowed
 All links should take the user to the correct page
INTEGRATION TESTING
Integration tests are designed to test integrated software components to

determine if they actually run as one program. Testing is event driven and is more
concerned with the basic outcome of screens or fields. Integration tests
demonstrate that although the components were individually satisfaction, as shown
by successfully unit testing, the combination of components is correct and
consistent. Integration testing is specifically aimed exposing the problem that aries
from the combination of components.
37
Software integration testing is the incremental integration testing of two or
more integrated software components on a single platform to produce failures
caused by interface defects.
The task of the integration test is to check those components or software

applications, e.g. components in a software system or - one step up – software
application at the company level – interact without error.
TEST RESULTS: All the test cases mentioned above passed successfully. No
defects encountered.
FUNCTIONAL TEST
Functional tests provides systematic demonstrations that functions tested are

available as specified by the business and technical requirements, system
documentation and user manuals.
Functional testing is centered on the following items
Valid Input : Identified classes of valid input must be accepted.
Invalid Input : Identified classes of invalid input must be rejected.
Functions : Identified function must be exercised
Output : Identified classes of application outputs must be exercised.
System/Procedures : interfacing systems or procedures must be invoked.
Organization and preparation of functional tests is focused on requirements,

key functions, or special test cases. In addition, systematic coverage pertaining to
identify Business process flows; data fields, predefined processes, and successive
38
processes must be considered for testing. Before functional testing is complete,
additional tests are identified and the effective value of current tests is determined.
SYSTEM TESTING
System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results. An
example of system testing is the configuration oriented system integration test.
System testing is based on process descriptions and flows, emphasizing pre-driven
process links and integration points.
WHITE BOX TESTING
White Box Testing is a testing in which in the software tester has knowledge
of the inner workings, structure and language of the software, or at least its
purpose. It is used to test areas that cannot be reached from a black box level.
BLACK BOX TESTING
Black Box Testing is the testing software without any knowledge of the
inner workings, structure or language of the module being tested. Black box tests,
as most other kinds of tests, must be written from a definitive source document,
such as specification or requirements document, such as specification or
requirements document, such as specification or requirements document. It is a
testing in which the software under test is treated, as a black box you cannot “see”
into it. The test provides inputs and responds to outputs without considering how
software works.
ACCEPTANCE TESTING
User Acceptance Testing is a critical phase of any project and requires

significant participation by the end user. It also ensures that the system meets the
functional requirements.
39
TEST RESULTS:
All the test cases mentioned above passed successfully. No defects

encountered.
40
CHAPTER 7
CONCLUTION
Using this banking system any information can be easily searched.

Administrator can view all the details 0f the customer. Using this system user can
create new account and maintain data efficiently and effectively. All records of
customer details are stored in separate tilts, which are maintained constantly update
by system. Manage large number of customer details with ease. This system more
efficient, fast, reliable, user friendly. The conclusion of this project is to provide a
solution for loan available details are send to customer through mail in the Single
803W“This alert mail is very useful to the customer to continue their account and
improve their security.
41
BIBLIOGRAPHY
Visual Basic 6 programming Black Books (Steven HolznZer)
“Visual Basic.net the tutorials” by kar’1 moore’s 2002
Visual Studio team foundation server 2012 adapting software agile software
practices by Sam (ruckenhenimer & nenoloje)
Beginning SQL server 2008 for developers by robin dev-son
Beginning TSQL with Microsoft SQL server 2005 & 2008
REFERENCES
http:// thomaslarock.com /sqlserverbooks/
http://searchoracle.techtarget.com/answer/SQL -query-for-co-authored-books
http://www.amotlpaa .org/misc/sql.html
http://sqlblog.com/blogs/tibor_karaszi/archive/2016/06/30/books -online-for-sql-
server-2016.aspx
http://www.goodread.com/book/show/8314563-microsoft-visual-basic-2010-steps-
by-step
http://www.amazon.com/murachs-Visual -Basic-2005-Reference/dps/890774383
42
A.Sample source Code:
LOGIN:
Public Class login
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
If TextBox1.Text = "sa" And TextBox2.Text = "sa" Then
MsgBox("valid user")
Form1.Show()
Else
MsgBox("invalid user")
End If
End Sub
Private Sub login_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
End Sub
End Class
EMPLOYEE DETAILS:
Imports System.Data.SqlClient
Imports System.Data
Public Class employee

Dim con As New SqlConnection
Dim cmd As New SqlCommand
Dim re As SqlDataReader
Dim ad As New SqlDataAdapter
Dim ds As New DataSet
43
Dim i As Integer
Private Sub employee_Load(ByVal sender As System.Object, ByVal e As
con = New SqlConnection("Data Source=yamuna-pc;initial
catalog=ACCOUNT3;user id=sa;password=sa")
con.Open()
Disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
DataGridView1.Refresh()
ad = New SqlDataAdapter("select * from worker", con)
ad.Fill(ds, "worker")
DataGridView1.DataSource = ds
DataGridView1.DataMember = "worker"
End Sub
cmd = New SqlCommand("insert into worker values('" & TextBox1.Text &
"','" & TextBox2.Text & "','" & TextBox3.Text & "','" & TextBox4.Text & "','" &
TextBox5.Text & "','" & TextBox6.Text & "','" & TextBox7.Text & "','" &
TextBox8.Text & "','" & TextBox9.Text & "','" & TextBox10.Text & "')", con)
cmd.ExecuteNonQuery()
MsgBox("Values Add")
disp()
End Sub
44
cmd = New SqlCommand("update worker set LastName='" & TextBox3.Text
& "'where DateofBrith=" & Val(TextBox6.Text) & "", con)
MsgBox("Values Updated")
disp()
End Sub
cmd = New SqlCommand("delete from worker where Password='" &
TextBox9.Text & "'", con)
MsgBox("Values Deleted")
disp()
End Sub
cmd = New SqlCommand("select * from worker where BankName='" &
re = cmd.EndExecuteReader()
If re.Read Then
TextBox1.Text = re.GetValue(0)
45
Else
MsgBox("Record not found")
End If
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
TextBox7.Text = ""
TextBox8.Text = ""
TextBox9.Text = ""
TextBox10.Text = ""
End Sub
Me.Hide()
End Sub
End Class
46
SAVING ACCOUNT:
Imports System.Data
Public Class save
Private Sub save_Load(ByVal sender As System.Object, ByVal e As
con.Open()
disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
ad = New SqlDataAdapter("select * from save1", con)
ad.Fill(ds, "save1")
DataGridView1.DataMember = "save1"
End Sub
47
cmd = New SqlCommand("insert into save1 values('" & TextBox1.Text &
disp()
End Sub
cmd = New SqlCommand("update save1 set UserName='" & TextBox1.Text
& "'where AccountType='" & TextBox3.Text & "'", con)
disp()
End Sub
cmd = New SqlCommand("delete from save1 where BranchName='" &
End Sub
48
cmd = New SqlCommand("select * from save1 where DateofDeposit='" &
If re.Read Then
Else
End If
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
TextBox7.Text = ""
End Sub
49
Me.Hide()
End Sub
End Class
JOINT ACCOUNT:
Imports System.Data
Public Class jaint
Dim i As Integer
Private Sub jaint_Load(ByVal sender As System.Object, ByVal e As
con.Open()
disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
ad = New SqlDataAdapter("select * from join1", con)
ad.Fill(ds, "join1")
50
DataGridView1.DataMember = "join1"
End Sub
cmd = New SqlCommand("insert into join1 values('" & TextBox1.Text & "','"
& TextBox2.Text & "','" & TextBox3.Text & "','" & TextBox4.Text & "','" &
TextBox5.Text & "','" & TextBox6.Text & "')", con)
disp()
End Sub
cmd = New SqlCommand("update join1 set JointCustomerName='" &
TextBox5.Text & "'where DateofJoining=" & Val(TextBox3.Text) & "", con)
disp()
End Sub
cmd = New SqlCommand("delete from join1 where Purpose='" &
disp()
51
End Sub
cmd = New SqlCommand("select * from join1 where UserName='" &
If re.Read Then
Else
End If
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
End Sub
52
Me.Hide()
End Sub
SEnd Class
LOAN ACCOUNT:
Imports System.Data
Public Class Loan
Private Sub Loan_Load(ByVal sender As System.Object, ByVal e As
con.Open()
disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
ad = New SqlDataAdapter("select * from loanacc", con)
53
ad.Fill(ds, "loanacc")
DataGridView1.DataMember = "loanacc"
End Sub
cmd = New SqlCommand("insert into loanacc values('" & TextBox1.Text &
TextBox5.Text & "')", con)
disp()
End Sub
cmd = New SqlCommand("update loanacc set LoanProductName='" &
TextBox2.Text & "'where LoanPurpose='" & TextBox5.Text & "'", con)
disp()
End Sub
cmd = New SqlCommand("delete from loanacc where InterestAmount='" &
54
End Sub
cmd = New SqlCommand("select * from loanacc where AccountStatus='" &
If re.Read Then
Else
End If
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
End Sub
Me.Hide()
55
End Sub
End Class
CREATE NEW ACCOUNT:
Imports System.Data
Public Class newacc
Private Sub newacc_Load(ByVal sender As System.Object, ByVal e As
con.Open()
Disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
ad = New SqlDataAdapter("select * from newacc1", con)
ad.Fill(ds, "newacc1")
DataGridView1.DataMember = "newacc1"
56
End Sub
cmd = New SqlCommand("insert into newacc1 values('" & TextBox1.Text &
disp()
End Sub
cmd = New SqlCommand("update newacc1 set Name='" & TextBox1.Text &
"'where AccountType='" & TextBox4.Text & "'", con)
disp()
End Sub
cmd = New SqlCommand("delete from newacc1 where Date='" &
End Sub
57
cmd = New SqlCommand("select * from newacc1 where Dateofopening='" &
If re.Read Then
Else
End If
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
58
TextBox7.Text = ""
TextBox8.Text = ""
TextBox9.Text = ""
End Sub
Me.Hide()
End Sub
Private Sub DataGridView1_CellContentClick(ByVal sender As System.Object,
ByVal e As System.Windows.Forms.DataGridViewCellEventArgs) Handles
DataGridView1.CellContentClick
End Sub
End Class
TRANSFER MONEY MODULE:
Imports System.Data
Public Class transfer
Dim i As Integer
Private Sub transfer_Load(ByVal sender As System.Object, ByVal e As
59
con.Open()
disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
ad = New SqlDataAdapter("select * from trans1", con)
ad.Fill(ds, "trans1")
DataGridView1.DataMember = "trans1"
End Sub
cmd = New SqlCommand("insert into trans1 values('" & TextBox1.Text &
disp()
End Sub
cmd = New SqlCommand("update trans1 set BranchName='" &
TextBox2.Text & "'where DateofClosing=" & Val(TextBox5.Text) & "", con)
60
disp()
End Sub
cmd = New SqlCommand("delete from trans1 where Address='" &
disp()
End Sub
cmd = New SqlCommand("select * from trans1 where NameoftheBank='" &
If re.Read Then
TextBox1.Text = re.GetValue(0)s
Else
End If
61
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
End Sub
Me.Hide()
End Sub
End Class
HOUSING LOAN:
Imports System.Data
Public Class Housing
Dim i As Integer
62
Private Sub Housing_Load(ByVal sender As System.Object, ByVal e As
con.Open()
disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
ad = New SqlDataAdapter("select * from house1", con)
ad.Fill(ds, "house1")
DataGridView1.DataMember = "house1"
End Sub
cmd = New SqlCommand("insert into house1 values('" & TextBox1.Text &
disp()
End Sub
63
cmd = New SqlCommand("update house1 set Name='" & TextBox1.Text &
"'where Date=" & Val(TextBox3.Text) & "", con)
disp()
End Sub
cmd = New SqlCommand("delete from house1 where AccountNumber='" &
disp()
End Sub
cmd = New SqlCommand("select * from house1 where TotalAmount='" &
If re.Read Then
64
Else
End If
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
TextBox7.Text = ""
End Sub
Me.Hide()
End Sub
End Class
AGRICALTURE LOAN:
Imports System.Data
Public Class Agri
65
Dim i As Integer
Private Sub Agri_Load(ByVal sender As System.Object, ByVal e As
con.Open()
disp()
End Sub
Sub disp()
ad.Dispose()
ds.Clear()
ad = New SqlDataAdapter("select * from agri1", con)
ad.Fill(ds, "agri1")
DataGridView1.DataMember = "agri1"
End Sub
cmd = New SqlCommand("insert into agri1 values('" & TextBox1.Text & "','"
& TextBox2.Text & "','" & TextBox3.Text & "','" & TextBox4.Text & "','" &
66
disp()
End Sub
cmd = New SqlCommand("update agri1 set CandidateName='" &
TextBox5.Text & "'where Date=" & Val(TextBox4.Text) & "", con)
disp()
End Sub
cmd = New SqlCommand("delete from agri1 where AccountNumber='" &
disp()
End Sub
cmd = New SqlCommand("select * from agri1 where NameoftheBank='" &
If re.Read Then
67
Else
End If
End Sub
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
TextBox7.Text = ""
TextBox8.Text = ""
TextBox9.Text = ""
End Sub
Me.Hide()
End Sub
End Class
68
B. Screen Shorts:
Login:
Main Form:
69
Employee Details:
Transfer Money Details:
70
Joint Account:
Create New Account:
71
Agriculture Loan:
Saving Account:
72
Loan Account:
Housing Loan:
73
Report
Saving Account Report:
Loan Account Report:
74
Agriculture Report:
Housing Loan Report:
75
Create New Account:
76

Banking System

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

Banking System

Uploaded by

Copyright:

Available Formats

CHAPTER 1

The bank management has become necessary which would be useful to

2.2 PROPSED SYSTEM

The bank management has became necessary which would be useful to

5. Transfer money Module

6. Loan Entry Module

These accounts are designed to help the individuals (personal customers) to

This module represents customers account in the banking organization. These

Loan Available Details:

This module represents to the available loans from the bank.

HARDWARE AND SOFTWARE REQUIREMENTS

Monitor : LCD Color

Mouse : Optical Mouse

3.2 Software Requirements:

Front End : Visual Studio 2010(VB.Net)

Back End : SQL Server 2008

“.NET” is also the collective name given to various software components

THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime(CLR)

The CLR is described as the “execute engine” of .NET. It provides the

With Managed Code comes Managed data. CLR provides memory

Common Type System

Common Language Specification

The CLR provides built-in support for language interoperability. To ensure

THE CLASS LIBRARY

.NET provides a single-rooted hierarchy of classes, containing over 7000

The set of classes is pretty comprehensive, providing collection, file, screen

The multi-language capability of the .NET Framework and Visual Studio

THE .NET FRAMEWORK

The .NET Framework is a now computing platform that simplifiers

1. To provides a consistent object-oriented programming environment

There are different types of application such as Windows-based application and

SQL SERVER database consist of six types of objects,

A database is a collection of data about a specific topic

We can work with a table in two types,

DATA SHEET VIEW

Software architecture involves the high level structure of software system

A SOFTWARE ARCHITECTURE CAN BE DEFINED IN MANY WAYS

 UML (Unified Modeling Language) - UML is one of object-oriented

A model is a complete, basic and simplified description of software

ARCHITECTURE DESCRIPTION LANGUAGE (ADLs)

An ADL is a language that provides syntax and semantics for defining

ADLs must support the architecture components their connections, interface

An architecture description language is a formal specification language

It is hard to classify or differentiate an ADL and a programming language or

 It should be appropriate for communicating the architecture to all

Bank Worker Account Customer Transfer Loan

Loan Create Education

A data flow (DFD) is a graphical representation of the “flow” of data through

In the course of developing a set of leveled data flow diagrams the

PHYSICAL VS.LOGICAL DFD

- Off Page Connector

STRENGTHS AND WEAKNESS

 Modification to a data layout in DFDs may cause the entire layout to be

RELATIONSHIP AND RULES

Highest Level is context Diagram. Some important points are

 1 bubble (process) represents the entire system.

Next level is Level 0 DFD. Some important points are

 Level 0 DFD must balance with the context diagram it describes.

Next level is Level 1 DFD. Some important points are

 Level 1 DFD must balance with the level 0 it describes.

 In DFDs, all arrows must be labeled. The information flow continuity,