69% found this document useful (78 votes)

57K views

Project Report - Banking Management System

The document is a project report for a Banking Management System. It includes sections on system requirements, design, current status, lessons learned, and source code. The key points are: 1) The project aims to computerize common banking tasks like account opening, transactions, loans, and account maintenance to make record keeping easier. 2) System requirements include maintaining customer records and accounts, processing daily transactions, and generating reports. 3) A feasibility study was conducted and the project was deemed economically, technically, and operationally feasible. 4) Visual Basic .NET will be used for the interface and MS SQL Server 2000 for the backend database.

Uploaded by

Gourav Sharma

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

69% found this document useful (78 votes)

57K views

Project Report - Banking Management System

Uploaded by

Gourav Sharma

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

You are on page 1/ 154

PROJECT REPORT

BANKING MANAGEMENT SYSTEM

TABLE OF

CONTENTS

 Abstract of the Project

 System Requirements

 Product Definition

 Feasibility Analysis

 Project Plan

 System requirements specification

 Developing/Operation/Maintenance

Environments

 External Interface and data Flows

 Functional and performance Specifications

 Design
 Detailed DFDs

 Data structure, Database and File Specifications.

 Project Legacy

 Current status of project

 Remaining areas of concern

 Technical and managerial lessons learnt

 Future recommendations

 Source code

 Scope of the Project

 Bibliography and References

ABSTRACT OF THE PROJECT

As we are beginners and have no practical experience in the

field of software development and moreover the Banking

System is very wide. So, we limit the scope of our project by

computerizing the following fields of the Banking System: -

 Account Opening.

 Daily Transactions.
 Loan Sanctions.

 Account Maintenance.

 Search:-

1. Searches record of a particular Account Holder.

2. Searches the record for a each type of Account(s).

I. Savings Account

II. Current Account

III. Fixed Deposit Account

IV. Recurring Deposit Account

V. Loan Account

3. Searches the record of a particular organization’s

Account Holders.

SYSTEM REQUIREMENTS

 PRODUCT DEFINITION:-

We have come to final

conclusion that after analyzing the existing system of the

“Solitaire Software”. We came to know that it is very

difficult for the person to maintain records manually same

in the case with the person who is maintaining Books Like

Ledgers etc., so in order to provide the bank with such a

system that helps them easy in maintaining the records of

the customers, we are going with this project. The

operations performed by this project are maintenance the

information of the Customers that are dealing with the

bank.

 PROBLEM STATEMENT:-

 Data redundancy and inconsistency.

 Difference in accessing data.

 Data isolation.

 Security problem

 Communication gap

 Updating problem

 FUNCTIONALITY TO BE PROVIDED:-
 Maintenance of Account Holder’s records those are

available in the Books.

 Maintenance of Daily Transactions that are ongoing in

the Bank.

 Maintenance of Different Accounts for the annual

closing of Accounting Books.

 Searching Criterion.

 Maintenance of the reports.

 PROCESSING ENVIRONMENT-HARDWARE AND

SOFTWARE: -

 Operating system is a platform on which the

specified application will be used. Once it has been

complete, the software we are about to make, will

execute on both client machine and server machine.

 Configuration:-

 O/S –Windows XP.

 RAM – Min. 256 MB

 Networking enabled for clients, or database.

 SOLUTION STRATEGY:-

 Classical Life Cycle Model:-

This is a sequential

approach to software development. It begins with

analysis and progresses through design, coding,

testing & maintenance.

 Analysis:-

To understand the nature of the program

to build, the analysts must know the required

function, behavior, performance and interfacing.

These requirements are found by interleaving the

Customer and asking them various questions

regarding their needs.

 Design:-
This process translates the requirement

into a representation that can be accessed before

putting into actual code, design includes the following

activities:-

1. Algorithm

2. Logical Design Flow Charts

3. Physical Design

4. Database Design

 Coding:-

The design is then translated into actual

machine language using appropriate language.

 Testing:-

The design is then translated in written,

testing begins, the testing focus on the checking

the logic if the code, intervals of the software to

uncover errors so that the code produces the

actual result.

 Maintenance:-
Maintenance is done after the

software has been installed at the user site. As

error bound to occur so changes has to be done to

meet the user needs.

 ACCEPTANCE CRITERIA:-

 Computerize maintenance of records.

 Maintain Account Holder’s information.

 Maintain the records of the Daily Transactions in

the bank.

 Maintain various reports( i.e. Account Statements).

 FEASIBILITY ANALYSIS:-

Depending on the results

of the initial investigation, the survey is expanded to a

more detailed feasibility study. A feasibility study is a

test of a system proposal. According to its workability,

impact on the organization, ability to meet user’s needs

and effective use of the resources its main task done

during the feasibility study are:-

1. Evaluation of existing system and procedures. Our

group went to various Banking Professionals to

gather information about the software system. They

are using and evaluating those system and the

procedures invoked in it during the period of

feasibility study.

2. Analysis of alternative candidate systems after

studying the various systems we derived various

alternatives through which we develop our project

and evaluated the alternative. The most appropriate

is selected.

 ECONOMIC FEASIBILITY:-
The only tangible benefit

provided by the proposed system is that the paper work

is reduced to the minimum and hence the reduction in

cost incurred on Stationary and its storage. The system

provides many benefits that can’t be measured in terms

of Money for e.g. user’s friendliness, more user

response being more efficient.

 TECHNICAL FEASIBILITY:-

The proposed system is

technically feasible as it can be developed easily with

the help of available technology. The proposed system

requires MS – VISUAL Studio 2005 using VB.Net as a

Interface for Programming & back-end as MS-SQL

Server 2000 for storing/maintaining database. The

database can be easily interconnected using MS-SQL

Server 2000.

 OPERATIONAL FEASIBILITY:-

Automation makes our

life easy. The proposed system is highly user friendly

and is much easily able to interact with the system.

Therefore the users will readily accept the system as

data entry and making queries can be easily done.

 PROJECT PLAN:-

 TEAM STRUCTURE AND SIZE:-

 For developing this project, our team structure

consist 3 members as mentioned above.

 Each member has devoted his efforts toward the

achievement for this project.

 The whole project is divided among us, so that

functionality can be achieved.

 DEVELOPMENT SCHEDULE:-

As per college requirements and infrastructure, our

team has devoted maximum time for the

development of the project.

 PROGRAMMING LANGUAGE, DEVELOPMENT TOOLS

(FRONT-END AND BACK-END):-

 Front-End: - Visual Studio 2005

 Back-End: - MS-SQL Server 2000.

VISUAL PROGRAMMING

 Visual programming aims at providing the user with an

interface that is intuitive and easy to use. In developing

such an interface, the programmer employs user-friendly

features such as windows, menus, buttons and list boxes.

 Its Environment provides all features that are required

to develop a graphical user interface as ready -to- use

components. The programmer does not have to write code

to create and display commonly required user-friendly

features each time around.

 When the programmer needs a specific user interface

feature such as button, he selects the appropriate ready-

to-use component provided by the visual programming

environment. These components can be moved, resized

and renamed as required.

 For Example:-

If the programmer needs to have a

button then the visual programming environment provides

him with one. All that, the programmer does this select

the button and place it on screen at the required position.

 Typically the mouse is used to select and place the

necessary components. Thus, the visual programming

environment is also called a point and click environment.

 A visual programming environment automates the

process of creating a user interface. The interface provided

by the visual programming environment to the

programmer designs the user interface visually instead of

writing code.
 In addition it also provides a means of associating code

with each component. In each case of calculator, for each

button, we can specific that the code is to execute when

we click on it.

NEED FOR VISUAL PROGRAMMING:-

 There are several programming tools that allow us to

build such visually appealing and intuitive interface. These

tools allow us to design interface that employ user friendly

features such as menus, buttons, windows etc.

 However, the disadvantage of such tools is that the

interface is designed using code. The programmer has to

code the user interface features specifying the size,

position etc. this makes designing the user interface a

major task in itself.

ADVANTAGES OF VISUAL PROGRAMMING:-

 Visual development of graphical user interface which

are easy to use and easy to learn.

 A programmer need not write code to display the

required component.

 For Example:-
The visual programming environment

displays a list of available components. The programmer

picks up the required component from this list to display

it.

 The component can be moved, resized and even

deleted, if so required.

 There is no restriction on the number of controls that

can be placed on a form.

 The interface components provided by the visual

programming environment have some code built into

them.
 For example:-

A button’ knows’ when it has been clicked

upon. In the case of conventional programming tools, the

programmer has to write code to determine the

component that has been clicked and then execute the

appropriate code.

 Some popular Visual Programming tools are:-

 Visual basis.net 2005

 Power builder

 Developer 2000

 Visual Basic is one of the most popular programming

tools available today. And it’s also secret that there have

been massive changes in it as it became Visual Basic.Net.

 The reason of that change is Visual Basic itself, which

has now become Visual Basic.Net. The difference between

Visual Basic.Net and the previous version. Visual Basic 6.0

is revolutionary and far reaching. Visual Basic.Net has

been more than four years in the marking and it

represents entirely new directions for Visual Basic. Besides

the biggest change integrated support for web

development the very syntax, of techniques that you’ve

probably learned carefully are now completely different

such as data handling and many controls; project types

and other aspects of Visual Basic 6.0 are no longer

available at all.

 Visual Basic has a long and so far glorious history.

When it first appeared, it created a revolution in windows

programming. Visual Basic introduced unheard of ease to

windows programming just builds the program you want

right before your eyes, and then run it. In so doing it

changed programming form a chore to something very like

fun.
 There are two visual styles available in V.B. IDE that are

 SDI (Single Document Interface).

 MDI (Multiple Document Interface)

INTRODUCTION TO VISUAL STUDIO .NET

 Microsoft’s .NET initiative is broad-based and very

ambitious. It includes .NET framework, which

encompasses the languages and execution platform, plus

extensive class libraries providing rich building

functionality. Besides the core .NET framework, the .NET

initiative includes protocols (such as Simple Object Access

Protocol-SOAP) to provide a new level of s/w integration

over the Internet via standard net services.

 The first release product based on .NET framework was

Visual Studio 2002.

 BROAD AND DEEP PLATFORM FOR THE FUTURE:-

.NET framework encompasses a virtual machine that

abstracts away much of the windows API from

development. Its environment supports multiple

languages. The vision of Microsoft .NET is globally

distributed systems, using XML as universal glue to allow

function running on different computers across an

organization or across the world.

 DIFFICULTIES WITH DNA AND COM:-

The Pre .NET

technologies used for development on Microsoft platforms

encompassed the COM standard for creation of

components and DNA model for multitier s/w

architectures. These standards had some drawbacks.

 Difficulty in integrating Internet technologies.

 Lack of full object orientation.

 One threading model.

 Poor integration with Internet.

 Poor error handling.

OVERVIEW OF .NET FRAMEWORK

.NET is a framework that covers all the layers s/w development

above the operating system. It provides the richest level

of integration among presentation technologies,

component technologies and data technologies ever seen

on a Microsoft platform. The entire architecture has been

created to make it easy to develop internet applications,

as it is to develop for the desktop.

VS.NET supports Windows 2003,Windows XP and all versions of

Windows 2000.Programs created for .NET can also run

under Windows NT, Windows 98, and Windows Me, though

VS.NET doesn’t run on the system.

MAJOR COMPONENTS OF .NET FRAMEWORK: -

 ASP.NET (Web Services, Web forms, Asp.Net application

Services).

 WINDOW FORMS (Controls, Drawing, Window

application Services).

 NET FRAMEWORK BASE CLASSES (ADO. Net, XML,

Threading, IO, Component model, Security, Diagnostics,

etc.).

 COMMON LANGUAGE RUNTIME (Memory Management,

Common type System, Lifecycle Monitoring).

The framework starts all the way down at the memory

management and component loading level, and goes all the

way up to multiple ways of rendering user and program

interfaces.
CLR (Common Language Runtime):-

The CLR manages

the execution of code on .NET platform .The functionality

exposed by CLR is available to all .NET languages. Language

Runtimes go back further than DOS languages. Its main

parts are: -

 Common type System

 Intermediate Language to Native code compilers.

 Execution support.

 Security.

 Garbage Collection, Stack walk, Code Manager.

 Class Loader and Memory layout.

THE DESIGN OF CLR IS BASED ON FOLLOWING GOALS:-

1. Simple Faster Development.

2. Automatic handling of system level task.

3. Excellent Tool support.

4. Simple safer deployment.

5. Scalability.

XML AS .NET META LANGUAGE: -

Much of the Underlying

integration of .Net is accomplished with XML. Web Services

depend completely on XML for interfacing with Remote

Object. ADO.Net is dependent on XML for representations of

Remote Data. When ADO.NET creates data set .The data is

converted to XML for manipulation by ADO.NET.

INTRODUCTION TO VB.NET & VS.NET: -

SOLUTION EXPLORER: -

On right side of VS.NET is

Solution explorer. It provides a central location for all the

files in your Project.

 NAMESPACES: -

Namespace is a way of organizing

classes, Structures, Enumeration, Delegates and

Interfaces that .NET Framework class library provides. A

Namespace is a combination of Naming convention and an

assembly that organizes collections of objects and

Removes ambiguity in object references.

 CODE WINDOW: -
This is an editor to write code .it is

also possible to hide the customs portions of code.

#Region is used to hide the code.

 PROPERTIES WINDOWS: -

This window displays the

properties of the form and the objects present in the form.

The property value can be retrieved and as well as its

value can be set

 USEFUL FEATURES OF .NET: -

 Task List

 Command Window

 Server explorer

 Macros in Visual Studio

 ELEMENTS OF A .NET APPLICATION

 Assemblies: -

An assembly is the basic unit of

deployment.
 Modules: -

The individual files that make up an

assembly.

 Classes: -

This unit encapsulates data and its

behavior.
INTRODUCTION TO BACK END TOOL

Introduction to SQL: -

SQL is a standard computer

language for accessing and manipulating databases.

• SQL stands for Structured Query Language.

• SQL allows you to access a database.

• SQL is an ANSI standard computer language.

• SQL can execute queries against a database.

• SQL can retrieve data from a database.

• SQL can insert new records in a database.

• SQL can delete records from a database.

• SQL can update records in a database.

• SQL is easy to learn.

 SQL is an ANSI (American National Standards Institute)

standard computer language for accessing and

manipulating database systems. SQL statements are used

to retrieve and update data in a database. SQL works with

database programs like MS Access, DB2, Informix, MS SQL

Server, Oracle, Sybase, etc.

 Unfortunately, there are many different versions of the

SQL language, but to be in compliance with the ANSI

standard; they must support the same major keywords in

a similar manner (such as SELECT, UPDATE, DELETE,

INSERT, WHERE, and others).

SQL Database Tables: -

A database most often contains

one or more tables. Each table is identified by a name (e.g.

"Customers" or "Orders"). Tables contain records (rows) with

data.

Below is an example of a table called "Persons": -

Last Name First Name Address City

Hansen Ola Timoteivn 10 Sandnes
Svendson Tove Borgvn 23 Sandnes
Pettersen Kari Storgt 20 Stavanger

 The table above contains three records (one for each

person) and four columns (Last Name, First Name,

Address, and City).

SQL Queries: -

With SQL, we can query a database

and have a result set returned.

 A query like this: -

SELECT Last Name FROM Persons

 Gives a result set like this: -

Last Name
Hansen
Svendson
Petersen
SQL Data Manipulation Language (DML)

 SQL (Structured Query Language) is syntax for

executing queries. But the SQL language also includes

syntax to update, insert, and delete records.

 These query and update commands together form the

Data Manipulation Language (DML) part of SQL: -

 SELECT - extracts data from a database table

 UPDATE - updates data in a database table

 DELETE - deletes data from a database table

 INSERT INTO - inserts new data into a database table

SQL Data Definition Language (DDL)

 The Data Definition Language (DDL) part of SQL permits

database tables to be created or deleted. We can also

define indexes (keys), specify links between tables, and

impose constraints between database tables.

 The most important DDL statements in SQL are: -

 CREATE TABLE - creates a new database table

 ALTER TABLE - alters (changes) a database table

 DROP TABLE - deletes a database table

 CREATE INDEX - creates an index (search key)

 DROP INDEX - deletes an index

MS SQL SERVER 2000

 The code base for MS SQL Server (prior to version 7.0)

originated in Sybase SQL Server, and was Microsoft's

entry to the enterprise-level database market, competing

against Oracle, IBM, and, later, Sybase itself.

 Microsoft, Sybase and Ashton-Tate originally teamed up

to create and market the first version named SQL Server

1.0 for OS/2 (about 1989) which was essentially the same

as Sybase SQL Server 3.0 on Unix, VMS, etc.

 Microsoft SQL Server 4.2 was shipped around 1992

(available bundled with Microsoft OS/2 version 1.3). Later

Microsoft SQL Server 4.21 for Windows NT was released at

the same time as Windows NT 3.1.

 Microsoft SQL Server v6.0 was the first version

designed for NT, and did not include any direction from

Sybase.

 About the time Windows NT was released, Sybase and

Microsoft parted ways and each pursued their own design

and marketing schemes. Microsoft negotiated exclusive

rights to all versions of SQL Server written for Microsoft

operating systems.

 Later, Sybase changed the name of its product to

Adaptive Server Enterprise to avoid confusion with

Microsoft SQL Server. Until 1994, Microsoft's SQL Server

carried three Sybase copyright notices as an indication of

its origin.

 Since parting ways, several revisions have been done

independently. SQL Server 7.0 was a rewrite from the

legacy Sybase code. It was succeeded by SQL Server

2000, which was the first edition to be launched in a

variant for the IA-64 architecture.

 In the eight years since release of Microsoft's previous

SQL Server product (SQL Server 2000), advancements

have been made in performance, the client IDE tools, and

several complementary systems that are packaged with

SQL Server 2005.

 These include: an ETL tool (SQL Server Integration

Services or SSIS), a Reporting Server, an OLAP and data

mining server (Analysis Services), and several messaging

technologies, specifically Service Broker and Notification

Services.

 SQL Server 2000(codenamed Yukon), released in

October 2000.

 It included native support for managing XML data, in

addition to relational data.For this purpose, it defined an

xml data type that could be used either as a data type in

database columns or as literals in queries.

 XML columns can be associated with XSD schemas; XML

data being stored is verified against the schema. XML is

converted to an internal binary data type before being

stored in the database. Specialized indexing methods were

made available for XML data.

 XML data is queried using XQuery; SQL Server 2000

added some extensions to the T-SQL language to allow

embedding XQuery queries in T-SQL. In addition, it also

defines a new extension to XQuery, called XML DML, that

allows query-based modifications to XML data.

 SQL Server 2000 also allows a database server to be

exposed over web services using TDS packets

encapsulated within SOAP (protocol) requests. When the

data is accessed over web services, results are returned as

XML.

 For relational data, T-SQL has been augmented with

error handling features and support for recursive queries.

SQL Server 2000 has also been enhanced with new

indexing algorithms and better error recovery systems.

Data pages are check-summed for better error resiliency,

and optimistic concurrency support has been added for

better performance.

 Permissions and access control have been made more

granular and the query processor handles concurrent

execution of queries in a more efficient way. Partitions on

tables and indexes are supported natively, so scaling out a

database onto a cluster is easier.SQL CLR was introduced

with SQL Server 2000 to let it integrate with the .NET

Framework.

 SQL Server 2000 introduced "MARS" (Multiple Active

Results Sets), a method of allowing usage of database

connections for multiple purposes.

SYSTEM REQUIREMENTS SPECIFICATION

SYSTEM ANALYSIS:

Analysis is a detailed study of the various operations

performed by the system and their relationship within and

outside the system.

1. Data Dictionary: -

A Data Dictionary is a structure

repository of data about data. It is a set of rigorous

definitions of all the data flow diagram, data elements and

data structure.

 There are three classes of items to be defined:

 Data element: smallest unit of data.

 Data structure: group of data element handled as

a unit.
 Data flow and data stores: temporary location of

data and permanent location of data.

2. Decision tree: -

A decision tree is a diagram that presents

condition and actions sequentially. It is a method of

showing relationship of each condition and its permissible

actions.

3. Decision table: -

A decision table is a table of

contingencies for defining a problem and actions to be

taken single representation of the relationship between

conditions and actions.

SYSTEM DESIGN

 The design of information system produces the detail

that states how system will need the requirements

identified during system analysis. Often system specialists

refer to the stage as logical design, in correct to

developing program software, which is referred ton as

physical design.
 This phase take requirements as agreed and develops

the system to the level of detail necessary to prepare the

way of programming. At this point analyst is concerned

with the detail of input and output, the processing

required, and the way in which the system will operate on

the data today based. It is concerned with the computer

oriented design of the system, such as the detail of the

input transactions, the detail of the printed report, screens

and other outputs the file or the database structures, the

contents of records, the processing required and the

efficiency of the system from a computer processing point

of view.

 System analyst start by identifying by reports and other

outputs the system will produce. Then the specific data on

each case pin pointed, including its exact location on the

display screens. Usually designers sketch the form or

display as except it to appear when the system is

completed.
 The design also describes the data to be input,

calculated or stored. Individual’s data items and

calculations procedure written tells how to process the

data and produce the output. The documents contains the

design specifications use many different ways of portray

the design.

 For Example: -

The logical data flow diagram, entity

relationship model etc., the designers are responsible for

providing programmers with complete and clearly outlined

specifications that states what he software would be.

 Location: -

The project was discussed as well as

developed in our own college’s software lab during our

practical and in our free time.

 Support and Outside Service: -

The major

support providers were our project in charge. They help

us in queries and rectify all the errors and defects.

DESIGN

 DETAILED DFDs: -

 DATA FLOW DIAGRAM: -

The data flow diagram is

also known as “bubble chart” has the purpose of
clarifying system requirements and identifying major
transformations that will become programs in system
design so it is the starting point of specification down to
the lowest level of detail. A DFDs consists of a series if
bubbles joined by lines. The bubbles represent data
transformation and the lines represent the data flow in
the system.

 DFD SYMBOLS:

 A system defined a source or destination of data.

 An arrow identifies data flow, data in motion.
 A circle represents the process that transforms
incoming data flow to outgoing data flow.
 An open rectangular is data store-data at rest or a
temporary repository of data.
SYSTEM DATA FLOW DIAGRAM

BANKING ACCOUNT
TRANSACTIONS
HOL

DATABASE
DATA STRUCTURES AND DATABASE

SPECIFICATIONS

“ACCOUNT_INFO” Table: -

Field Name Type Constraints

Account_No Int Primary Key
Branch_No Varchar(7) References

Branch_Info(Branch_No)
Branch_Name VARCHAR(50) Not Null
Account_H_Type Varchar(15) Not Null
No_Account_H Varchar(5) Not Null
Saluation_F Varchar(5) Not Null
Name_P_O_F Varchar(50) Not Null
Fa_Name_F Varchar(50) Not Null
Gender_F Varchar(6) Not Null
DOB_F DateTime Not Null
Age_F Varchar(3) Check(Age_F>=0 and

Age_F<100)
Occupation_F Varchar(15) Not Null
Photo_F Image Not Null
Sign_F Image Not Null
Address_F Varchar(100) Not Null
Ph_No_F Varchar(11) Not Null
Mob_No_F Varchar(14) Not Null
Saluation_S Varchar(5)
Name_P_O_S Varchar(50)
Fa_Name_S Varchar(50)
Gender_S Varchar(6)
DOB_S DateTime
Age_S Varchar(3) Check(Age_S>=0 and

Age_S<100)
Occupation_S Varchar(15)
Photo_S Image
Sign_S Image
Address_S Varchar(100)
Ph_No_S Varchar(11)
Mob_No_S Varchar(14)
Saluation_T Varchar(5)
Name_P_O_T Varchar(50)
Fa_Name_T Varchar(50)
Gender_T Varchar(6)
DOB_T DateTime
Age_T Varchar(3) Check(Age_T>=0 and

Age_T<100)
Occupation_T Varchar(15)
Photo_T Image
Sign_T Image
Address_T Varchar(100)
Ph_No_T Varchar(11)
Mob_No_T Varchar(14)
Account_Type Varchar(25) Not Null
Witness_Name Varchar(50) Not Null
Witness_Sign Image Not Null
Nominee_Rel Varchar(10) Not Null
Nominee_Name Varchar(50) Not Null
Nominee_Sign Image Not Null
Opening_Bal Varchar(10)
T_Date DateTime Not Null

“Branch_Info” Table: -

Field Name Type Constraints

Branch_No Varchar(7) Primary Key

Branch_Name Varchar(50)
“Deposit_Info” Table: -

Field Name Type Constraints

Account_No Int References

Account_Info(Account_No)
Branch_No Varchar(7)
Depositor_Name Varchar(150)
Account_H_Type Varchar(15)
Deposit_Amt Varchar(10)

Deposit_Date DateTime
“Fixed_Info” Table: -

Field Name Data type Constraints

Account_No Int References

Account_Info(Account_No)
Branch_No Varchar(7)
Depositor_Name Varchar(50)
Account_H_Type Varchar(15)
Time_Span Varchar(5) References

Rate_Of_Interest_Info(Time_Span)
ROI Varchar(5)
Start_Date DateTime
Mature_Date Varchar(15)
Deposit_Amt Varchar(10)
Mature_Amt Varchar(10)

“Login_Info” Table: -

Field Name Data type Description

UserName Varchar(20) Primary Key

UserPassWord Varchar(15)
“Login_Info” Table: -

Field Name Data type Description

Time_Span Varchar(5) Primary Key

ROI Varchar(5)

“Recurring_Info” Table: -

Field Name Data type Description

Account_No Int References

Account_Info(Account_No)
Branch_No Varchar(7)
Depositor_Name Varchar(50)
Account_H_Type Varchar(15)
Time_Span Varchar(5) References

Rate_Of_Interest_Info(Time_Span)
ROI Varchar(5)
Start_Date DateTime
Mature_Date Varchar(15)
Monthly_Deposit Varchar(10)
Principle_Amt Varchar(10)
Mature_Amt Varchar(10)

“Withdrawl_Info” Table: -
Field Name Type Constraints

Account_No Int References

Account_Info(Account_No)
Branch_No Varchar(7)
Withdrawee_Nam Varchar(150)

e
Account_H_Type Varchar(15)
Withdrawl_Amt Varchar(10)

Withdrawl_Date DateTime
“Loan_Info” Table: -

Field Name Type Constraints

Account_No Int References

Account_Info(Account_No)
Branch_No Varchar(7)
Acc_Holder_Name Varchar(50)
Account_Type Varchar(15)

Account_Sub_Type Varchar(15)
Time_Span Varchar(5) References

Rate_Of_Interest_Info(Time_Span)
ROI Varchar(5)
Issue_Date DateTime
Due_Date Varchar(15)
Loan_Sanctioned Varchar(10)
No_Installments Varchar(5)
EMI Varchar(10)
Total_Loan_Ret Varchar(10)
PROJECT LEGACY

 Current status of project: -

This project is now wards

complete but we can add more things like ATM, Online

Transactions through Online Banking.

 Remaining areas of concern: -

This software project is

complete and can be used to access records, can

generate reports whenever necessary or needed.

 Technical and managerial lessons learnt: -

During the

development of project we have learnt many lessons

like the rules prevailing within an organization like: -

 Proper defined structure.

 Good chain of commands.

 Work should be divided among each other.

 Effective and efficient environment for working and

development.

 Future recommendations: -

As we all know that the

change is permanent, so according to change this

project can be modified or manipulated according to

needs.
SPLASH FORM
CODING

Public Class SPLASH

Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Timer1.Tick
If ProgressBar1.Value = ProgressBar1.Maximum Then
LOGIN.Show()
Me.Hide()
Timer1.Stop()
Else
ProgressBar1.Value = ProgressBar1.Value + 10
End If
End Sub
Private Sub FlashLabel()
Label1.ForeColor = Color.RoyalBlue
Timer3.Start()
End Sub
Private Sub Timer2_Tick(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Timer2.Tick
Call FlashLabel()
End Sub
Private Sub Timer3_Tick(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Timer3.Tick
Label1.ForeColor = SystemColors.Control
Timer3.Stop()
End Sub
End Class
LOGIN FORM
CODING

Imports System.Data.SqlClient

Public Class LOGIN

Private Sub LOGIN_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
Button1.Enabled = False
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button2.Click
Dim A As Integer
A = MsgBox("Do you want to exit", MsgBoxStyle.OkCancel,
"Exit")
If A = vbOK Then
Application.Exit()
End If
If A = vbCancel Then
Exit Sub
End If
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
Dim CON As New SqlConnection
Dim CMD As New SqlCommand
Dim DR As SqlDataReader

CON.ConnectionString = "Server =ANGELDEVIL;Initial

Catalog=BankingSystem;Integrated Security=True"
CON.Open()
CMD.Connection = CON
CMD.CommandText = "Select * From Login_Info"

DR = CMD.ExecuteReader

While DR.Read
If DR.HasRows Then
If TextBox1.Text = DR(0) And TextBox2.Text = DR(1) Then
Me.Hide()
Dim A As Integer
A = MsgBox("Login Successfully", MsgBoxStyle.OkOnly)
If A = vbOK Then
MAIN.Show()
End If
Return
End If
End If
End While

MsgBox("Invalid User Name or Password", MsgBoxStyle.Exclamation)

TextBox1.Text = ""
TextBox2.Text = ""
Button1.Enabled = False
TextBox1.Select()
CMD.Dispose()
CON.Close()
End Sub
Private Sub Button3_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button3.Click
Me.Hide()
CHANGE_PASSWORD_FORM.Show()
End Sub

Private Sub TextBox1_TextChanged(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles TextBox1.TextChanged
If TextBox1.Text = "" Then
Button1.Enabled = False
ElseIf TextBox2.Text = "" Then
Button1.Enabled = False
Else
Button1.Enabled = True
End If
End Sub

Private Sub TextBox2_TextChanged(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles TextBox2.TextChanged
If TextBox1.Text = "" Then
Button1.Enabled = False
ElseIf TextBox2.Text = "" Then
Button1.Enabled = False
Else
Button1.Enabled = True
End If
End Sub
End Class
MDI FORM
CODING

Imports System.Windows.Forms

Public Class MAIN

Private Sub ExitToolStripMenuItem1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
ExitToolStripMenuItem1.Click
Dim A As Integer
A = MsgBox("Do You Want To Close", vbOKCancel)
If A = vbOK Then
Application.Exit()
Else
Return
End If
End Sub

Private Sub DepositToolStripMenuItem1_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
DepositToolStripMenuItem1.Click
NOMINAL_ACCOUNTS.MdiParent = Me
NOMINAL_ACCOUNTS.Show()
End Sub
Private Sub DepositToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
DepositToolStripMenuItem.Click
DEPOSIT_FORM.MdiParent = Me
DEPOSIT_FORM.Show()
End Sub
Private Sub WithdrawlToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
WithdrawlToolStripMenuItem.Click
WITHDRAWL.MdiParent = Me
WITHDRAWL.Show()
End Sub
Private Sub HelpMenu_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles HelpMenu.Click
ABOUT_US_FORM.MdiParent = Me
ABOUT_US_FORM.Show()
End Sub
Private Sub FixedDepositToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
FixedDepositToolStripMenuItem.Click
FIXED_DEPOSIT.MdiParent = Me
FIXED_DEPOSIT.Show()
End Sub
Private Sub AccountsToolStripMenuItem1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
AccountsToolStripMenuItem1.Click
ACCOUNTS_REPORT_FORM.MdiParent = Me
ACCOUNTS_REPORT_FORM.Show()
End Sub
Private Sub SavingsToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
SavingsToolStripMenuItem.Click
DEPOSIT_REPORT.MdiParent = Me
DEPOSIT_REPORT.Show()
End Sub
Private Sub CurrentToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
CurrentToolStripMenuItem.Click
FIXED_REPORT.MdiParent = Me
FIXED_REPORT.Show()
End Sub
Private Sub RecurringToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
RecurringToolStripMenuItem.Click
RECURRING_REPORT.MdiParent = Me
RECURRING_REPORT.Show()
End Sub
Private Sub WithdrawlToolStripMenuItem1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
WithdrawlToolStripMenuItem1.Click
WITHDRAWL_REPORT.MdiParent = Me
WITHDRAWL_REPORT.Show()
End Sub
Private Sub LoanToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
LoanToolStripMenuItem.Click
LOAN.MdiParent = Me
LOAN.Show()
End Sub
Private Sub RecurringDepositToolStripMenuItem_Click(ByVal sender
As System.Object, ByVal e As System.EventArgs) Handles
RecurringDepositToolStripMenuItem.Click
RECURRING_DEPOSIT.MdiParent = Me
RECURRING_DEPOSIT.Show()
End Sub
End Class
ACCOUNT OPENING FORM
CODING

Imports System.Data.SqlClient
Imports System.IO

Public Class NOMINAL_ACCOUNTS

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles Button2.Click
Me.Close()
End Sub

Private Sub NOMINAL_ACCOUNTS_Load(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

' Button1.Enabled = False

TextBox1.ReadOnly = True
TextBox1.Enabled = False
TextBox2.ReadOnly = True
TextBox2.Enabled = False

Dim CON As New SqlConnection

Dim CMD As New SqlCommand
Dim DR As SqlDataReader

CON.ConnectionString = "Server =ANGELDEVIL;Initial

Catalog=BankingSystem;Integrated Security=True"

CON.Open()
CMD.Connection = CON
CMD.CommandText = "Select * From Account_Info"
DR = CMD.ExecuteReader

While DR.Read
TextBox1.Text = DR(0)
End While

DR.Close()

CMD.Dispose()
CON.Close()

TextBox1.Text = Val(TextBox1.Text) + 1

TextBox9.ReadOnly = True
TextBox9.Enabled = False
TextBox10.ReadOnly = True
TextBox10.Enabled = False
TextBox11.ReadOnly = True
TextBox11.Enabled = False
TextBox23.ReadOnly = True
TextBox23.Enabled = False

CON.Open()
CMD.Connection = CON
CMD.CommandText = "Select * From Branch_Info"
DR = CMD.ExecuteReader

While DR.Read
ComboBox1.Items.Add(DR(0))
End While

DR.Close()
CMD.Dispose()
CON.Close()

End Sub

Dim STRImage As String

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles Button1.Click

IF TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text =

"" Or TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = ""
Or TextBox7.Text = "" Or TextBox8.Text = "" Or TextBox9.Text = "" Or
TextBox10.Text = "" Or TextBox11.Text = "" Or TextBox12.Text = ""
Or TextBox13.Text = "" Or TextBox14.Text = "" Or TextBox15.Text =
"" Or TextBox16.Text = "" Or TextBox17.Text = "" Or TextBox18.Text
= "" Or TextBox19.Text = "" Or TextBox20.Text = "" Or
TextBox21.Text = "" Or TextBox22.Text = "" Or TextBox23.Text = ""
Or ComboBox1.Text = "" Or ComboBox2.Text = "" Or ComboBox3.Text
= "" Or ComboBox4.Text = "" Or ComboBox5.Text = "" Or
ComboBox6.Text = "" Or ComboBox7.Text = "" Or ComboBox8.Text =
"" Or ComboBox9.Text = "" Or ComboBox10.Text = "" Or
ComboBox11.Text = "" Or ComboBox12.Text = "" Or
RadioButton1.Checked = False Or RadioButton2.Checked = False Or
RadioButton3.Checked = False Or RadioButton4.Checked = False Or
RadioButton5.Checked = False Or RadioButton6.Checked = False Or
DateTimePicker1.Text = "" Or DateTimePicker2.Text = "" Or
DateTimePicker3.Text = "" Or DateTimePicker4.Text = "" Then

MessageBox.Show("Plz fill the form")

Exit Sub

End If

Dim CON As New SqlConnection

Dim CMD As New SqlCommand

CON.ConnectionString = "Server =ANGELDEVIL;Initial

Catalog=BankingSystem;Integrated Security=True"

CON.Open()
CMD.Connection = CON
CMD.CommandType = CommandType.StoredProcedure
CMD.CommandText = "InsertAccount_Info"

'Try

CMD.Parameters.Add("@Account_No", SqlDbType.Int).Value =
TextBox1.Text
CMD.Parameters.Add("@Branch_No", SqlDbType.VarChar).Value
= ComboBox1.Text
CMD.Parameters.Add("@Branch_Name",
SqlDbType.VarChar).Value = TextBox2.Text
If RadioButton1.Checked = True Then
CMD.Parameters.Add("@Account_H_Type",
SqlDbType.VarChar).Value = RadioButton1.Text
ElseIf RadioButton2.Checked = True Then
CMD.Parameters.Add("@Account_H_Type",
SqlDbType.VarChar).Value = RadioButton2.Text
ElseIf RadioButton3.Checked = True Then
CMD.Parameters.Add("@Account_H_Type",
SqlDbType.VarChar).Value = RadioButton3.Text
End If
If RadioButton4.Checked = True Then
CMD.Parameters.Add("@No_Account_H",
SqlDbType.VarChar).Value = RadioButton4.Text
ElseIf RadioButton5.Checked = True Then
CMD.Parameters.Add("@No_Account_H",
SqlDbType.VarChar).Value = RadioButton5.Text
ElseIf RadioButton6.Checked = True Then
CMD.Parameters.Add("@No_Account_H",
SqlDbType.VarChar).Value = RadioButton6.Text
End If
CMD.Parameters.Add("@Saluation_F", SqlDbType.VarChar).Value
= ComboBox2.Text
CMD.Parameters.Add("@Name_P_O_F",
SqlDbType.VarChar).Value = TextBox3.Text
CMD.Parameters.Add("@Fa_Name_F", SqlDbType.VarChar).Value
= TextBox6.Text
CMD.Parameters.Add("@Gender_F", SqlDbType.VarChar).Value =
ComboBox5.Text
CMD.Parameters.Add("@DOB_F", SqlDbType.DateTime).Value =
DateTimePicker1.Text
CMD.Parameters.Add("@Age_F", SqlDbType.VarChar).Value =
TextBox9.Text
CMD.Parameters.Add("@Occupation_F",
SqlDbType.VarChar).Value = ComboBox8.Text