09CSA10

Banking System
Contents
Phase 1

Project Analysis and Planning

1.1.

Study of the Problem

1.2.

1.3.

Project Scope

Objectives

Phase 2

Cost Estimation

Phase 3

Modeling the Requirements

3.1.

Module Description
3.1.1. Login
3.1.2. Deposit

Details

And

Withdraw

Amount

3.1.3. Balance Details

3.1.4. Modify
3.2.

UML Diagram
3.2.1. Use

case

Diagram

3.2.2. Class

Diagram

3.2.3.

Sequence Diagram
3.2.4. Collaboration Diagram
Phase 4

Configuration Management
4.1.

S/W Requirements
4.2.

H/W Requirements
4.3.

4.4.

Tools

Software Development
4.4.1. Form Creation
4.4.2. Script

Phase 5

Software Testing
5.1.

Preparing Test Plan

5.2.

Perform Validation Testing

5.3.

Validation Test Criteria

09CSA10
5.4.

Coverage Analysis
5.5.

Memory Leaks

Synopsis
This is a small scale project for banking system .The basic idea of this
system is the manager of the bank can maintains the details about the customers,
withdraw and deposit amount. It consists of customer details, banking system,
balance details. The manager of the bank can enter the customers account number
and get the amount details of that particular customer. In banking system we can
calculate the customers account balance based on withdraw and deposit amount.
In the customer details module various details like account number, Name,
deposit amount, withdraw amount, balance are obtained from the user. In the
Display module the total database is displayed. In the balance Details module, the
individual database is displayed which shows the balance details of the particular
customer. By using the Modify module we can modify and update the customer
details on the database stored.

09CSA10

Phase 1 Project Analysis and Planning

1.1.

Study of the Problem

The banking system is critical to businesses and other organizations because of the

significant amounts of money involved in customers withdraw or deposit process. This is a

small scale project for banking process. The basic idea is that the manager of the bank maintains
the information such as banks name, its branches all over. The customer details maintain the
Customers account_number , Name along with personal information. The balance details
determine by the deposit and withdraw amount of the customer. This banking system involves
with two types of users.

USER

ADMINISTRATOR

USERS ROLE:
The users can login/logout the database. He/She can view his/her personal details,
balance details. The user can just view the information where as he/she could not make changes
in the database.
ADMINISTRATOR ROLE:
The administrator plays a vital role in the banking system. The administrator controls the
entire database. The balance calculations are calculated by the administrator itself. The main role
of the administrator is to safeguard the database.

1.2.

Project Scope
The supplementary specification applies to banking process. This specification defines

the non-functional requirement of the system such as:

Functionality:
Since it stand alone application, a single user may use it at a time.
Usability:
Desktop interface
Windows 98/2000/Xp

09CSA10
Reliability:
The system is available at 24 hours a day, seven days a week.
Performance:
The performance depends on hardware specification

1.3.

Objectives
The purpose of this document is to define the requirements of banking system. This

supplementary specification lists the requirements that are not readily captured in the use case
model. Supplementary specification and the use case model capture a complete set of
requirement of the system.

Phase 2 Cost Estimation

An estimate is a prediction based upon probabilistic assessment. It is the responsibility of
the project manager to make accurate estimations of effort and cost. This is particularly true for
projects subject to competitive bidding where a bid too high compared with competitors would
result in loosing the contract or a bid too low could result in a loss to the organization. This does
not mean that internal projects are unimportant. From a project leaders estimate the management
often decide whether to proceed with the project. Industry has a need for accurate estimates of
effort and size at a very early stage in a project. However, when software cost estimates are done
early in the software development process the estimate can be based on wrong or incomplete
requirements. A software cost estimate process is the set of techniques and procedures that
organizations use to arrive at an estimate. An important aspect of software projects is to know the
cost, The major contributing factor is effort.
Why SCE is difficult and error prone ?

Software cost estimation requires a significant amount of effort to perform it correctly.

SCE is often done hurriedly, without an appreciation for the effort required.

You need experience at developing estimates, especially for large projects.

Human bias i.e An Estimator is likely to consider how long a certain portion of the
system would take, and then to merely extrapolate this estimate to the rest of the system,
ignoring the non-linear aspects of software development.

09CSA10
The causes of poor and inaccurate estimation

New software projects are nearly always different form the last.

Software practitioners don't collect enough information about past projects.

Estimates are forced to match the resources available.

2.1. Cost and Pricing

Our project is of high range and is highly efficient which can satisfy the payroll calculation
for almost all software companies. The chances of error occurrence is very limited and so our
costs around Rs 10, 00,000(app).

A team of 12 members is required for completing the task.

It takes a time span of 3 weeks to shape the project.

There are no specific environmental constraints.

Phase 3 Modeling the Requirements

3.1.

Module Description
3.1.1. Login
It is the login session for the Administrator, User and Exit.
3.1.2.

Deposit And Withdraw Amount Details

It is used to know the withdraw and deposit amounts of the customer.

3.1.3. Balance Details

It is used to determine the balance details.
3.1.4. Modify
It is used to modify and any update the database.

3.2.

UML Diagram
3.2.1. Use case Diagram
Use Case diagrams show the various activities the users can perform on the

system. The System is something that performs a function. They model the dynamic aspects of
the system. It provides a users perspective of the system.

09CSA10
Actor:
An actoris a user of the system playing a particular role.
Use case:
Use case is a particular activity a user can do on the system.
Relationship:
Relationships are simply illustrated with a line connecting actors to use cases.

login

account creation

withdraw
customer

bank

deposit

get account balance

account details

db

3.2.2. Class Diagram

A class diagram describes the types of objects in the system and the various kinds
of static relationships that exist among them.i.e.,A graphical representation of a static view on

09CSA10
declarative static elements.A class is the description of a set of objects having similar attributes,
operations, relationships and behavior.

customer1
name : variant
password : variant
account no : variant

bank1
name : variant
age : variant
password : variant

login()
withdraw()
deposit()

account creation()

database
account no : variant
password : variant
balance : variant
print()
update()

3.2.3. Sequence Diagram

A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order. It is a
construct of a message sequence chart. Sequence diagrams are sometimes called event diagrams,
event scenarios, and timing diagrams

09CSA10

3.2.4. Collaboration Diagram

A Collaboration diagram is very similar to a Sequence diagram in the purpose it
achieves; in other words, it shows the dynamic interaction of the objects in a system. A
distinguishing feature of a Collaboration diagram is that it shows the objects and their association
with other objects in the system apart from how they interact with each other. The association
between objects is not represented in a Sequence diagram.

09CSA10
A Collaboration diagram is easily represented by modeling objects in a system and representing
the associations between the objects as links. The interaction between the objects is denoted by
arrows. To identify the sequence of invocation of these objects, a number is placed next to each
of these arrows.

1: create an account
4: login
7: withdraw/deposit

8: check account details

9: withdraw/deposit

customer
bank

6: provide request details

3: account created
11: get money/receipt
10: updated

2: account updated
5: request to provide service
database

Phase 4 Configuration Management

Configuration management is also used in software development, where it is called
Unified Configuration Management (UCM). Using UCM, developers can keep track of the
source code, documentation, problems, changes requested, and changes made. An advantage of a
configuration management application is that the entire collection of systems can be reviewed to
make sure any changes made to one system do not adversely affect any of the other systems

09CSA10

4.1.

S/W Requirements
OS: Windows
Language: Visual Basic

4.2.

H/W Requirements
Intel PII Processor with 300 MHz speed.
64 MB RAM
10MB Hard disk space

4.3.

Tools
Design Tool: Rational Rose suite

4.4.

Software Development
4.4.1. Form creation

Form 1:

09CSA10

Form 2:

Form 3:

09CSA10
Form 4:

Form 5:

09CSA10
Form 6:

4.4.2 Script
Coding for form1:
Private Sub Command1_Click()
Form2.Show
Unload Me
End Sub
Private Sub Command2_Click()
End
End Sub
Coding for Form 2:
Private Sub Command5_Click()
If (Text1.Text = "raje") Then
Form3.Show
Unload Me
ElseIf (Text1.Text = "") Then
MsgBox ("Enter your Pincode")
Else
MsgBox ("Incorrect pincodepls enter correctly")
Text1.Text = ""
End If
End Sub

09CSA10
Private Sub Command6_Click()
Form1.Show
End Sub
Coding for Form 3:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
Form4.Show
Unload Me
End Sub
Private Sub Command2_Click()
Form5.Show
Unload Me
End Sub
Private Sub Command3_Click()
Form6.Show
Unload Me
End Sub
Private Sub Command4_Click()
Form7.Show
Unload Me
End Sub
Private Sub Command6_Click()
Form1.Show
Unload Me
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("Z:\VB\atm.mdb")
Set rs = db.OpenRecordset("accounts")
End Sub

Coding for Form 4:

Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
Form3.Show

09CSA10
Unload Me
End Sub
Private Sub Command2_Click()
Form1.Show
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("Z:\VB\atm.mdb")
Set rs = db.OpenRecordset("accounts")
Text1.Enabled = False
Text1.Text = rs.Fields(0)
End Sub
Coding for Form 5:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
Text1.Text = ""
End Sub
Private Sub Command2_Click()
rs.Edit
rs(2) = Text1.Text
rs.Update
rs.Edit
rs(0) = rs(0) + rs(2)
rs.Update
MsgBox "deposit successfully", vbOKOnly
Text1.Text = ""
End Sub
Private Sub Command3_Click()
Data1.Refresh
Unload Me
Form3.Show
End Sub
Private Sub Command4_Click()
Unload Me
Form1.Show
End Sub
Private Sub Form_Load()
Text1.Text = ""
Set db = OpenDatabase("Z:\VB\atm.mdb")
Set rs = db.OpenRecordset("accounts")
Command2.Enabled = False

09CSA10
End Sub
Private Sub Text1_Change()
Command2.Enabled = True
End Sub
Coding for Form 6:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
Text1.Text = ""
End Sub
Private Sub Command2_Click()
rs.Edit
rs(1) = Text1.Text
rs.Update
rs.Edit
rs(0) = rs(0) - rs(1)
rs.Update
MsgBox "withdraw successfully", vbOKOnly
Text1.Text = ""
End Sub
Private Sub Command3_Click()
Form3.Refresh
Data1.UpdateRecord
Unload Me
Form3.Show
End Sub
Private Sub Command4_Click()
Unload Me
Form1.Show
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("Z:\VB\atm.mdb")
Set rs = db.OpenRecordset("accounts")
Text1.Text = ""
Command2.Enabled = False
End Sub
Private Sub Text1_Change()
Command2.Enabled = True
End Sub

09CSA10

Phase 5 Software Testing

5.1.

Preparing Test Plan

Preparing test plan is the first step in the last phase of software development cycle

.The test plan consists of all the activities that had to be done in the software testing phase. This
test plan has been documented using the rational test manager software.
5.2.

Perform Validation Testing

Software is completely assembled as a package interfacing errors have been

uncovered and a final series of software test validation testing may begin. Validation successive
when the customer is satisfied.
5.3.

Validation Test Criteria

Software validation is achieved through a series of black box test that

demonstrates conformity with requirements.

5.4.

Coverage Analysis

Coverage analysis is used to identify untested code. Using rational pure coverage,
untested code can easily be identified.
5.5.

Memory Leaks
Memory leak testing has been done using rational purity software.

Result:
Based on the system requirements specification BANKING INFORMATION SYSTEM
has been designed and implemented.