INTRODUCTION

The project entitled Banking Soft " which keep the day by day tally record as a
complete banking system. It can keep the information of bank employee, transactions,
loan solution, T! information and account information. The e"citing part of this project
is# it displays the employee details, payment details, loan details and transaction details.
SYNOPSIS
The project entitled Banking Soft " which keep the day by day tally record as
a complete banking system. It can keep the information of bank employee, transactions,
loan solution, T! information and account information. The e"citing part of this project
is# it displays the employee details, payment details, loan details and transaction details.
AIM
In the e"isting system the transactions are done only manually but in
proposed system we ha$e to computeri%e all the banking transaction using the software
Banking Soft.
They are&
dministrati$e !odule
ADMINISTRATIVE MODULE
This module is the main module which performs all the main operations in
the system. The major operations in the system are&
dmin login
dd'(elete')pdate *mployee
+ithdrawal'deposit'payment Transaction
,reating new ccount'-oan account'.i"ed (eposit
Searching account information'Transaction information
*/Solution T! information sa$ing
0eport generation
Settings
,hange 1assword
USER MODULE
2
This module is also a main module which performs all the main operations in the
system. The major operations in the system are&
)ser login
,reating 3ewccount'-oan ccount'.i"ed (eposit
Searching ccount Information 'Transaction Information
*/Solution T! information sa$ing
0eport generation
,hange password
SYSTEM STUDY AND ANALISYS
SYSTEM ANALYSIS
System analysis is a process of gathering and interpreting facts, diagnosing problems
and the information to recommend impro$ements on the system. It is a problem sol$ing
acti$ity that re4uires intensi$e communication between the system users and system
de$elopers. System analysis or study is an important phase of any system de$elopment
process. The system is studied to the minutest detail and analy%ed. The system analyst
plays the role of the interrogator and dwells deep into the working of the present system.
The system is $iewed as a whole and the input to the system are identified. The outputs
from the organi%ations are traced to the $arious processes. System analysis is concerned
with becoming aware of the problem, identifying the rele$ant and decisional $ariables,
analy%ing and synthesi%ing the $arious factors and determining an optimal or at least a
satisfactory solution or program of action.
detailed study of the process must be made by $arious techni4ues like inter$iews,
4uestionnaires etc. The data collected by these sources must be scrutini%ed to arri$e to a
conclusion. The conclusion is an understanding of how the system functions. This system
is called the e"isting system. 3ow the e"isting system is subjected to close study and
problem areas are identified. The designer now functions as a problem sol$er and tries to
sort out the difficulties that the enterprise faces. The solutions are gi$en as proposals. The
proposal is then weighed with the e"isting system analytically and the best one is
selected. The proposal is presented to the user for an endorsement by the user. The
proposal is re$iewed on user re4uest and suitable changes are made. This is loop that
ends as soon as the user is satisfied with proposal.
1reliminary study is the process of gathering and interpreting facts, using the
information for further studies on the system. 1reliminary study is problem sol$ing
acti$ity that re4uires intensi$e communication between the system users and system
de$elopers. It does $arious feasibility studies. In these studies a rough figure of the
system acti$ities can be obtained, from which the decision about the strategies to be
followed for effecti$e system study and analysis can be taken.

EXISTING SYSTEM
5
In the e"isting system the transactions are done only manually but in proposed
system we ha$e to computeri%e all the banking transaction using the software financial
management system.
2. 1.1 PROBLEMS WITH EXISTING SYSTEM

-ack of security of data.
!ore man power.
Time consuming.
,onsumes large $olume of pare work.
3eeds manual calculations.
3o direct role for the higher officials.
(amage of machines due to lack of attention.
To a$oid all these limitations and make the working more accurately the system needs to
be computeri%ed.
PROPOSED SYSTEM
The aim of proposed system is to de$elop a system of impro$ed facilities. The
proposed system can o$ercome all the limitations of the e"isting system. The system
pro$ides proper security and reduces the manual work.
2. 2. 1 ADVANTAGES OF THE PROPOSED SYSTEM
The system is $ery simple in design and to implement. The system re4uires $ery low
system resources and the system will work in almost all configurations. It has got
following features
Security of data.
*nsure data accuracy6s.
1roper control of the higher officials.
0educe the damages of the machines.
!inimi%e manual data entry.
!inimum time needed for the $arious processing.
7reater efficiency.
Better ser$ice.
)ser friendliness and interacti$e.
!inimum time re4uired.
2.3. FEASIBILITY STUDY
.easibility study is made to see if the project on completion will ser$e the purpose of
the organi%ation for the amount of work, effort and the time that spend on it. .easibility
study lets the de$eloper foresee the future of the project and the usefulness. feasibility
8
study of a system proposal is according to its workability, which is the impact on the
organi%ation, ability to meet their user needs and effecti$e use of resources. Thus when a
new application is proposed it normally goes through a feasibility study before it is
appro$ed for de$elopment.
The document pro$ide the feasibility of the project that is being designed and lists
$arious areas that were considered $ery carefully during the feasibility study of this
project such as Technical, *conomic and 9perational feasibilities. The following are its
features&
2.3.1. TECHNICAL FEASIBILITY
The system must be e$aluated from the technical point of $iew first. The assessment
of this feasibility must be based on an outline design of the system re4uirement in the
terms of input, output, programs and procedures. :a$ing identified an outline system, the
in$estigation must go on to suggest the type of e4uipment, re4uired method de$eloping
the system, of running the system once it has been designed.
Technical issues raised during the in$estigation are&
(oes the e"isting technology sufficient for the suggested one;
,an the system e"pand if de$eloped;
The project should be de$eloped such that the necessary functions and performance
are achie$ed within the constraints. The project is de$eloped within latest technology.
Through the technology may become obsolete after some period of time, due to the fact
that ne$er $ersion of same software supports older $ersions, the system may still be used.
So there are minimal constraints in$ol$ed with this project. The system has been
de$eloped using <a$a the project is technically feasible for de$elopment.
2.3.2. ECONOMIC FEASIBILITY
The de$eloping system must be justified by cost and benefit. ,riteria to ensure that
effort is concentrated on project, which will gi$e best, return at the earliest. 9ne of the
factors, which affect the de$elopment of a new system, is the cost it would re4uire.

The following are some of the important financial 4uestions asked during preliminary
in$estigation&
The costs conduct a full system in$estigation.
The cost of the hardware and software.
The benefits in the form of reduced costs or fewer costly errors.
=
Since the system is de$eloped as part of project work, there is no manual cost to spend
for the proposed system. lso all the resources are already a$ailable, it gi$e an indication
of the system is economically possible for de$elopment.
2.3.3. BEHAVIORAL FEASIBILITY
This includes the following 4uestions&
Is there sufficient support for the users;
+ill the proposed system cause harm;

The project would be beneficial because it satisfies the objecti$es when de$eloped and
installed. ll beha$ioral aspects are considered carefully and conclude that the project is
beha$iorally feasible.
SYSTEM DESIGN
3.1 INTRODUCTION
(esign is the first step into the de$elopment phase for any engineered product or
system. (esign is a creati$e process. good design is the key to effecti$e system. The
term design> is defined as the process of applying $arious techni4ues and principles for
the purpose of defining a process or a system in sufficient detail to permit its physical
reali%ation>. It may be defined as a process of applying $arious techni4ues and principles
for the purpose of defining a de$ice, a process or a system in sufficient detail to permit its
physical reali%ation. Software design sits at the technical kernel of the software
engineering process and is applied regardless of the de$elopment paradigm that is used.
The system design de$elops the architectural detail re4uired to build a system or product.
s in the case of any systematic approach, this software too has undergone the best
possible design phase fine tuning all efficiency, performance and accuracy le$els. The
design phase is a transition from a user oriented document to a document to the
programmers or database personnel. System design goes through two phases of
de$elopment& -ogical and 1hysical (esign.
LOGICAL DESIGN:
The logical flow of a system and define the boundaries of a system. It includes the
following steps&
0e$iews the current physical system ? its data flows, file content, $olumes ,
fre4uencies etc.
1repares output specifications ? that is, determines the format, content and
fre4uency of reports.
1repares input specifications ? format, content and most of the input functions.
1repares edit, security and control specifications.
Specifies the implementation plan.
1repares a logical design walk through of the information flow, output, input,
controls and implementation plan.
0e$iews benefits, costs, target dates and system constraints.
@
PHYSICAL DESIGN:
1hysical system produces the working systems by define the design specifications that
tell the programmers e"actly what the candidate system must do. It includes the following
steps.
(esign the physical system.
Specify input and output media.
(esign the database and specify backup procedures.
(esign physical information flow through the system and a physical design +alk
through.
1lan system implementation.
1repare a con$ersion schedule and target date.
(etermine training procedures, courses and timetable.
(e$ise a test and implementation plan and specify any new hardware'software.
)pdate benefits , costs , con$ersion date and system constraints
Desi!"S#e$i%i$&'i(! &$'i)i'ies:
,oncept formulation.
1roblem understanding.
:igh le$el re4uirements proposals.
.easibility study.
0e4uirements engineering.
rchitectural design.
MODULE DESIGN
A*+i!
The dministrator logs in using the admin login. In this administrator has the
full authority o$er the software. In this System ,the administrator has the power to add or
update or delete all the details.
Use,
The )ser logs in using the )ser login. In this module the user can successfully
enter into the software if it is a authenticated user.



INPUT DESIGN
The design of input focuses on controlling the amount of input re4uired, controlling
the errors, a$oiding delay, a$oiding e"tra steps and keeping the process simple. The input
A
is designed in such a way so that it pro$ides security and ease of use with retaining the
pri$acy. Input (esign considered the following things&
o +hat data should be gi$en as input;
o :ow the data should be arranged or coded;
o The dialog to guide the operating personnel in pro$iding input.
o !ethods for preparing input $alidations and steps to follow when error
occur.
OB-ECTIVES
Input (esign is the process of con$erting a user/oriented description of the input into a
computer/based system. This design is important to a$oid errors in the data input process
and show the correct direction to the management for getting correct information from
the computeri%ed system.
It is achie$ed by creating user/friendly screens for the data entry to handle large $olume
of data. The goal of designing input is to make data entry easier and to be free from
errors. The data entry screen is designed in such a way that all the data manipulates can
be performed. It also pro$ides record $iewing facilities.
+hen the data is entered it will check for its $alidity. (ata can be entered with the help of
screens. ppropriate messages are pro$ided as when needed so that the user will not be in
a mai%e of instant. Thus the objecti$e of input design is to create an input layout that is
easy to follow
OUTPUT DESIGN

4uality output is one, which meets the re4uirements of the end user and presents the
information clearly. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and
direct source information to the user. *fficient and intelligent output design impro$es the
system6s relationship to help user decision/making.
(esigning computer output should proceed in an organi%ed, well thought out manner#
the right output must be de$eloped while ensuring that each output element is designed so
that people will find the system can use easily and effecti$ely. +hen analysis design
computer output, they should &
Identify the specific output that is needed to meet the re4uirements.
Select methods for presenting information.
,reate document, report, or other formats that contain information produced by
the system.

3.3 DATABASE DESIGN
B
database is an organi%ed mechanism that has the capability of storing information
through which a user can retrie$e stored information in an effecti$e and efficient manner.
The data is the purpose of any database and must be protected.
The database design is a two le$el process. In the first step, user re4uirements are
gathered together and a database is designed which will meet these re4uirements as
clearly as possible. This step is called Information -e$el (esign and it is taken
independent of any indi$idual (B!S.
In the second step, this Information le$el design is transferred into a design for the
specific (B!S that will be used to implement the system in 4uestion. This step is called
1hysical -e$el (esign, concerned with the characteristics of the specific (B!S that will
be used. database design runs parallel with the system design. The organi%ation of the
data in the database is aimed to achie$e the following two major objecti$es.
(ata Integrity
(ata independence
3ormali%ation is the process of decomposing the attributes in an application, which
results in a set of tables with $ery simple structure. The purpose of normali%ation is to
make tables as simple as possible. 3ormali%ation is carried out in this system for the
following reasons.
To structure the data so that there is no repetition of data , this helps in sa$ing.
To permit simple retrie$al of data in response to 4uery and report re4uest.
To simplify the maintenance of the data through updates, insertions, deletions.
To reduce the need to restructure or reorgani%e data which new application
re4uirements arise.
RELATIONAL DATABASE MANAGEMENT SYSTEM .RDBMS/:
relational model represents the database as a collection of relations. *ach relation
resembles a table of $alues or file of records. In formal relational model terminology, a
row is called a tuple, a column header is called an attribute and the table is called a
relation. relational database consists of a collection of tables, each of which is assigned
a uni4ue name. row in a tale represents a set of related $alues.
RELATIONS0 DOMAINS 1 ATTRIBUTES:
table is a relation. The rows in a table are called tuples. tuple is an ordered set of n
elements. ,olumns are referred to as attributes. 0elationships ha$e been set between
e$ery table in the database. This ensures both 0eferential and *ntity 0elationship
Integrity. domain ( is a set of atomic $alues. common method of specifying a
domain is to specify a data type from which the data $alues forming the domain are
drawn. It is also useful to specify a name for the domain to help in interpreting its $alues.
*$ery $alue in a relation is atomic, that is not decomposable.
RELATIONSHIPS:
C
Table relationships are established using Dey. The two main keys of prime importance
are 1rimary Dey E .oreign Dey. *ntity Integrity and 0eferential Integrity 0elationships
can be established with these keys.*ntity Integrity enforces that no 1rimary Dey can ha$e
null $alues.0eferential Integrity enforces that no 1rimary Dey can ha$e null $alues.
0eferential Integrity for each distinct .oreign Dey $alue, there must e"ist a matching
1rimary Dey $alue in the same domain. 9ther key are Super Dey and ,andidate Deys.
0elationships ha$e been set between e$ery table in the database. This ensures both
0eferential and *ntity 0elationship Integrity.
NORMALI2ATION:
s the name implies, it denoted putting things in the normal form. The application
de$eloper $ia normali%ation tries to achie$e a sensible organi%ation of data into proper
tables and columns and where names can be easily correlated to the data by the user.
3ormali%ation eliminates repeating groups at data and thereby a$oids data redundancy
which pro$es to be a great burden on the computer resources. These includes&
3ormali%e the data.
,hoose proper names for the tables and columns.
,hoose the proper name for the data.
Fi,s' N(,+&3 F(,+&
The .irst 3ormal .orm states that the domain of an attribute must include only atomic
$alues and that the $alue of any attribute in a tuple must be a single $alue from the
domain of that attribute. In other words 23. disallows relations within relations> or
relations as attribute $alues within tuples>. The only attribute $alues permitted by 23.
are single atomic or indi$isible $alues.
The first step is to put the data into .irst 3ormal .orm. This can be donor by mo$ing
data into separate tables where the data is of similar type in each table. *ach table is
gi$en a 1rimary Dey or .oreign Dey as per re4uirement of the project. In this we form
new relations for each nonatomic attribute or nested relation. This eliminated repeating
groups of data.
relation is said to be in first normal form if only if it satisfies the constraints that
contain the primary key only.
Se$(!* N(,+&3 F(,+&
ccording to Second 3ormal .orm, .or relations where primary key contains multiple
attributes, no nonkey attribute should be functionally dependent on a part of the primary
key.
In this we decompose and setup a new relation for each partial key with its dependent
attributes. !ake sure to keep a relation with the original primary key and any attributes
F
that are fully functionally dependent on it. This step helps in taking out data that is only
dependant on apart of the key.
relation is said to be in second normal form if and only if it satisfies all the first
normal form conditions for the primary key and e$ery non/primary key attributes of the
relation is fully dependent on its primary key alone.
T4i,* N(,+&3 F(,+&
ccording to Third 3ormal .orm, 0elation should not ha$e a nonkey attribute
functionally determined by another nonkey attribute or by a set of nonkey attributes. That
is, there should be no transiti$e dependency on the primary key.
In this we decompose and set up relation that includes the nonkey attributes that
functionally determines other nonkey attributes. This step is taken to get rid of anything
that does not depend entirely on the 1rimary Dey.
relation is said to be in third normal form if only if it is in second normal form and
more o$er the non key attributes of the relation should not be depend on other non key
attribute.
TABLES STRUCTURE
Table& login
1rimary Dey& username
Fie3* D&'& T5#e C(!s',&i!'s Des$,i#'i(!
username ,harG2@H 1rimary key
password 3umberGFH
rights ,harG2IH
Table& employee
1rimary Dey& emp id
Fie3* D&'& T5#e C(!s',&i!'s Des$,i#'i(!
*mp no 3umberGFH 1rimary key
*mployee name charG8IH
ddress charG8IH
,ity ,harG8IH
State charG8IH
,ountry ,harG8IH
pincode number
1hone2 number
2I
1hone5 number
fa" ,harG8IH
SYSTEM DEVELOPEMENT
6.1 SYSTEM SPECIFICATION
HARDWARE RE7UIREMENTS
1rocessor & JCA ,ompatible processor with 2.B 7:% ,lock speed
0! & @25 !B or more
:ard disk & 5I 7B or more
!onitor & K7'SK7
Deyboard & 2I= Deys
!ouse & 5 buttons' 8 buttons
SOFTWARE RE7UIREMENTS
9perating System & +indows 5III'J1
.ront end & Kisual Basic A.I
Back end & !S ccess
6.2 SOFTWARE ENVIRONMENT
T4e C(!',(3 P,(#e,'ies
Before writing an e$ent procedure for the control to response to a userLs input, you ha$e
to set certain properties for the control to determine its appearance and how it will work
with the e$ent procedure. Mou can set the properties of the controls in the properties
window or at runtime.
H&!*3i! s(+e (% '4e $(++(! $(!',(3s
3.2.1 T4e Te8' B(8
The te"t bo" is the standard control for accepting input from the user as well as to display
the output. It can handle string Gte"tH and numeric data but not images or pictures. String
in a te"t bo" can be con$erted to a numeric data by using the function KalGte"tH. The
following e"ample illustrates a simple program that processes the input from the user.
22
E8&+#3e 3.1
In this program, two te"t bo"es are inserted into the form together with a few labels. The
two te"t bo"es are used to accept inputs from the user and one of the labels will be used
to display the sum of two numbers that are entered into the two te"t bo"es. Besides, a
command button is also programmed to calculate the sum of the two numbers using the
plus operator. The program use creates a $ariable sum to accept the summation of $alues
from te"t bo" 2 and te"t bo" 5.The procedure to calculate and to display the output on the
label is shown below. The output is shown in .igure 8.5
1ri$ate Sub ,ommand2N,lickGH
OTo add the $alues in te"t bo" 2 and te"t bo" 5
Sum P KalGTe"t2.Te"tH Q KalGTe"t5.Te"tH
OTo display the answer on label 2
-abel2.,aption P Sum
*nd Sub
Fi9,e 3.2

3.2.2 T4e L&:e3
The label is a $ery useful control for Kisual Basic, as it is not only used to pro$ide
instructions and guides to the users, it can also be used to display outputs. 9ne of its most
important properties is C&#'i(!. )sing the synta" 3&:e3.C&#'i(!, it can display te"t and
numeric data . Mou can change its caption in the properties window and also at runtime.
1lease refer to *"ample 8.2 and .igure 8.2 for the usage of label.
3.2.3 T4e C(++&!* B9''(!
The command button is one of the most important controls as it is used to e"ecute
commands. It displays an illusion that the button is pressed when the user click on it. The
most common e$ent associated with the command button is the ,lick e$ent, and the
synta" for the procedure is
1ri$ate Sub ,ommand2N,lick GH
Statements
*nd Sub
25
3.2.6 T4e Pi$'9,e B(8
The 1icture Bo" is one of the controls that is used to handle graphics. Mou can load a
picture at design phase by clicking on the picture item in the properties window and
select the picture from the selected folder. Mou can also load the picture at runtime using
the L(&*Pi$'9,e method. .or e"ample, the statement will load the picture grape.gif into
the picture bo".
1icture2.1ictureP-oad1icture G",&RKB programRImagesRgrape.gif"H
Mou will learn more about the picture bo" in future lessons. The image in the picture bo"
is not resi%able.

3.2.; T4e I+&e B(8
The Image Bo" is another control that handles images and pictures. It functions almost
identically to the picture bo". :owe$er, there is one major difference, the image in an
Image Bo" is stretchable, which means it can be resi%ed. This feature is not a$ailable in
the 1icture Bo". Similar to the 1icture Bo", it can also use the -oad1icture method to
load the picture. .or e"ample, the statement loads the picture grape.gif into the image
bo".
Image2.1ictureP-oad1icture G",&RKB programRImagesRgrape.gif"H
3.2.< T4e Lis' B(8
The function of the -ist Bo" is to present a list of items where the user can click and
select the items from the list. In order to add items to the list, we can use the A**I'e+
+e'4(*. .or e"ample, if you wish to add a number of items to list bo" 2, you can key in
the following statements
E8&+#3e 3.2

1ri$ate Sub .ormN-oad G H

-ist2.ddItem -esson2>
-ist2.ddItem -esson5>
-ist2.ddItem -esson8>
-ist2.ddItem -esson=>

*nd Sub
The items in the list bo" can be identified by the Lis'I!*e8 property, the $alue of the
-istInde" for the first item is I, the second item has a -istInde" 2, and the second item
has a -istInde" 5 and so on
3.2.= T4e C(+:( B(8
The function of the ,ombo Bo" is also to present a list of items where the user can click
and select the items from the list. :owe$er, the user needs to click on the small
arrowhead on the right of the combo bo" to see the items which are presented in a drop/
down list. In order to add items to the list, you can also use the A**I'e+ +e'4(*. .or
e"ample, if you wish to add a number of items to ,ombo bo" 2, you can key in the
following statements
28
E8&+#3e 3.3
1ri$ate Sub .ormN-oad G H
,ombo2.ddItem Item2>
,ombo2.ddItem Item5>
,ombo2.ddItem Item8>
,ombo2.ddItem Item=>
*nd Sub

3.2.> T4e C4e$? B(8
The ,heck Bo" control lets the user selects or unselects an option. +hen the ,heck Bo"
is checked, its $alue is set to 2 and when it is unchecked, the $alue is set to I. Mou can
include the statements ,heck2.KalueP2 to mark the ,heck Bo" and ,heck2.KaluePI to
unmark the ,heck Bo", as well as use them to initiate certain actions. .or e"ample, the
program will change the background color of the form to red when the check bo" is
unchecked and it will change to blue when the check bo" is checked. Mou will learn
about the conditional statement IfS.ThenS.*lesif in later lesson. Kb0ed and $bBlue are
color constants and Back,olor is the background color property of the form.
3.2.@ T4e O#'i(! B(8

The 9ption Bo" control also lets the user selects one of the choices. :owe$er, two or
more 9ption Bo"es must work together because as one of the 9ption Bo"es is selected,
the other 9ption Bo"es will be unselected. In fact, only one 9ption Bo" can be selected
at one time. +hen an option bo" is selected, its $alue is set to True> and when it is
unselected# its $alue is set to .alse>. In the following e"ample, the shape control is
placed in the form together with si" 9ption Bo"es. +hen the user clicks on different
option bo"es, different shapes will appear. The $alues of the shape control are I, 2, and
5,8,=,@ which will make it appear as a rectangle, a s4uare, an o$al shape, a rounded
rectangle and a rounded s4uare respecti$ely.
E8&+#3e 3.6
1ri$ate Sub 9ption2N,lick G H
Shape2.Shape P I
*nd Sub
1ri$ate Sub 9ption5N,lickGH
Shape2.Shape P 2
*nd Sub
1ri$ate Sub 9ption8N,lickGH
Shape2.Shape P 5
*nd Sub
1ri$ate Sub 9ption=N,lickGH
Shape2.Shape P 8
*nd Sub
1ri$ate Sub 9ption@N,lickGH
Shape2.Shape P =
*nd Sub
1ri$ate Sub 9ptionAN,lickGH
Shape2.Shape P @
2=
*nd Sub

3.2.1A T4e D,i)e Lis' B(8
The (ri$e -istBo" is for displaying a list of dri$es a$ailable in your computer. +hen you
place this control into the form and run the program, you will be able to select different
dri$es from your computer as shown in .igure 8.8

3.2.11 T4e Di,e$'(,5 Lis' B(8
The (irectory -ist Bo" is for displaying the list of directories or folders in a selected
dri$e. +hen you place this control into the form and run the program, you will be able to
select different directories from a selected dri$e in your computer as shown in .igure 8.=

3.2.12 T4e Fi3e Lis' B(8
The .ile -ist Bo" is for displaying the list of files in a selected directory or folder. +hen
you place this control into the form and run the program, you will be able to shown the
list of files in a selected directory as shown in .igure 8.@
Mou can coordinate the (ri$e -ist Bo", the (irectory -ist Bo" and the .ile -ist Bo" to
search for the files you want. The procedure will be discussed in later lessons.
SYSTEM IMPLEMENTATION AND TESTING
2@
;.1 CODING
!ain .orm ,oding
C4&!e P&ssB(,*
9ption *"plicit
1ublic -oginSucceeded s Boolean
1ri$ate Sub cmd,ancelN,lickGH
-oginSucceeded P .alse
)nload !e
*nd Sub
1ri$ate Sub cmd9DN,lickGH
If Te"t2.Te"t P "" 9r Te"t5.Te"t P "" 9r Te"t8.Te"t P "" 9r Te"t=.Te"t P "" Then
!sgBo" "pls fill the re4uired spaces", $b,ritical Q $b9D9nly
*"it Sub
*nd If
If Te"t2.Te"t TU login Then
!sgBo" "M9) ,3LT ,:37* T:* 1SS+90( 9. 9T:*0 )S*0S", $b,ritical Q
$b9D9nly
Te"t2.Set.ocus
*"it Sub
*nd If
L*"it Sub
+ith rsNuser
.!o$e.irst
L(o +hile 3ot .*9.
If TrimGTe"t5.Te"tH P ..ieldsG2H Then
If TrimGTe"t8.Te"tH P TrimGTe"t=.Te"tH Then
..ieldsG2H P TrimGTe"t=.Te"tH
.)pdate
..ieldsG2H P Te"t=.Te"t
!sgBo" "password changed", $b9D9nly
)nload !e
*lse
!sgBo" " 3ew 1assword is in/consistent", $bInformation
Te"t8.Set.ocus
*nd If
*lse
!sgBo" "In$alid 9ld 1assword, try againV", , "-ogin"
Te"t5.Set.ocus
*nd If
.!o$e3e"t
L-oop
*nd +ith
2A
*nd Sub
1ri$ate Sub .ormN-oadGH
,all ,onnect
Top P 5III
-eft P 8III
*nd Sub
Wi'4*,&B&3
1ri$ate Sub ,ombo2N,lickGH
+ith 0SNaccount
.!o$e.irst
+hile 3ot .*9.
If ,ombo2.-istG,ombo2.-istInde"H P ..ieldsGIH Then
Te"t5.Te"t P ..ieldsG25H
*nd If
.!o$e3e"t
+end
*nd +ith
*nd Sub
1ri$ate Sub cleaallGH
Te"t2.Te"t P ""
Te"t5.Te"t P ""
Te"t8.Te"t P ""
Te"t=.Te"t P ""
,ombo2.-istInde" P /2
Te"t2.Set.ocus
*nd Sub
1ri$ate Sub ,ommand=N,lickGH
!in P 5III
actual P KalGTe"t5.Te"tH
dep P KalGTe"t8.Te"tH
final P actual / dep
Te"t=.Te"t P final
If KalGTe"t=.Te"tH T 2III Then
temp P !sgBo"G"mount ,anLt Be -ess Than 2III", $b,ritical Q $b9D9nly,
"utoBank"H
*"it Sub
cleaall
*nd If
2B
+ith 0SNaccount
.!o$e.irst
.)pdate
..ieldsG25H P Te"t=.Te"t
.!o$e3e"t
*nd +ith
+ith 0SNtransaction
.dd3ew
..ieldsGIH P Te"t2.Te"t
..ieldsG2H P ,ombo2.Te"t
..ieldsG5H P "+ithdrawal"
..ieldsG8H P Te"t5.Te"t
..ieldsG=H P Te"t8.Te"t
..ieldsG@H P Te"t@.Te"t
..ieldsGAH P Te"t=.Te"t
.)pdate
*nd +ith
!sgBo" "Mour ccount has being (ebited by " E Te"t8.Te"t E ", Mour final balance is "
E Te"t=.Te"t, $bInformation, "ccount (eposit"
cleaall
*nd Sub
1ri$ate Sub ,ommand@N,lickGH
cleaall
!e.:ide
*nd Sub
1ri$ate Sub .ormN-oadGH
,all ,onnect
+ith 0SNaccount
+hile 3ot .*9.

,ombo2.ddItem ..ieldsGIH

.!o$e3e"t
+end
*nd +ith
Te"t@.Te"t P .ormatG(ate E TimeH

*nd Sub
Res93'
1ri$ate Sub ,ommand=N,lickGH
2C
If 3ot t"tNid.Te"t P "" Then
data.,ommand2 t"tNid.Te"t
(ata0eport8.Show
t"tNid.Te"t P ""
!e.:ide
*lse
t"tNid.Set.ocus
*nd If
*nd Sub
A**L(&!
1ri$ate Sub ,heck2NDey1ressGDeyscii s IntegerH
If Deyscii P 28 Then
If ,heck2.Kalue P 2 Then
Te"t=.*nabled P True
Te"t@.*nabled P True
Te"tA.*nabled P True
-abel=.*nabled P True
-abel@.*nabled P True
-abelA.*nabled P True
Te"t=.Set.ocus
*lseIf ,heck2.Kalue P I Then
Te"t=.*nabled P .alse
Te"t@.*nabled P .alse
Te"tA.*nabled P .alse
-abel=.*nabled P .alse
-abel@.*nabled P .alse
-abelA.*nabled P .alse
,ommand5.Set.ocus
*nd If
*nd If
*nd Sub
1ri$ate Sub ,ommand2N,lickGH
+ith 0SNloan
(im id s String
(im code s String
id P "-3"
temp P 2III
temp P temp Q 0SNloan.0ecord,ount Q 2
code P id Q "/" Q ,StrGtempH
Te"t2.Te"t P code
.rame2.*nabled P True
*nd +ith
Te"t5.Set.ocus
*nd Sub
2F
1ri$ate Sub ,ommand5N,lickGH
.rame2.*nabled P .alse
If !sgBo"G"re Mou Sure;", $bWuestion Q $bMes3o, "uotBank"H P $bMes Then
If check TU $b9D Then
+ith 0SNloan
.dd3ew

..ieldsGIH P Te"t2.Te"t
..ieldsG2H P Te"t5.Te"t
..ieldsG5H P Te"t8.Te"t
..ieldsG8H P Te"tB.Te"t
..ieldsG=H P -abelC.,aption
..ieldsG@H P -oanSegment.,aption
..ieldsGAH P -oanType.,aption
..ieldsGBH P Te"tC.Te"t
Select ,ase term
,ase FI
..ieldsGCH P FI
maturitydate P (ate Q FI
..ieldsGFH P maturitydate

,ase A
..ieldsGCH P A
maturitydate P (ate Q 2CI
..ieldsGFH P maturitydate

,ase 2
..ieldsGCH P 2
maturitydate P (ate Q 8A@
..ieldsGFH P maturitydate

,ase 5
..ieldsGCH P 5
maturitydate P (ate Q 8A@ Q 8A@
..ieldsGFH P maturitydate

*nd Select
..ieldsG2IH P Te"t=.Te"t
..ieldsG22H P Te"t@.Te"t
..ieldsG25H P Te"tA.Te"t
.)pdate
!sgBo" "Mour 0e4uest has being sent for $erification", $bInformation, "-oan
pplication .orm"
!sgBo" "Mou shall be contacted as soon as the $erification is complete",
$bInformation, "-oan pplication .orm"
cleaall
*"it Sub
*nd +ith
*nd If
5I
*nd If
.rame2.*nabled P .alse
*nd Sub
1ri$ate Sub ,ommand8N,lickGH
)nload !e
*nd Sub
1ri$ate Sub .ormN-oadGH
,all ,onnect
.rame2.*nabled P .alse
-abelC.,aption P .ormatG(ateH E " " E GTimeH
*nd Sub
1ublic Sub cleaallGH
Te"t2.Te"t P ""
Te"t8.Te"t P ""
Te"t5.Te"t P ""
Te"tB.Te"t P ""
.rame5.*nabled P .alse
.rameA.*nabled P .alse
Te"t=.Te"t P ""
Te"t@.Te"t P ""
Te"tA.Te"t P ""
Te"tC.Te"t P ""
Te"tF.Te"t P ""
Te"t=.*nabled P .alse
Te"t@.*nabled P .alse
Te"tA.*nabled P .alse
-abel=.*nabled P .alse
-abel@.*nabled P .alse
-abelA.*nabled P .alse
.rame2.*nabled P .alse
,ommand2.Set.ocus
*nd Sub
1ri$ate Sub (ata,ombo2NDey1ressGDeyscii s IntegerH
If Deyscii P 28 Then
If (ata,ombo2.Te"t P "" Then
(ata,ombo2.Set.ocus
*"it Sub
*nd If
Te"t8.Set.ocus
*nd If
*nd Sub
1ri$ate Sub option2AN,lickGH
52
term P FI
maturitydate P (ate Q FI
Te"tF.Te"t P maturitydate
*nd Sub
1ri$ate Sub option2BN,lickGH
term P A
maturitydate P (ate Q 2CI
Te"tF.Te"t P maturitydate
*nd Sub
1ri$ate Sub option2CN,lickGH
maturitydate P (ate Q 8A@
Te"tF.Te"t P maturitydate
term P 2
*nd Sub
1ri$ate Sub option2FN,lickGH
maturitydate P (ate Q 8A@ Q 8A@
Te"tF.Te"t P maturitydate
term P 5
*nd Sub
1ri$ate Sub 9ption2N,lickGH
Set -oanType P 9ption2
,heck2.Set.ocus
Te"tC.Te"t P @IIII
*nd Sub
1ri$ate Sub 9ption2IN,lickGH
If Deyscii P 28 Then
9ption25.Set.ocus
*nd If
*nd Sub
1ri$ate Sub 9ption22NclickGH
If Deyscii P 28 Then
9ption25.Set.ocus
*nd If
*nd Sub
1ri$ate Sub 9ption25N,lickGH
Set -oanType P 9ption25
,heck2.Set.ocus
Te"tC.Te"t P 5@IIII
*nd Sub
1ri$ate Sub 9ption28N,lickGH
Set -oanType P 9ption25
55
,heck2.Set.ocus
Te"tC.Te"t P @IIIII
*nd Sub
1ri$ate Sub 9ption2=N,lickGH
Set -oanType P 9ption25
,heck2.Set.ocus
Te"tC.Te"t P 2IIIIII
*nd Sub
1ri$ate Sub 9ption2@N,lickGH
Set -oanType P 9ption25
,heck2.Set.ocus
Te"tC.Te"t P 2@IIIII
*nd Sub
1ri$ate Sub 9ption5N,lickGH
,heck2.Set.ocus
Set -oanType P 9ption5
Te"tC.Te"t P 2IIIII
*nd Sub
1ri$ate Sub 9ption8N,lickGH
,heck2.Set.ocus
Set -oanType P 9ption8
Te"tC.Te"t P 5IIIII
*nd Sub
1ri$ate Sub 9ption=N,lickGH
,heck2.Set.ocus
Set -oanType P 9ption=
Te"tC.Te"t P 8IIIIII
*nd Sub
1ri$ate Sub 9ption@N,lickGH
,heck2.Set.ocus
Set -oanType P 9ption@
Te"tC.Te"t P 5@III
*nd Sub
1ri$ate Sub 9ptionAN,lickGH
,heck2.Set.ocus
Set -oanType P 9ptionA
Te"tC.Te"t P 2IIIII
58
*nd Sub
1ri$ate Sub 9ptionBN,lickGH
,heck2.Set.ocus
Set -oanType P 9ptionB
Te"tC.Te"t P 5IIIII
*nd Sub
1ri$ate Sub 9ptionCN,lickGH
.rameA.*nabled P .alse
.rame5.*nabled P True
9ption2.Set.ocus
Set -oanSegment P 9ptionC
*nd Sub
1ri$ate Sub 9ptionFN,lickGH
.rame5.*nabled P .alse
.rameA.*nabled P True
9ption2I.Set.ocus
Set -oanSegment P 9ptionF
*nd Sub
1ri$ate Sub Te"t8NDey1ressGDeyscii s IntegerH
If Deyscii P 28 Then
If KalGTe"t8.Te"tH T 5III Then
!sgBo" "VVV mount ,anLt Be -ess Then 5III VVV", $b,ritical Q $b9D9nly,
"utoBank"
Te"t8.Set.ocus
SendDeys "X:omeYQX*ndY"
*"it Sub
*nd If
Te"t8.Te"t P KalGTe"t8.Te"tH
9ptionC.Set.ocus
*nd If
*nd Sub
1ri$ate Sub Te"t=NDey1ressGDeyscii s IntegerH
If Deyscii P 28 Then
Te"t=.Te"t P ),aseGTe"t=.Te"tH
Te"t@.Set.ocus
*nd If
*nd Sub
1ri$ate Sub Te"t@NDey1ressGDeyscii s IntegerH
If Deyscii P 28 Then
Te"t@.Te"t P ),aseGTe"t@.Te"tH
Te"tA.Set.ocus
*nd If
*nd Sub
1ri$ate Sub Te"tANDey1ressGDeyscii s IntegerH
If Deyscii P 28 Then
5=
Te"tA.Te"t P ),aseGTe"tA.Te"tH
,ommand5.Set.ocus
*nd If
*nd Sub
1ri$ate .unction checkGH
(im temp s Integer
If ,heck2.Kalue P 2 N
nd Te"t=.Te"t P "" N
nd Te"t@.Te"t P "" N
nd Te"tA.Te"t P "" Then
temp P !sgBo"G"VVV3o dditional 3ame .oundVVV", $b9D9nly Q $b,ritical,
"utoBank"H
*nd If
check P temp
*nd .unction
;.2 SYSTEM IMPLEMENTATION AND TESTING
Implementation is the stage of the project where the theoretical design is turned into a
working system. It can be considered to be the most crucial stage in achie$ing a
successful new system gaining the users confidence that the new system will work and
will be effecti$e and accurate. It is primarily concerned with user training and
documentation. ,on$ersion usually takes place about the same time the user is being
trained or later. Implementation simply means con$ening a new system design into
operation, which is the process of con$erting a new re$ised system design into an
operational one.
5@
;.2.1. SYSTEM TESTING
Software Testing is the process of e"ecuting software in a controlled manner, in order
to answer the 4uestion / (oes the software beha$e as specified;. Software testing is often
used in association with the terms $erification and $alidation. Kalidation is the checking
or testing of items, includes software, for conformance and consistency with an
associated specification. Software testing is just one kind of $erification, which also uses
techni4ues such as re$iews, analysis, inspections, and walkthroughs. Kalidation is the
process of checking that what has been specified is what the user actually wanted.
Kalidation : re we doing the right job;
Kerification : re we doing the job right;
Software testing should not be confused with debugging. (ebugging is the process of
analy%ing and locali%ing bugs when software does not beha$e as e"pected. lthough the
identification of some bugs will be ob$ious from playing with the software, a methodical
approach to software testing is a much more thorough means for identifying bugs.
(ebugging is therefore an acti$ity which supports testing, but cannot replace testing.
9ther acti$ities which are often associated with software testing are static analysis and
dynamic analysis. Static analysis in$estigates the source code of software, looking for
problems and gathering metrics without actually e"ecuting the code. (ynamic analysis
looks at the beha$ior of software while it is e"ecuting, to pro$ide information such as
e"ecution traces, timing profiles, and test co$erage information.
Testing is a set of acti$ity that can be planned in ad$anced and conducted
systematically. Testing begins at the module le$el and work towards the integration of
entire computers based system. 3othing is complete without testing, as it $ital success of
the system testing objecti$es, there are se$eral rules that can ser$e as testing objecti$es.
They are

Testing is a process of e"ecuting a program with the intend of finding an error. good test
case is one that has high possibility of finding an undisco$ered error. successful test is
one that unco$ers an undisco$ered error.

If a testing is conducted successfully according to the objecti$es as stated abo$e, it
would unco$ered errors in the software also testing demonstrate that the software
function appear to be working according to the specification, that performance
re4uirement appear to ha$e been met.

There are three ways to test program.
.or correctness
.or implementation efficiency
.or computational comple"ity

Test for correctness are supposed to $erify that a program does e"actly what it was
designed to do. This is much more difficult than it may at first appear, especially for large
programs.
5A
TEST PLAN
test plan implies a series of desired course of action to be followed in accomplishing
$arious testing methods. The Test 1lan acts as a blue print for the action that is to be
followed. The software engineers create a computer program, its documentation and
related data structures. The software de$elopers is always responsible for testing the
indi$idual units of the programs, ensuring that each performs the function for which it
was designed. There is an independent test group GIT7H which is to remo$e the inherent
problems associated with letting the builder to test the thing that has been built. The
specific objecti$es of testing should be stated in measurable terms. So that the mean time
to failure, the cost to find and fi" the defects, remaining defect density or fre4uency of
occurrence and test work/hours per regression test all should be stated within the test
plan.
The le$els of testing include&
)nit testing
Integration Testing
(ata $alidation Testing
9utput Testing
UNIT TESTING
)nit testing focuses $erification effort on the smallest unit of software design ? the
software component or module. )sing the component le$el design description as a guide,
important control paths are tested to unco$er errors within the boundary of the module.
The relati$e comple"ity of tests and unco$ered scope established for unit testing. The unit
testing is white/bo" oriented, and step can be conducted in parallel for multiple
components. The modular interface is tested to ensure that information properly flows
into and out of the program unit under test. The local data structure is e"amined to ensure
that data stored temporarily maintains its integrity during all steps in an algorithm6s
e"ecution. Boundary conditions are tested to ensure that all statements in a module ha$e
been e"ecuted at least once. .inally, all error handling paths are tested.
Tests of data flow across a module interface are re4uired before any other test is
initiated. If data do not enter and e"it properly, all other tests are moot. Selecti$e testing
of e"ecution paths is an essential task during the unit test. 7ood design dictates that error
conditions be anticipated and error handling paths set up to reroute or cleanly terminate
processing when an error does occur. Boundary testing is the last task of unit testing step.
Software often fails at its boundaries.
)nit testing was done in Sell/Soft System by treating each module as separate entity
and testing each one of them with a wide spectrum of test inputs. Some flaws in the
internal logic of the modules were found and were rectified.
INTEGRATION TESTING
5B
Integration testing is systematic techni4ue for constructing the program structure
while at the same time conducting tests to unco$er errors associated with interfacing. The
objecti$e is to take unit tested components and build a program structure that has been
dictated by design. The entire program is tested as whole. ,orrection is difficult because
isolation of causes is complicated by $ast e"panse of entire program. 9nce these errors
are corrected, new ones appear and the process continues in a seemingly endless loop.
fter unit testing in Sell/Soft System all the modules were integrated to test for any
inconsistencies in the interfaces. !oreo$er differences in program structures were
remo$ed and a uni4ue program structure was e$ol$ed.
VALIDATION TESTING OR SYSTEM TESTING
This is the final step in testing. In this the entire system was tested as a whole with all
forms, code, modules and class modules. This form of testing is popularly known as
Black Bo" testing or System testing.
Black Bo" testing method focuses on the functional re4uirements of the software.
That is, Black Bo" testing enables the software engineer to deri$e sets of input conditions
that will fully e"ercise all functional re4uirements for a program.
Black Bo" testing attempts to find errors in the following categories# incorrect or
missing functions, interface errors, errors in data structures or e"ternal data access,
performance errors and initiali%ation errors and termination errors.
OUTPUT TESTING OR USER ACCEPTANCE TESTING
The system considered is tested for user acceptance# here it should satisfy the firm6s
need. The software should keep in touch with perspecti$e system# user at the time of
de$eloping and making changes whene$er re4uired. This done with respect to the
following points
Input Screen (esigns,
9utput Screen (esigns,
9nline message to guide the user and the like.
The abo$e testing is done taking $arious kinds of test data. 1reparation of test data plays
a $ital role in the system testing. fter preparing the test data, the system under study is
tested using that test data. +hile testing the system by which test data errors are again
unco$ered and corrected by using abo$e testing steps and corrections are also noted for
future use.
;.3. TRAINING
9nce the system is successfully de$eloped the ne"t important step is to ensure that the
administrators are well trained to handle the system. This is because the success of a
system in$ariably depends on how they are operated and used. The implementation
5C
depends upon the right people being at the right place at the right time. *ducation
in$ol$es creating the right atmosphere and moti$ating the user. The administrators are
familiari%ed with the run procedures of the system, working through the se4uence of
acti$ities on an ongoing basis.
Implementation is the state in the project where the theoretical design is turned into a
working system. By this, the users get the confidence that the system will work
effecti$ely. The system can be implemented only after through testing.
The systems personnel check the feasibility of the system. The actual data were
inputted to the system and the working of the system was closely monitored. The master
option was selected from the main menu and the actual data were input through the
corresponding input screens. The data mo$ement was studied and found to be correct
4ueries option was then selected and this contains $arious reports. )tilities pro$ide
$arious data needed for in$entory was input and the module was test run. Satisfactory
results were obtained. 0eports related to these processes were also successfully
generated. Karious input screen formats are listed in the appendi".
Implementation walkthroughs ensure that the completed system actually sol$es the
original problem. This walkthrough occurs just before the system goes into use, and it
should include careful re$iew of all manuals, training materials and system
documentation. gain, users, the analyst and the members of the computer ser$ices staff
may attend this meeting.


APPENDIX
SCREEN SHOTS
L(i!
5F
H(+e
A** E+#3(5ee
8I
U#*&'e Me+:e,
82
T,&!s&$'i(!
85
De#(si'
88
P&5+e!'
8=
A$$(9!' I!%(,+&'i(!
L(&! A##3i$&'i(!
8@
Fi8e* De#(si' I!%(,+&'i(!
8A
ccount Information
8B
T,&!s&$'i(! L(
8C
CONCLUSION
Banking Soft " keeps the day by day tally record as a complete banking system. It can
keep the information of bank employee, transactions, loan solution, T! information and
account information. The e"citing part of this project is# it displays the employee details,
payment details, loan details and transaction details.
BIBLIOGRAPHY
B99DS&
1. ,harles :ampfed G5IIIH OKisual Basic6 )ni$ersity of
Toronto
2. :erbert Schildt G5IIIH OKisual Basic A.I6 Tata !c7raw :ill
3. <ohn Zukowski G5IIIH OKisual Basic A.I6 OB1B 1ublications
6. <amie <aworsky OKisual Basic A.I6Techmedia
;. Stefen (enninger OKisual Basic A.I6uthor6s 1ress
<. Ian Somer$ille OSoftware engineering6
=. 0ajee$ mall OSoftware engineering6
>. *lmasri 3a$athe O.undamentals of database systems6
ONLINE REFERENCE:
www.w8schools.com
www.theser$erside.com
www.$isual.com
8F
=I