Bank Management System

PROJECT REPORT BMS

CHAPTER 1

INTRODUCTION

DEPT. OF INFORMATION TECHNOLOGY 1 TKM INSTITUTE OF TECHNOLOGY

PROJECT REPORT BMS

1 INTRODUCTION

PROJECT OVERVIEW

The main Objective of "BANK MANAGEMENT SYSTEM” is to prepare a software or

application, which could maintain data & provide a user friendly interface for retrieving

customer related details just in few seconds, with 100% accuracy. Software is completely

computerized, so it is not time consuming process. No paper work required & can be

implemented further. It contains two levels of users: - Admin, and User

MODULE DESCRIPTION

1. ADMIN MODULE

This module deals with all transaction of bank management. By using this module

administrator can Create/Edit/View all details of customers, he can go for any

transactions like withdraw and deposits money and also they view all the transactions.

Various functions of Administrator are given below.

1.1 Create New Account

By using this functionality user can create a new account in any bank by

selecting bank name option. All the information’s are automatically inserted into the

database.

2.1 Edit An Account

By using this functionality user can update an existing account. The new values

are automatically updated in the database.

3.1 View Account Details

By using this option, the administrator can view the account details of any users

who are having an account in the bank.


PROJECT REPORT BMS

4.1 Withdraw Amount

By using this facility provided, the administrator can withdraw money. The new

balance amount will be automatically calculated and updated in the database

5.1 Deposit Amount

By using this facility provided, the administrator can deposit money. The new

balance amount will be automatically calculated and updated in the database

6.1 Transaction Report

By using this functionality, the administrator can view all the transaction reports

like deposits, withdrawals….etc. we have also provided options to filter the reports based

on name, date….etc

1.2 USER MODULE

Each account number is provided with a password. This module describes all about

customers, by using this module any customer can do some operations like view his

account information, change account details...etc The customer can also view his

transaction Reports


PROJECT REPORT BMS

1.2 HARDWARE SPECIFICATION

PROCESSOR : PENTIUM III 866 MHz

RAM : 1 GB Ram or higher

HARD DISK : 80GB

MONITOR : 15” COLOR

KEYBOARD : 104 Standard

MOUSE : Standard(Microsoft Compactable)

1.3 SOFTWARE SPECIFICATIONS

OPERATING SYSTEM : Windows XP Professional or Higher

ENVIRONMENT : Visual Studio .NET 2009

FRONT-END LANGUAGE : Visual Basic.net

BACK-END LANGUAGE : MS ACCESS

DESIGNING : ADOBE PHOTOSHOP CS2 or higher


PROJECT REPORT BMS

DEVELOPING TOOL

ABOUT .NET

The .NET Framework is just part of Microsoft’s overall .NET

platform strategy. The framework is made up of the Common Language Runtime

environment, Base Class Library, and higher-level frameworks such as Vb.NET

and Windows Forms as shown in Figure


PROJECT REPORT BMS

FEATURES OF VISUAL BASIC. NET

Visual Basic .NET, the latest version of visual basic, includes many new features.

The Visual Basic supports interfaces but not implementation inheritance. Visual basic.net

supports implementation inheritance, interfaces and overloading. In addition, Visual

Basic .NET supports multithreading concept.

COMMON LANGUAGE SPECIFICATION (CLS):

Visual Basic.NET is also compliant with CLS (Common Language Specification)

and supports structured exception handling. CLS is set of rules and constructs that are

supported by the CLR (Common Language Runtime). CLR is the runtime environment

provided by the .NET Framework; it manages the execution of the code and also makes

the development process easier by providing services.

Visual Basic.NET is a CLS-compliant language. Any objects, classes, or

components that created in Visual Basic.NET can be used in any other CLS-compliant

language. In addition, we can use objects, classes, and components created in other CLS-

compliant languages in Visual Basic.NET .The use of CLS ensures complete

interoperability among applications, regardless of the languages used to create the

application.

IMPLEMENTATION INHERITANCE:

Visual Basic.NET supports implementation inheritance. This means that, while

creating applications in Visual Basic.NET, we can drive from another class, which is

know as the base class that derived class inherits all the methods and properties of the

base class. In the derived class, we can either use the existing code of the base class or

override the existing code. Therefore, with help of the implementation inheritance, code

can be reused.


PROJECT REPORT BMS

CONSTRUCTORS AND DESTRUCTORS:

Constructors are used to initialize objects, whereas destructors are used to destroy

them. In other words, destructors are used to release the resources allocated to the object.

In Visual Basic.NET the sub finalize procedure is available. The sub finalize procedure is

used to complete the tasks that must be performed when an object is destroyed. The sub

finalize procedure is called automatically when an object is destroyed. In addition, the

sub finalize procedure can be called only from the class it belongs to or from derived

classes.

GARBAGE COLLECTION:

Garbage Collection is another new feature in Visual Basic.NET. The .NET

Framework monitors allocated resources, such as objects and variables. In addition,

the .NET Framework automatically releases memory for reuse by destroying objects that

are no longer in use. In Visual Basic.NET, the garbage collector checks for the objects

that are not currently in use by applications. When the garbage collector comes across an

object that is marked for garbage collection, it releases the memory occupied by the

object.

OVERLOADING:

Overloading is another feature in Visual Basic.NET. Overloading enables us to

define multiple procedures with the same name, where each procedure has a different set

of arguments. Besides using overloading for procedures, we can use it for constructors

and properties in a class.

MULTITHREADING:

Visual Basic.NET also supports multithreading. An application that supports

multithreading can handle multiple tasks simultaneously, we can use multithreading to

decrease the time taken by an application to respond to user interaction. To decrease the

time taken by an application to respond to user interaction, we must ensure that a separate

thread in the application handles user interaction.


PROJECT REPORT BMS

STRUCTURED EXCEPTION HANDLING:

Visual Basic.NET supports structured handling, which enables us to detect and

remove errors at runtime. In Visual Basic.NET, we need to use Try…Catch…Finally

statements to create exception handlers. Using Try…Catch…Finally statements, we can

create robust and effective exception handlers to improve the performance of our

application.

ADO.NET

ADO.NET is the latest in a long line of data access technologies released by

Microsoft. ADO.NET differs somewhat from the previous technologies, however, in that

it comes as part of a whole new platform called the .NET Framework. This platform is set

to revolutionize every area of development, and ADO.NET is just one aspect of that. The

ADO.NET classes are divided into two components: the Data Providers (sometimes

called Managed Providers), which handle communication with a physical data store, and

the Dataset, which represents the actual data. Either component can communicate with

data consumers such as Web Forms and Win Forms.

DATA PROVIDERS

The Data Provider components are specific to a data source. The .NET Framework

includes two Data Providers: a generic provider that can communicate with any OLE DB

data-source, and a SQL Server provider that has been optimized for Microsoft SQL

Server versions 7.0 and later. Data Providers for other databases such as Oracle and DB2

are expected to become available, or we can write our own. The two Data Providers

included in the .NET Framework contain the same objects, although their names and

some of their properties and methods are different. The Connection object represents the

physical connection to a data source. Its properties determine the data provider (in the

case of the OLE DB Data Provider), the data source and database to which it will

connect, and the string to be used during connecting. Its methods are fairly simple.

You can open and close the connection, change the database, and manage transactions.

The Command object represents a SQL statement or stored procedure to be executed at


PROJECT REPORT BMS

the data source. Command objects can be created and executed independently against a

Connection object, and they are used by Data Adapter objects to handle communications

from a Dataset back to a data source. Command objects can support SQL statements and

stored procedures that return single values, one or more sets of rows, or no values at all.

A Data Reader is a fast, low-overhead object for obtaining a forward-only, read-only

stream of data from a data source. They cannot be created directly in code; they are

created only by calling the Execute Reader method of a Command.

The Data Adapter is functionally the most complex object in a Data Provider. It

provides the bridge between a Connection and a Dataset. The Data Adapter contains four

Command objects: the Select Command, Update Command, Insert Command, and Delete

Command. The Data Adapter uses the Select Command to fill a Data Set and uses the

remaining three commands to transmit changes back to the data source, as required.

DATA SETS

The Dataset is a memory-resident representation of data. The Dataset can be considered a

somewhat simplified relational database, consisting of tables and their relations. It’s

important to understand, however, that the Dataset is always disconnected from the data

source—it doesn’t “know” where the data it contains came from, and in fact, it can

contain data from multiple sources.


PROJECT REPORT BMS

DATABASE

Microsoft Access for consideration for our project database development platform:

Microsoft Access is available with the Microsoft Office Professional suite of

business products therefore no additional database software is required if your

company purchases computers with this suite of products already installed.

Microsoft Access 2007 database is likely to be available and supported for years

to come because Microsoft is the premier software company in the world

MS Access is the most widely used desktop database system in the world.

If database support is important to you then Access may be your best choice since

Access has more support and development consultants than any other desktop

database system.

Microsoft Access is significantly cheaper to implement and maintain compared to

larger database systems such as Oracle or SQL Server.

Microsoft Access consulting rates are typically lower for Access consultants

compared to Oracle or SQL Server consultants.

Fairly complex databases can be setup and running in 1/2 the time and cost of

other large database systems (the simpler the database the greater the cost

advantage).

Microsoft Access integrates well with the other members of the Microsoft Office

suite of products (Excel, Word, Outlook, etc.).

Other software manufacturers are more likely to provide interfaces to MS Access

than any other desktop database system.


PROJECT REPORT BMS

When designed correctly, Access database can be ported (usually with some

difficulty) to SQL server or Oracle. This is important if you want to start or

develop a small database system and then migrate to the larger database

management system and then migrate to the larger database management systems.

A Microsoft Access system can be placed on a website for access for remote

users. Simple screens can be developed within Access, Data Access Pages or full

control and functionality can be implemented using ACTIVE SERVER PAGE

(ASP) programming.

Why you should choose Microsoft Access Database!

Microsoft Access provides users with one of the simplest and most flexible RDBMS

solutions on the market today. Regular users of Microsoft products will enjoy the familiar

Windows 'look and feel' as well as the tight integration with other Microsoft Office

family products. If Microsoft Office is your preferred office software suite then it makes

sense to seriously consider Microsoft Access as your database of choice.

What are the Benefits?

Cost Access Database comes packaged with Microsoft Office Professional

and so it may already be part of your SOE.

Ease of use As with all Microsoft product, Access Database has that familiar

Windows 'look and feel'

Support Microsoft Access is one of the best-selling desktop databases of all

time. As such you can be sure of future support, and with Microsoft's

backing it should be around for some time to come.

Future proof Because Microsoft is constantly improving their database you can be

sure that your investment is future-proof. Microsoft Access is not a


PROJECT REPORT BMS

dead end product.

Multi-User Since the beginning, Access was designed to operate on a network.

Microsoft says that the latest version will support 255 concurrent

users; however in practice we would recommend a more comfortable

limit of 15 to 20 simultaneous users.

Cost of

development

The popularity of Access with database developers provides you with

greater choice of developers and lower development rates consistent

with a competitive market place.

Rapid

Application

Development

You can use Microsoft Access for Rapid Application Development

thus keeping your costs down. Its object oriented model means you

can build attractive, functional and easy to use applications in double-

quick time.

Scalable Access has an upgrade path. So, if performance starts to suffer from

an ever increasing number of users or records, you can upsize to SQL

Server.

Integration Access has been designed to works well with other products in the

Microsoft Office suite. It has been designed with integration in mind.

Legacy data Access can import many data formats so your existing data is not

lost. When properly exploited, and electronic data is available, this

feature alone can save 100s of data input hours

Web integration Access (2000 and later version) has close web links so online data

access is made easier. With a shift towards e-commerce, Access's

web integration could prove very useful, if not now, then sometime in

the near future.


PROJECT REPORT BMS

Multi-User Support

While Microsoft specifications allow for up to 255 simultaneous users, multiple sources

have found that no more than 12 users can successfully use a networked Access

application before the delay in connections through the file system pose a problem. Also

note that users must be attached to the local LAN and have access to the shared

networked drive hosting the Access application. This is not a problem for small teams in

one location, but once teams are spread across multiple locations the application access

slows down significantly for all users.

The maximum concurrent user count listed by Microsoft assumes that the data is stored in

one Access Database while access to the data comes from a separate Microsoft Access

interface, such as an Access Application Project. In this instance the Access application

resides on a user’s machine while the Access database data resides on a shared network

drive to which all users need Read/Write access.

While security is often not a consideration when deploying an Access database

application, note that complete security can only be attained through folder security

permissions. While users and roles can be defined in an Access database, it has been

found relatively simply to circumvent these permissions and gain full access to the

system. For secure access network administrators will need to grand and deny access to

shared folders to the specific users who can access the database.

More inherent in Microsoft access is the inability to easily use profile information about

users. It is not trivial to store profile specific information about a user. For example, if a

user is in one project, for them to see only their data in their queries, instead of data from

all projects, data must be pulled when a user logs into the system from a table and stored

globally. Then all queries must code in access to this property. Web application tools

such as ASP.NET provide profile information built-in, and adding these filters to stored

procedures is fairly trivial.

Most government organizations create a standard version of Microsoft Office across the

organization. All users have the same version and service pack of Office, allowing for


PROJECT REPORT BMS

simple deployment of the application. An Access database or Access Database Project

can connect to a remote Microsoft Access database and retrieve information.

Whenever a modification is made to the underlying database or user interface a new

version of the Access Database must be loaded on the desktops of all users of the system.

Scalability

For relatively small data sets Access works very well for providing flexible information

retrieval. It provides simple functionality to create pivot tables and generate graphical

reports. Connections to the database are made using Jet or ODBC database connections.

These connections work in small levels, but have more overhead when sending and

receiving information.

While up to 255 simultaneous connections are supported, this works in an environment

where all users are on the same LAN (local area network). Once users become distributed

across multiple locations, connections to the database slow down dramatically. This is

primarily due to the fact that all connections to the database must be made through a

mapped drive connection. Connecting to a remote mapped drive is much slower than

native SQL Server or other database connections.

Microsoft Access also has a file size limitation of 2 GB of data. While there is very little

possibility of exceeding the file size in many cases, the amount of time needed to retrieve

data for a query or report becomes exponentially long as the number of rows in a table

increases. When a table exceeds tens of thousands of rows processing time for a query

becomes minutes instead of seconds.

Very often to retrieve information formatted in a way that is usable multiple nested

queries are needed. Generally 3 or 4 nested queries are needed to retrieve the information

in a usable format. In some cases one query is run to generate a table, after which another

query is run to generate another table. This is done so that the final query can run quickly,

but requires multiple steps by a user to generate the data in a usable format that can be

retrieved in minutes instead of hours. This also adds a very large amount of work to make


PROJECT REPORT BMS

changes to a query or add additional data, as all underlying queries must be modified.

Confusion can easily occur as unused tables exist in the database, often where only the

database creator will know which tables to use at which time.

Reporting

As long as a strong understanding of SQL queries is understood and deep understanding

of the underlying tables, reports can be created to extract and display information,

including the ability to export the data to Excel or many other formats easily.

These reports use the underlying queries to generate and format their data. They work

very well, though not always quickly for large calculations or formatting. Generally a

more robust reporting tool such as SQL Server Reporting Services, Crystal Reports or

another application will retrieve this information faster and provide the same graphical

and export options. The disadvantage to these solutions is that quickly creating a new

report is not as easy as it is in Microsoft Access.

Data Import

Importing data into Microsoft Access is relatively simple for simple amounts of data.

Performing large data imports and formatting of final data is more difficult in Microsoft

Access than it is in more robust database tools such as SQL Server and Oracle. This is

generally due to the modified version of SQL available in Microsoft Access. Fewer

functions exist for formatting, extracting and updating data into disparate tables. Often to

extract a specific set of data, such as a list of locations, the database administrator must

create a query for that one action and run it to populate a location table. More robust tools

allow for multiple queries to run at one time, and provide transactional processes, so that

if any part of the import fails all changes are rolled back to a state before the import

began.


PROJECT REPORT BMS

Remote Use

For a user to use the system from a machine away from their office, they will need to

have the same version of Microsoft Access installed. While this is not often a problem in

government organizations, as mentioned above, it does require that users have access to

the shared folder wherever they are located. Web based applications allow a user to

access the system from any location that has Internet access.

Web applications also allow for seamless updates to the system. If a new field is added to

a form or report, the code is placed only on the Web server, and the new form appears to

the user the next time they access or refresh a page. In an Access application, the new

code must be sent to all users of the system. Without additional coding in the Access

application to ensure the latest version is always used, it is possible that a user could use

outdated code to update the application. This can allow for invalid data to be entered or

invalid reports to be generated.

User Accessibility

While Microsoft Office programs now meet (as of Office 2003) the governments’

standards for Section 508 accessibility, there is no guaranty that applications created in

Microsoft Access meet those standards. If forms are used in the access application, more

care must be taken in providing keyboard access and linking labels to fields for screen

reader access.


PROJECT REPORT BMS

CHAPTER 2

SYSTEM STUDY AND ANALYSIS


PROJECT REPORT BMS

2 SYSTEM STUDY AND ANALYSIS

2.1 EXISTING SYSTEM

The main limitations of the proposed system are:-

Lack of immediate retrievals

Lack of immediate information storage

Error prone manual calculation

Registers may lost or damage

Any unauthorized person can access confidential data.

In the existing system, the manual process, receiving data’s from customers are done

through manual records. These records are entered in manual process. In this process will

take long time, separate workers are need to maintaining records. The information is very

difficult to retrieve and to find particular information the user has to go through various

registers. This results in inconvenience and wastage of time. The information generated

by various transactions takes time and efforts to be stored at right place. Manual

calculations are error prone and take a lot of time this may result in incorrect information

2.2 PROPOSED SYSTEM

The objective & goals of the proposed system are:-

Main Aim of our project is to perform various banking tasks.

To allow only authorized user to access various functions and

procedures available in the system.

Locate any A/C wanted by the user.

Reduced clerical work as most of the work done by computer.

Provide greater speed & reduced time consumption.

To increase the number of A/C and customer.


PROJECT REPORT BMS

THE OBJECTIVE is to prepare a software or application, which could maintain data &

provide a user friendly interface for retrieving customer related details just in few

seconds. This will reduce the manual workload and give information instantly. The

software will maintain the list of A/C and customer record and balance status. The

software will be user friendly so that even a beginner can operate the package and thus

maintain the status of A/C and balance status easily.


PROJECT REPORT BMS

CHAPTER 3

SYSTEM DESIGN


PROJECT REPORT BMS

3. SYSTEM DESIGN

3.1 INPUT DESIGN

Input design is the process of converting user oriented input into a computer based

format. The data flow diagram indicates logical data flows, data stores source and

destinations. Input data are collected and organized into a group of numbered data. Once

identified appropriate input media are selected for processing. The goal of input design is

to make data entry as easy and free from errors as much as possible. Proper data

validation checking is exercised to correct the mistakes made during data entry.

ADMIN MODULE

1. Test case : LOGIN

Input : ID, Password.

Process : Click on the login link. If administrator enters ID and password correct it goes to the admin services otherwise displays the same page with an error message.

Output : Displays the admin services page.

2. Test case : ADD NEW ACCOUNT

Input : Name, Acno ,age, phno, address ,gender…etc

Process : Accept the details and check for validity

Output : A new account is created.


PROJECT REPORT BMS

3. Test case : EDIT AN ACCOUNT

Input : Account number and the new details

Process : The new values are inserted into database

Output : Details are updated to the database.

4. Test case : WITHDRAW AMOUNT

Input : Account number and amount to be withdrawn

Process : Calculate the balance amount.

Output : Details are updated to the database

5. Test case : DEPOSIT AMOUNT

Input : Account number and amount to be deposited.

Process : Calculate the balance amount.

Output : Details are updated to the database

6. Test case : VIEW TRANSACTION DETAILS

Input : Account no

Process : Retrieve the details from database.

Output : Transaction details are shown


PROJECT REPORT BMS

USER MODULE

1. Test case : EDIT USER ACCOUNT

Input : Account number and the new details

Process : The new values are inserted into database

Output : Details are updated to the database.

2. Test case : CHECK BALANCE

Input : Account no


Output : Balance amount is shown

3. Test case : VIEW TRANSACTION DETAILS

Input : Account no


Output : Transaction details are shown


PROJECT REPORT BMS

3.2 DATA BASE DESIGN

A relational database is a collection of data items organized as a set of formally

described tables’ from data can be accessed or reassembled in many different ways

without having to recognize the database tables. The relational database was invented by

E.F Codd at IBM in 1970

A database is an organized mechanism that has the capability of storing information

through which a user can retrieve stored information in an effective and efficient manner.

The data is the purpose of any database and must be protected.

During the database design phase of the system design, the analyst selects the storage

which is best for storing the systems data. The objective of the database design is to

provide auxiliary storage and to contribute to overall efficiency of the computer program

components of the system.

The basic functions involved in a database system related to the information required

by its users are:

Defining the data

Inputting the data

Locating the data


PROJECT REPORT BMS

3.2.1 ENTITY RELATIONSHIP DIAGRAM


Account

s

Account Deposit

Acno

Withdraw

Admin User

Password

Age

E-MAIL

Ac-no

Name

Address

Balance

Income

AcType

Gender

Ac-no

Name

Address

Balance

Income

AcType

Gender

Age

Password

E-mail Email

Creates

New a/c

Edit

Account

View

Transaction

Password

Age

Ac-no

Name

Ac-noName Passwor

d

Address

Email

A/c no

Withdrawe

Deposit

View

A/cDetails

Name

Address

BalancePerfor

m

Deposit/ Withdraw

TransID

balance

Edit

Name

Address

Email

Account

View

Transaction

deposit

Withdraw

TransId

BMS

Manages

PROJECT REPORT BMS

3.2.2 TABLE DESIGN

Table Name: Bank

Description: Stores Details about Account Holders

Field Name Data Type Constraints Description Key

Acno Number Indexed Account No Primary Key

Name Text Not null Name

Hname Text Not null House Name

Hplace Text Not null Place

Hdistrict Text Not null District

PinCode Number Not null Pin code

Age Number Not null Age

Gender Text Not null Gender

PhNo Number Not null Phone No

Occupation Text Not null Occupation

Email Text Not null Email

Annual Income Number Not null Annual income

Photo Text Not null Photo

BalanceAmount Number Not null Balance Amount

Password Text Not null Password

IntroducedBy Text Not null Introduced by

Acc_type Text Not null Account type

Validity Text Not null Validity


PROJECT REPORT BMS

Table Name: TRANSACTION

Description: Stores all the transactions

Field Name DataType Constraints Description Key

Tr_Date Date/Time Not null Transaction Date

AcNo Number Not null Account No

Withdraw Number Not null Amount Withdrawn

Deposit Number Not null Amount Deposited

TransId Number Indexed Transaction ID Primary Key


PROJECT REPORT BMS

3.3 CODE DESIGN

DATA FLOW DIAGRAM

The data flow diagram is a way of expressing system requirements in a graphical

form. This led to the modular design. A DFD is also known as bubble sort has the

purpose of clarifying system requirements and identifying system requirements and

identifying major transformations that will become program in system design.

DFD DIAGRAM FOR BANK MANAGEMENT SYSTEM

LEVEL 0 DFD FOR BANK MANGEMENT SYSTEMS

Grant access

Request for a/c details Reports

Queries Request for access

Request for member details

Grant Access


BANKING

PROJECT

USER /

ADMINISTRATOR

USER / ADMINISTRATOR

PROJECT REPORT BMS

LEVEL 1 DFD OF ADMIN MODULE

BANK DATABASE

Request a/c no & password

If Yes


ADMINISTRATORVERIFY A/c NUMBER & PASSWORD

ACCEPT

CHOICE

CHECK BALANCE

EDIT AN ACCOUNT

VIEW TRANASACTIO

N DEPOSIT/ WITHDRAW

CREATE NEW ACCOUNT

PROJECT REPORT BMS

LEVEL 1 DFD OF USER MODULE

BANK DATABASE

Request a/c no & password

If Yes


USERVERIFY A/c NUMBER & PASSWORD

ACCEPT

CHOICE

CHECK BALANCE

EDIT AN ACCOUNT

VIEW A/C DETAILS

VIEW TRANASACTIO

N

PROJECT REPORT BMS

LEVEL 2 DFD OF CREATE A NEW ACCOUNT

ESC

BANK DATABASE


ACCEPT CHOICE

NEW ACCOUNT

QUIT

ADMINISTRATOR

ACCEPT DETIALS

NEW ACCOUNT CREATED

PROJECT REPORT BMS

LEVEL 2 DFD FOR EDIT AN ACCOUNT

ESC

Store the details

BANK DATABASE


MODIFY RECORD

ACCEPT CHOICE

MODIFY

A/C

DELETE

A/C

QUIT

DELETE RECORD

ADMINISTRATOR/ USER

PROJECT REPORT BMS

LEVEL2 DFD FOR WITHDRAW OR DEPOSIT AMOUNT

BANK DATABASE

Balance amount

BANK DATABASE


ADMINISTRATOR ACCEPT CHOICE

CHECK VALID

ENTER A/C NO &

AMOUNT

DEPOSIT/ WITHDRAW

SHOW BALANCE AMOUNT

PROJECT REPORT BMS

LEVEL2 DFD FOR CHECKING BALANCE

BANK DATABASE

Returns balance

LEVEL2 DFD FOR VIEWING ACCOUNT DETAILS

BANK DATABASE


ADMINISTRATOR/

USER

CHECK VALID

ENTER A/C NO.

SHOW BALANCE AMOUNT

CHECK VALID

READ A/C NO.

ADMINISTRATOR/ USER

SHOW ACCOUNT DETAILS

PROJECT REPORT BMS

LEVEL2 DFD FOR TRANSACTION DETAILS

BANK DATABASE


CHECK VALID

READ A/C NO.

ADMINISTRATOR/ USER

SHOW TRANSACTION DETAILS

Date post:	29-Nov-2014
Category:	Documents
Upload:	nidihnrv2007
View:	406 times
Download:	4 times

Bank Management System

Documents