VIDYA VIJAY BAL MANDIR SCHOOL

A PROJECT ON BANK MANAGEMENT SYSTEM A PROJECT SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR DEPARTMENT OF COMMERCE 2013-2014

SUBMITTED TO : M ! SURAJ JAIS"AL

S#$%&''() B*: RAJNI KHORE CLASS : +II COMMERCE

B,-. M,-,/(%(-' S*0'(%

ACKNO"LEDGEMENT
"&'1 C,-)2 ,-) P3(,0# ( I ',.( 2442 '#-&'* '2 (54 (00 %* 0&-6( ( '1,-.0 ,-) 2$3&/,'&2- '2 %* (0'((%() /#&)( S# ,7 J,&08,3! I' &0 $(6,#0( 29 1&0 ,$3( ,-) %,'# ( /#&),-6( ,-) 62-24( ,'&2- 8&'12#' 81&61 &' 82#3) -2' 1,:( $((4200&$3( 92 %( '2 62%43('( %* 4 27(6'! I' &0 %* 43(,0,-' )#'* '2 '1,-. ,33 '1( 0',99 %(%$( 29 '1( 62%4#'( 6(-'( 812 -(:( 1(0&','() %( 9 2% '&%( )# &-/ '1( 4 27(6'! F&-,33*; I / ,'(9#33* ,6.-283()/( '1( 0#442 '; (-62# ,/(%(-' < 4,'&(-6( 29 %* 9,%&3*; A-) ,0 ,38,*0; -2'1&-/ &- %* 3&9( 82#3) $( 4200&$3( 8&'12#' G2); T1,-. Y2#=

PREFACE
This is a Project work undertaken in context of partial fulfillment of the Department of computers. Since Bank is associated with the lives of common people and their day to day routines so I decided to work on this project. The manual handling of the record is time consuming and highly prone to error. The purpose of this project is to automate the process of day to day activities like ew !ccount "pening# Daily Transactions# and $odification. The complete set of rules % procedures related to $anaging Baking day to day activities and generating report is called &B! ' $! !()$) T S*ST)$+ .$y project giving a ,rief idea regarding automated ,ank. I found it is ,etter to work with T-.B" /00 % its 1I2)S facility as data,ase storage. It is 3uite difficult to maintain Data,ase in Tur,o /00 instead the availa,ility of !//)SS % ".!/2) etc. having uni3ue capa,ility of handling large data,ase in efficient manner.

I have tried my ,est to make the complicated process of Bank $anagement System as simple as possi,le using Structured % $odular techni3ue % $enu oriented interface. I have tried to design the software in such a way that user may not have any difficulty in using this package % further expansion is possi,le without much effort. )ven though I cannot claim that this work to ,e entirely exhaustive# the main purpose of my exercise is perform each Bank activity in computeri4ed way rather than manually which is time consuming. I am confident that this software package can ,e readily used ,y non5programming personal avoiding human handled chance of error

INTRODUCTION
The project entitled &Bank Management System 6 which keep the day ,y day tally record as a complete ,anking system. It can keep the information of ,ank customers# transactions and account information. The exciting part of this project is7 it displays the employee details# reports and transaction details.

SYSTEM STUDY AND ANALISYS 2!1 SYSTEM ANALYSIS System analysis is a process of gathering and interpreting facts# diagnosing pro,lems and the information to recommend improvements on the system. It is a pro,lem solving activity that re3uires intensive communication ,etween the system users and system developers. System analysis or study is an important phase of any system development process. The system is studied to the minutest detail and analy4ed. The system analyst plays the role of the interrogator and dwells deep into the working of the present system. The system is viewed as a whole and the input to the system are identified. The outputs from the organi4ations are traced to the various processes. System analysis is concerned with ,ecoming aware of the pro,lem# identifying the relevant and decisional varia,les# analy4ing and synthesi4ing the various factors and determining an optimal or at least a satisfactory solution or program of action. ! detailed study of the process must ,e made ,y various techni3ues like interviews# 3uestionnaires etc. The data collected ,y these sources must ,e scrutini4ed to arrive to a conclusion. The conclusion is an understanding of how the system functions. This system is called the existing system. ow the existing system is su,jected to close study and pro,lem areas are identified. The designer now functions as a pro,lem solver and tries to sort out the difficulties that the
6

enterprise faces. The solutions are given as proposals. The proposal is then weighed with the existing system analytically and the ,est one is selected. The proposal is presented to the user for an endorsement ,y the user. The proposal is reviewed on user re3uest and suita,le changes are made. This is loop that ends as soon as the user is satisfied with proposal. Preliminary study is the process of gathering and interpreting facts# using the information for further studies on the system. Preliminary study is pro,lem solving activity that re3uires intensive communication ,etween the system users and system developers. It does various feasi,ility studies. In these studies a rough figure of the system activities can ,e o,tained# from which the decision a,out the strategies to ,e followed for effective system study and analysis can ,e taken.

2!2 AIM In the existing system the transactions are done only manually ,ut in proposed system we have to computeri4e all the ,anking transaction using this software. They are8 !dministrative $odule 2!3 E+ISTING SYSTEM In the existing system the transactions are done only manually ,ut in proposed system we have to computeri4e all the ,anking transaction using the software financial management system. 2!3!1 PROBLEMS "ITH E+ISTING SYSTEM 2ack of security of data. $ore man power. Time consuming. 2arge volume of paper work. eeds manual calculations. o direct role for the higher officials.
7

To avoid all these limitations and make the working more accurately the system needs to ,e computeri4ed. 2!4 PROPOSED SYSTEM The aim of proposed system is to develop a system of improved facilities. The proposed system can overcome all the limitations of the existing system. The system provides proper security and reduces the manual work.

2!4!1 ADVANTAGES OF THE PROPOSED SYSTEM The system is very simple in design and to implement. The system re3uires very low system resources and the system will work in almost all configurations. It has got following features Security of data. )nsure data accuracy9s. Proper control of the higher officials. .educe the damages of the machines. $inimi4e manual data entry. $inimum time needed for the various processing. (reater efficiency. Better service. -ser friendliness and interactive. $inimum time re3uired.

2!> FEASIBILITY STUDY

1easi,ility study is made to see if the project on completion will serve the purpose of the organi4ation for the amount of work# effort and the time that spend on it. 1easi,ility study lets the developer foresee the future of the project and the usefulness. ! feasi,ility study of a system proposal is according to its worka,ility# which is the impact on the organi4ation# a,ility to meet their user needs and effective use of resources. Thus when a new application is proposed it normally goes through a feasi,ility study ,efore it is approved for development. The document provide the feasi,ility of the project that is ,eing designed and lists various areas that were considered very carefully during the feasi,ility study of this project such as Technical# )conomic and "perational feasi,ilities. The following are its features8

TECHNICAL FEASIBILITY The system must ,e evaluated from the technical point of view first. The assessment of this feasi,ility must ,e ,ased on an outline design of the system re3uirement in the terms of input# output# programs and procedures. :aving identified an outline system# the investigation must go on to suggest the type of e3uipment# re3uired method developing the system# of running the system once it has ,een designed. Technical issues raised during the investigation are8 Does the existing technology sufficient for the suggested one; /an the system expand if developed;

The project should ,e developed such that the necessary functions and performance are achieved within the constraints. The project is developed within latest technology. Through the technology may ,ecome o,solete after some period of time# due to the fact that never version of same software supports older versions# the system may still ,e used. So there are minimal constraints involved with this project. The system has ,een developed using <ava the project is technically feasi,le for development. ECONOMIC FEASIBILITY The developing system must ,e justified ,y cost and ,enefit. /riteria to ensure that effort is concentrated on project# which will give ,est# return at the earliest. "ne of the factors# which affect the development of a new system# is the cost it would re3uire. The following are some of the important financial 3uestions asked during preliminary investigation8 The costs conduct a full system investigation. The cost of the hardware and software. The ,enefits in the form of reduced costs or fewer costly errors. Since the system is developed as part of project work# there is no manual cost to spend for the proposed system. !lso all the resources are already availa,le# it give an indication of the system is economically possi,le for development. BEHAVIORAL FEASIBILITY This includes the following 3uestions8 Is there sufficient support for the users; =ill the proposed system cause harm; The project would ,e ,eneficial ,ecause it satisfies the o,jectives when developed and installed. !ll ,ehavioral aspects are considered carefully and conclude that the project is ,ehaviorally feasi,le.

10

SYSTEM DESIGN 3!1 INTRODUCTION Design is the first step into the development phase for any engineered product or system. Design is a creative process. ! good design is the key to effective system. The term &design+ is defined as &the process of applying various techni3ues and principles for the purpose of defining a process or a system in sufficient detail to permit its physical reali4ation+. It may ,e defined as a process of applying various techni3ues and principles for the purpose of defining a device# a process or a system in sufficient detail to permit its physical reali4ation. Software design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm that is used. The system design develops the architectural detail re3uired to ,uild a system or product. !s in the case of any systematic approach# this software too has undergone the ,est possi,le design phase fine tuning all efficiency# performance and accuracy levels. The design phase is a transition from a user oriented document to a document to the programmers or data,ase personnel. System design goes through two phases of development8 2ogical and Physical Design.

11

3!2 LOGICAL DESIGN: The logical flow of a system and define the ,oundaries of a system. It includes the following steps8 .eviews the current physical system > its data flows# file content# volumes# fre3uencies etc. Prepares output specifications > that is# determines the format# content and fre3uency of reports. Prepares input specifications > format# content and most of the input functions. Prepares edit# security and control specifications. Specifies the implementation plan. Prepares a logical design walk through of the information flow# output# input# controls and implementation plan. .eviews ,enefits# costs# target dates and system constraints. 3!3 PHYSICAL DESIGN: Physical system produces the working systems ,y define the design specifications that tell the programmers exactly what the candidate system must do. It includes the following steps. Design the physical system. Specify input and output media. Design the data,ase and specify ,ackup procedures. Design physical information flow through the system and a physical design =alk through. Plan system implementation. Prepare a conversion schedule and target date. Determine training procedures# courses and timeta,le. Devise a test and implementation plan and specify any new hardware?software. -pdate ,enefits # costs # conversion date and system constraints

3!3!1 D(0&/-?S4(6&9&6,'&2- ,6'&:&'&(0:

12

/oncept formulation. Pro,lem understanding. :igh level re3uirements proposals. 1easi,ility study. .e3uirements engineering. !rchitectural design.

3!4 MODULE DESIGN 3!4!1 ADMINISTRATIVE MODULE This module is the main module which performs all the main operations in the system. The major operations in the system are8 !dmin login !dd?Delete?-pdate /ustomers =ithdrawal?deposit Transaction /reating new !ccount @Saving !ccount# .ecurring !ccount# /urrent !ccountsA Searching account information?Transaction information .eport generation Settings 3!4!2 CUSTOMER MODULE This module is the main module which performs some specific operations in the system. The operations in the system are8 /ustomer login Searching account information?Transaction information .eports

13

3!> INPUT DESIGN The design of input focuses on controlling the amount of input re3uired# controlling the errors# avoiding delay# avoiding extra steps and keeping the process simple. The input is designed in such a way so that it provides security and ease of use with retaining the privacy. Input Design considered the following things8 "1,' ),', 012#3) $( /&:(- ,0 &-4#'@ H28 '1( ),', 012#3) $( , ,-/() 2 62)()@ T1( )&,32/ '2 /#&)( '1( 24( ,'&-/ 4( 02--(3 &- 4 2:&)&-/ &-4#'! M('12)0 92 4 (4, &-/ &-4#' :,3&),'&2-0 ,-) 0'(40 '2 923328 81(- ( 2 266# !

3!A OBJECTIVES Input Design is the process of converting a user5oriented description of the input into a computer5,ased system. This design is important to avoid errors in the data input process and show the correct direction to the management for getting correct information from the computeri4ed system. It is achieved ,y creating user5friendly screens for the data entry to handle large volume of data. The goal of designing input is to make data entry easier and to ,e free from errors. The data entry screen is designed in such a way that all the data manipulates can ,e performed. It also provides record viewing facilities. =hen the data is entered it will check for its validity. Data can ,e entered with the help of screens. !ppropriate messages are provided as when needed so that the user will not ,e in mai4e of instant. Thus the o,jective of input design is to create an input layout that is easy to follow

3!B SYSTEM REQUIREMENT 3!B!1 HARD"ARE REQUIREMENTS Processor 8 BCD /ompati,le processor with E.F (:4 /lock speed

14

.!$

8 GEH $B or more HI (B or more J(!?SJ(! 8 8 EIK 'eys

:ard disk 8 $onitor 'ey,oard $ouse 8

H ,uttons? L ,uttons REQUIREMENTS

3!B!2 SOFT"ARE

"perating System 8 =indows HIII?BP 1ront end 8 Jisual Basic D.I Back end 8 $S !ccess 3!B!3 SOFT"ARE ENVIRONMENT T1( C2-' 23 P 24( '&(0 Before writing an event procedure for the control to response to a userMs input# you have to set certain properties for the control to determine its appearance and how it will work with the event procedure. *ou can set the properties of the controls in the properties window or at runtime. H,-)3&-/ 02%( 29 '1( 62%%2- 62-' 230

T1( T(5' B25 The text ,ox is the standard control for accepting input from the user as well as to display the output. It can handle string @textA and numeric data ,ut not images or pictures. String in a text ,ox can ,e converted to a numeric data ,y using the function Jal@textA. The following example illustrates a simple program that processes the input from the user. E5,%43( In this program# two text ,oxes are inserted into the form together with a few la,els. The two text ,oxes are used to accept inputs from the user and one of the la,els

15

will ,e used to display the sum of two num,ers that are entered into the two text ,oxes. Besides# a command ,utton is also programmed to calculate the sum of the two num,ers using the plus operator. The program use creates a varia,le sum to accept the summation of values from text ,ox E and text ,ox H.The procedure to calculate and to display the output on the la,el is shown ,elow. The output is shown in 1igure L.H Private Su, /ommandEN/lick@A OTo add the values in text ,ox E and text ,ox H Sum P Jal@TextE.TextA 0 Jal@TextH.TextA OTo display the answer on la,el E 2a,elE./aption P Sum )nd Su,

F&/# ( 3!2

T1( L,$(3 The la,el is a very useful control for Jisual Basic# as it is not only used to provide instructions and guides to the users# it can also ,e used to display outputs. "ne of its most important properties is C,4'&2-. -sing the syntax 3,$(3!C,4'&2-# it can display text and numeric data . *ou can change its caption in the properties window and also at runtime. Please refer to )xample L.E and 1igure L.E for the usage of la,el. T1( C2%%,-) B#''2-

16

The command ,utton is one of the most important controls as it is used to execute commands. It displays an illusion that the ,utton is pressed when the user click on it. The most common event associated with the command ,utton is the /lick event# and the syntax for the procedure is Private Su, /ommandEN/lick @A Statements )nd Su,

T1( P&6'# ( B25 The Picture Box is one of the controls that is used to handle graphics. *ou can load a picture at design phase ,y clicking on the picture item in the properties window and select the picture from the selected folder. *ou can also load the picture at runtime using the L2,)P&6'# ( method. 1or example# the statement will load the picture grape.gif into the picture ,ox. PictureE.PictureP2oadPicture @6/8QJB programQImagesQgrape.gif6A *ou will learn more a,out the picture ,ox in future lessons. The image in the picture ,ox is not resi4a,le.

T1( I%,/( B25 The Image Box is another control that handles images and pictures. It functions almost identically to the picture ,ox. :owever# there is one major difference# the image in an Image Box is stretcha,le# which means it can ,e resi4ed. This feature is not availa,le in the Picture Box. Similar to the Picture Box# it can also use the 2oadPicture method to load the picture. 1or example# the statement loads the picture grape.gif into the image ,ox. ImageE.PictureP2oadPicture @6/8QJB programQImagesQgrape.gif6A

T1( C2%$2 B25 The function of the /om,o Box is also to present a list of items where the user can click and select the items from the list. :owever# the user needs to click on the small arrowhead on the right of the com,o ,ox to see the items which are

17

presented in a drop5down list. In order to add items to the list# you can also use the A))I'(% %('12). 1or example# if you wish to add a num,er of items to /om,o ,ox E# you can key in the following statements E5,%43( Private Su, 1ormN2oad @ A /om,oE.!ddItem &ItemE+ /om,oE.!ddItem &ItemH+ /om,oE.!ddItem &ItemL+ /om,oE.!ddItem &ItemK+ )nd Su, T1( C1(6. B25 The /heck Box control lets the user selects or unselects an option. =hen the /heck Box is checked# its value is set to E and when it is unchecked# the value is set to I. *ou can include the statements /heckE.JaluePE to mark the /heck Box and /heckE.JaluePI to unmark the /heck Box# as well as use them to initiate certain actions. 1or example# the program will change the ,ackground color of the form to red when the check ,ox is unchecked and it will change to ,lue when the check ,ox is checked. *ou will learn a,out the conditional statement IfR.ThenR.)lesif in later lesson. J,.ed and v,Blue are color constants and Back/olor is the ,ackground color property of the form. T1( O4'&2- B25 The "ption Box control also lets the user selects one of the choices. :owever# two or more "ption Boxes must work together ,ecause as one of the "ption Boxes is selected# the other "ption Boxes will ,e unselected. In fact# only one "ption Box can ,e selected at one time. =hen an option ,ox is selected# its value is set to &True+ and when it is unselected7 its value is set to &1alse+. In the following example# the shape control is placed in the form together with six "ption Boxes. =hen the user clicks on different option ,oxes# different shapes will appear. The values of the shape control are I# E# and H#L#K#G which will make it appear as a rectangle# a s3uare# an oval shape# a rounded rectangle and a rounded s3uare respectively.

18

>! SYSTEM IMPLEMENTATION AND TESTING Implementation is the stage of the project where the theoretical design is turned into a working system. It can ,e considered to ,e the most crucial stage in achieving a successful new system gaining the users confidence that the new system will work and will ,e effective and accurate. It is primarily concerned with user training and documentation. /onversion usually takes place a,out the same time the user is ,eing trained or later. Implementation simply means convening a new system design into operation# which is the process of converting a new revised system design into an operational one. >!1! SYSTEM TESTING Software Testing is the process of executing software in a controlled manner# in order to answer the 3uestion 5 Does the software ,ehave as specified;. Software testing is often used in association with the terms verification and validation. Jalidation is the checking or testing of items# includes software# for conformance and consistency with an associated specification. Software testing is just one kind of verification# which also uses techni3ues such as reviews# analysis# inspections# and walkthroughs. Jalidation is the process of checking that what has ,een specified is what the user actually wanted. Jalidation : !re we doing the right jo,; Jerification : !re we doing the jo, right; Software testing should not ,e confused with de,ugging. De,ugging is the process of analy4ing and locali4ing ,ugs when software does not ,ehave as expected. !lthough the identification of some ,ugs will ,e o,vious from playing with the software# a methodical approach to software testing is a much more thorough means for identifying ,ugs. De,ugging is therefore an activity which supports testing# ,ut cannot replace testing. "ther activities which are often associated with software testing are static analysis and dynamic analysis. Static analysis investigates the source code of software# looking for pro,lems and gathering metrics without actually executing the code. Dynamic analysis

19

looks at the ,ehavior of software while it is executing# to provide information such as execution traces# timing profiles# and test coverage information. Testing is a set of activity that can ,e planned in advanced and conducted systematically. Testing ,egins at the module level and work towards the integration of entire computers ,ased system. othing is complete without testing# as it vital success of the system testing o,jectives# there are several rules that can serve as testing o,jectives. They are Testing is a process of executing a program with the intend of finding an error.! good test case is one that has high possi,ility of finding an undiscovered error.! successful test is one that uncovers an undiscovered error. If a testing is conducted successfully according to the o,jectives as stated a,ove# it would uncovered errors in the software also testing demonstrate that the software function appear to ,e working according to the specification# that performance re3uirement appear to have ,een met. There are three ways to test program. 1or correctness 1or implementation efficiency 1or computational complexity Test for correctness are supposed to verify that a program does exactly what it was designed to do. This is much more difficult than it may at first appear# especially for large programs.

>!1!1 TEST PLAN ! test plan implies a series of desired course of action to ,e followed in accomplishing various testing methods. The Test Plan acts as a ,lue print for the action that is to ,e followed. The software engineers create a computer program# its documentation and related data structures. The software developers is always responsi,le for testing the individual units of the programs# ensuring that each performs the function for which it was designed. There is an independent test group @IT(A which is to remove the inherent pro,lems associated with letting the
20

,uilder to test the thing that has ,een ,uilt. The specific o,jectives of testing should ,e stated in measura,le terms. So that the mean time to failure# the cost to find and fix the defects# remaining defect density or fre3uency of occurrence and test work5hours per regression test all should ,e stated within the test plan. The levels of testing include8 -nit testing Integration Testing Data validation Testing "utput Testing

>!1!2 UNIT TESTING -nit testing focuses verification effort on the smallest unit of software design > the software component or module. -sing the component level design description as a guide# important control paths are tested to uncover errors within the ,oundary of the module. The relative complexity of tests and uncovered scope esta,lished for unit testing. The unit testing is white5,ox oriented# and step can ,e 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 examined to ensure that data stored temporarily maintains its integrity during all steps in an algorithm9s execution. Boundary conditions are tested to ensure that all statements in a module have ,een executed at least once. 1inally# all error handling paths are tested. Tests of data flow across a module interface are re3uired ,efore any other test is initiated. If data do not enter and exit properly# all other tests are moot. Selective testing of execution paths is an essential task during the unit test. (ood design dictates that error conditions ,e 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 ,oundaries. -nit testing was done in Sell5Soft System ,y 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.

21

>!1!3 INTEGRATION TESTING Integration testing is systematic techni3ue for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The o,jective is to take unit tested components and ,uild a program structure that has ,een dictated ,y design. The entire program is tested as whole. /orrection is difficult ,ecause isolation of causes is complicated ,y vast expanse of entire program. "nce these errors are corrected# new ones appear and the process continues in a seemingly endless loop. !fter unit testing in Sell5Soft System all the modules were integrated to test for any inconsistencies in the interfaces. $oreover differences in program structures were removed and a uni3ue program structure was evolved. >!1!4 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 Box testing or System testing. Black Box testing method focuses on the functional re3uirements of the software. That is# Black Box testing ena,les the software engineer to derive sets of input conditions that will fully exercise all functional re3uirements for a program. Black Box testing attempts to find errors in the following categories7 incorrect or missing functions# interface errors# errors in data structures or external data access# performance errors and initiali4ation errors and termination errors. >!1!> OUTPUT TESTING OR USER ACCEPTANCE TESTING The system considered is tested for user acceptance7 here it should satisfy the firm9s need. The software should keep in touch with perspective system7 user at the time of developing and making changes whenever re3uired. This done with respect to the following points Input Screen Designs# "utput Screen Designs#
22

 "nline message to guide the user and the like. The a,ove testing is done taking various kinds of test data. Preparation of test data plays a vital role in the system testing. !fter preparing the test data# the system under study is tested using that test data. =hile testing the system ,y which test data errors are again uncovered and corrected ,y using a,ove testing steps and corrections are also noted for future use. >!2 TRAINING "nce the system is successfully developed the next important step is to ensure that the administrators are well trained to handle the system. This is ,ecause the success of a system invaria,ly depends on how they are operated and used. The implementation depends upon the right people ,eing at the right place at the right time. )ducation involves creating the right atmosphere and motivating the user. The administrators are familiari4ed with the run procedures of the system# working through the se3uence of activities on an ongoing ,asis. 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 effectively. The system can ,e implemented only after through testing. The systems personnel check the feasi,ility 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 movement was studied and found to ,e correct 3ueries option was then selected and this contains various reports. -tilities provide various data needed for inventory was input and the module was test run. Satisfactory results were o,tained. .eports related to these processes were also successfully generated. Jarious input screen formats are listed in the appendix. Implementation walkthroughs ensure that the completed system actually solves the original pro,lem. This walkthrough occurs just ,efore the system goes into use# and it should include careful review of all manuals# training materials and system documentation. !gain# users# the analyst and the mem,ers of the computer services staff may attend this meeting.

23

CONCLUSION &Bank $anagement System 6 keeps the day ,y day tally record as a complete ,anking system. It can keep the information of ,ank employee# transactions# loan solution# !T$ information and account information. The exciting part of this project is7 it displays the employee details# payment details# loan details and transaction details.

24

BIBLIOGRAPHY B""'S8 E. Software )ngineering H. Jisual Basic D.I

25