LinkedIn SlideShare

Upload
Login
Signup
Search
Home Technology Education More Topics For Uploaders Collect Leads
Prepared by: Manish Najkani(10BCA38)
Rahul Nath(10BCA40)Nitish Xavier Tirkey
(10BCA52)
Submitted to:
BCA ...
ACKNOWLEDGEMENT I am thankful to all the faculty members, providing theirvaluab
le time and guidance in elaborating view of...
AbstractRequirements definition and management is recognized as a necessary ste
pin the delivery of successful systems and ...
Table of Contents1. Introduction of the Project 1.1. Project Objective 1.2.
Project Benefit 1.3. Project Scope 1.4...
1.1.
Project Objective
To allow only authorized user to access var
ious function and
processed a...
The failure of a larger institution could have serious ramifications for
the entire system in that if one universa...
System development Life cycle consist of two major steps of Systemanalysis and
design. It includes set of activities that ...
How the present system works?
What all drawbacks are in the present system?
Wha
t is their vision about the new syste...
system investigation is being considered. The project request must be examined
to determine precisely what the originator...
This billing software is technically feasible. The primarytechnical requirement
includes the availability of Windows 2000 ...
Windows OS: Version 2000 or XP; Source: Microsoft forClient
Visual Basi
c: Version 6.0 and above; Source: Microsoft...
was required to go through the various operations. The user just
needed t
o have the basic knowledge of computers. ...
Reviewing organization documents
Onsite observations
Conducting interviews 2.2.
1. Reviewing
...
information about the present workflow, objects and people was
gathered.
This helped me to understand various...
User Interface
Communication Interface3.1.1. User Interface
The various
documents that are maintained by the R...
It should be able to adequately serve as training material for new
project
members, imparting them enough informatio...
TransactionFlow chart
ACC. NO.
ADDRESS.
NAME
BALANCE. START BANK
h ...
START
CUSTOMER
has
has
F
IXED
ACCOUNT
...
TRANSACTION
CUSTOMER
CURRENT BALANCE
DEBI
T
CREDIT
UP...
Testing & Debugging
Testing is a process of executing the program with the
intent of finding errors and it establishe...
Integration testing is performed after all the software units are combinedtoget
her. The objective here is to test the soft...
Implementation & consequently maintenance was notincluded as part of our projec
t.
Testing Process
APPENDIX5.1. References Books: System Analysis & Design Elias M.Awad (Galgot
ia Publication) Microsoft Access
...
6 of 25
SYNOPSIS ON BANK MANAGEMENT SYSTEM

69,726
Share Like Download
Nitish Xavier Tirkey
Nitish Xavier Tirkey
Follow
0 43 0 10
Published on Sep 20, 2012
Published in: Education, Economy & Finance, Business
8 Comments
37 Likes
Statistics
Notes
no profile picture user
Share your thoughts...
Post
abdulsamad1420 Abdussamad Ahmad Ibrahim Argungu , Student / Programmer at Aptec
h Computer Education
hello please can you help us wit the source code ?
1 week ago
akshitavarshney1 Akshita Varshney , Student at Invertis University (OffiCial)
thanku
i want this....
2 years ago
sonuasati sonu asati , Software Developer at MWT PVT LTD. at MWT PVT LTD
thanks
2 years ago
mvvinodh Vin Vinodh
thanks
2 years ago
nitishxavier11 Nitish Xavier Tirkey at Nitish Xavier Tirkey
Thanks Vikram Gaurh
2 years ago
Show More
SYNOPSIS ON BANK MANAGEMENT SYSTEM
1. Prepared by: Manish Najkani(10BCA38) Rahul Nath(10BCA40)Nitish Xavier Tirkey(
10BCA52) Submitted to: BCA DEPT. Renu Kewalramani Class: SY BCA Sem-IV
2. ACKNOWLEDGEMENT I am thankful to all the faculty members, providing theirvalu
able time and guidance in elaborating view of studying theproject details and ge
tting the right vision for its implementation. I am also thankful to Mrs. Renu K
ewalramani, who is having avast knowledge of DBMS, System Analysis and Design &P
rogramming concepts which are the building block of project. I also thank Mr. Sa
mir Thakkar, our H.O.D., and all otherfaculty members who are directly or indire
ctly involved with ourproject. I am also pleased with the support and co-operati
on of thelab in charge in order to make use of the free lab slots.
3. AbstractRequirements definition and management is recognized as a necessary s
tepin the delivery of successful systems and software projects, discipline isals
o required by standards, regulations, and quality improvement initiatives.Creati
ng and managing requirements is a challenge of IT, systems andproduct developmen
t projects or indeed for any activity where you have tomanage a contractual rela
tionship. Organization need to effectively defineand manage requirements to ensu
re they are meeting needs of the customer,while proving compliance and staying o
n the schedule and within budge.The impact of a poorly expressed requirement can
bring a business out ofcompliance or even cause injury or death. Requirements d
efinition andmanagement is an activity that can deliver a high, fast return on i
nvestment.The BANK MANAGEMENT SYSTEM undertaken as a project is basedon relevant
technologies. The main aim of this project is to developsoftware for bank manag
ement system. This project is to develop softwarefor bank management system. Thi
s project has been developed to carry outthe processes easily and quickly, which

is not possible with the manualssystems, which are overcome by this software. T
his project is developedusing VB language and. Hence it provides the complete so
lution for thecurrent management system.
4. Table of Contents1. Introduction of the Project 1.1. Project Objective 1.2. P
roject Benefit 1.3. Project Scope 1.4. Project Limitation2. System Development L
ife Cycle 2.1. Preliminary Investigation 2.1.1. Request Clarification 2.1.2. Fea
sibility Study 2.1.2.1. Technical Feasibility 2.1.2.2. Economical Feasibility 2.
1.2.3. Operational Feasibility 2.1.3. Request Approval 2.2. Determination of Sys
tem Requirements3. System Design 3.1. Interface Design 3.1.1. User Interface 3.1
.2. Communication Interface 3.2. Detailed System Specification 3.2.1. Detailed S
ystem Design 3.2.1.1 Functional Flow of System 3.2.1.2 Data Flow of System4. Tes
ting & Debugging5. Appendix 5.1. References Introduction of the Project
5. 1.1. Project Objective
To allow only authorized user to access various functi
on and processed available in the system.
Locate any A/C wanted by the user. Red
uced clerical work as most of the work done by computer. Provide greater speed &
reduced time consumption.1.2. Project Benefits Some benefits are:
Access to pri
vilege banking zone
Dedicated Relationship Manager International Debit Card with
insurance coverage
Facility to link with current account
Anywhere Banking with
higher limits Daily account balance alerts Multi-city cheque book with 25 leaves
1.3. Project Scope Banking activities are considered to be the life blood of the
national Economy. Without banking services, trading and business activities can
not be carried on smoothly. Banks are the distributors and protectors of liquid
capital which is of vital significance to a developing country. Efficient admini
stration of the banking system helps in the economic Growth of the nation. Banki
ng is useful to trade and commerce.1.4. Project Limitation
6. The failure of a larger institution could have serious ramifications for the
entire system in that if one universal bank were to collapse, it could lead to a
systemic financial crisis.
Universal bankers may be tempted to take excessive r
isks. Banks may deploy their own assets in securities with consequent risk to co
mmercial and savings deposits. Vulnerable to high risks due to investment bankin
g activities coupled with focus on commercial banking activities.
Unsound loans
may be made in order to shore up the price of securities or the financial positi
on of companies in which a bank had invested its own assets.System Development L
ife Cycle Implementation Preliminary Investigation Determination of System Testi
ng Requirements Developm ent of Design of System System
7. System development Life cycle consist of two major steps of Systemanalysis an
d design. It includes set of activities that analysts, designers andusers carry
out to develop and implement an information system. So, here we followed the dif
ferent stages of system development lifecycle to develop Billing Software effici
ently. The systems development life cycle consists of the followingactivities: 1
. Preliminary Investigation 2. Determination Requirements 3. Design of System 4.
Development of System 5. System Testing 6. Implementation2.1. Preliminary Inves
tigation For this, the need arises to understand the viewpoint of two important
entities Top management and users. In order to gather pertinent information, I in
terviewed the TopManagement and asked the following questions:
8. How the present system works?
What all drawbacks are in the present system?
W
hat is their vision about the new system?
What specific facilities they want fro
m new system, those are currently not in scope of existing system? How will data
flow in the system? Who will be authenticated to access data and his/her access
rights? To find more about present system s working mechanism such as the ways of
getting inputs and providing outputs, I interviewed the current users of the sy
stem by asking following question: Are they comfortable with the present system?
What flaws exists in the current system?
Do they feel the necessity of new syst
em? What will be their requirements from new system?
Are they satisfied with the
ir role in new system?After carrying out these interviews, I drew conclusion abo
ut the TopManagement s requirements and whether users are in support of the newsys
tem.This activity is consisting of three parts:-2.1.1. Request Clarification As
previously stated, the requests are made from employees and users in the organiz
ation, which are not clearly stated, therefore a
9. system investigation is being considered. The project request must be examine

d to determine precisely what the originator wants. My project is basically mean

t for Receipt & Revenue section so taking in to consideration of all these tasks
; the corresponding development came in to existence.2.1.2. Feasibility Study Fe
asibility study tried to determine whether a given solution would work or not. I
ts main objective is not to solve the problem, but to acquire its scope. It focu
ses on following:
Meet user requirements Best utilization of available resources
Develop a cost effective system
Develop a technically feasible system It is fur
ther classified into 3 aspects:- 2.1.2.1. Technical Feasibility Issues to be stu
died are, whether the work for the project will be done with current equipment,
existing S/W technology and available personnel? If the new technology is requir
ed, then what is the likelihood that it can be developed?
10. This billing software is technically feasible. The primarytechnical requirem
ent includes the availability of Windows 2000 orhigher version of operating syst
ems installed in the network. MSAccess is also required which was already instal
led. To developprograms VB 6.0 was required which was also available. Reliabilit
y,access power and data security was also available. The system can alsobe devel
oped if the new technology is acquired. Thus, through all theends technical feas
ibility was met. The tools that we were requiring were all available to us theya
re:- Hardware Requirements Server Machine: Minimum p-3, 256 MB RAM, 20 GB Hard D
isk Client Machine: Minimum p-3, 128 MB RAM, 8 GB Hard Disk Printer: 132 columns
High Speed Dot Matrix Printer with local language support Software Requirements
Windows OS: Version 2000 and above; Source: Microsoft forServer
11. Windows OS: Version 2000 or XP; Source: Microsoft forClient Visual Basic: Ve
rsion 6.0 and above; Source: Microsoft MS-Access: Version 2000 and above; Source
: Microsoft2.1.2.2. Economic Feasibility Issues to be studied are, whether the n
ew system is costeffective or not? The benefits in the form of reduced cost? Thi
s billing software is economically feasible. As thehardware was installed from q
uite beginning, the cost on project ofhardware is low. Similarly, the software l
oaded for this project wasused even after this project was developed for many ot
her applications.The software cost was under budget. Moreover, the technicalrequ
irements were already available so there was no furtherexpenditure for buying so
ftware packages.2.1.2.3. Operational Feasibility Issues to be studied are, is th
ere sufficient support for managementand users? Is the current method acceptable
to users? Will theproposed system cause any harm? This billing software is oper
ationally feasible. This applicationprovides the necessary information to the us
er such as how to enter theinformation regarding different operations performed
on the database.The application was planned in such a way that no prior knowledg
e
12. was required to go through the various operations. The user just needed to h
ave the basic knowledge of computers. This software also possesses behavioral fe
asibility. It s because the users of the system are computer professionals and kno
w the advantages of computer system. Moreover, this application is going to enha
nce their skills and reduce their workloads. 2.1.3. Request Approval Not all the
requested projects are desirable or feasible. However, those that are both feas
ible and desirable should be put into scheduled. After the project is approved,
its cost, priority, completion time and personnel requirements are estimated and
used to determine where to add it to any project list. The Top Management revie
wed the above factors and gave their ascent. After the consent to request approv
al, the design was taken up.2.2. Determination of System Requirement Determinati
on of system requirement means studying the adjacent system in order to collect
the details regarding the way it captures data, processes the data, produces the
output. I used following techniques for identifying system requirements:
13. Reviewing organization documents
Onsite observations
Conducting interviews 2
.2.1. Reviewing OrganizationDocuments I first learnt about the organization invo
lved in, or affected by the project, I got to know how the department works and
the employees were directly involved/associated with the application. Annual man
uals and reports were of great help to me. 2.2.2.. Onsite Observations It is a p
rocess of recognizing and observing people, objects and their occurrence to obta
in the information. The major objective of the Onsite Observation is to get as c
lose as possible to real system being studied. Here, I observed the activities o

f the system directly. I saw the office environment, workload on the system, and
workload on the users. The physical layout of the current system along with the
location & movement of staff was analyzed. In this way, the
14. information about the present workflow, objects and people was gathered. Thi
s helped me to understand various procedures & processes, which were to be devel
oped in the new system. 2.2.3. Conducting Interviews Written documents and onsit
e observation just tell that how the system should operate. They do not include
enough details to allow a decision to be made about the merits of system proposa
l, nor do they present user views about the current system. I conducted intervie
ws of the staff, which were directly involved with the application. Also the reg
ular users of the application were interviewed. Based on their viewpoints, cryst
al clear system requirements were jolted down. These interviews were of great he
lp. Design of System3.1. Interface Design A well-designed interface improves the
user perception of the content or services. It needs not to be flashy but it sh
ould be ergonomically sound. Two main types of design interface, which I conside
red, are:
15.
User Interface
Communication Interface3.1.1. User Interface The various docu
ments that are maintained by the RR section that have been used to analyze the u
ser interfaces that will interact with the billing software. The billing softwar
e consists of many modules and these modules consist of various sub modules, whi
ch provides the user with various facilities.3.1.2. Communication Interface The
software may either be installed on a client server based setup with a Local Are
a Network (using the Ethernet Interface, one to one connection and TCP/IP) or on
a standalone machine whereby client and server components resides on the same m
achine.3.2. Detailed Design SpecificationComplete design specification serves th
e following purposes:
16. It should be able to adequately serve as training material for new project m
embers, imparting them enough information and understanding about the project im
plementation.
It should serve as Objective Evidence that the designers and/or impl
ementers are following through on their commitment to implement the functionalit
y described in their requirements specifications. 3.2.1. Detailed Design The des
ign that we have formed for the new system are given as under:-3.2.1.2 Data Flow
Diagram:0-Level DFD Account No User Account Details Bank System
17. TransactionFlow chart
18. ACC. NO. ADDRESS. NAME BALANCE. START BANK h CUSTOMER as TRANSACTION Done by
DEBIT CREDIT
19. START
20. CUSTOMER has has FIXED ACCOUNT DEPOSITE AMOUNT ID. NO. DURATION BALANCE ACC.
ID.Transaction Process
21. TRANSACTION CUSTOMER CURRENT BALANCE DEBIT CREDIT UPDATE BALANCE UPDATE BALA
NCE BALANCE
22. Testing & Debugging Testing is a process of executing the program with the i
ntent of finding errors and it establishes confidence that the program does what
it is suppose to do. Testing can be performed in two ways:- Unit Testing:It is
testing of individual module. Before initiating unit testing, it mustbe ensured
that the code is peer previewed. Integration Testing:
23. Integration testing is performed after all the software units are combinedto
gether. The objective here is to test the software interfaces. Projectteam condu
cts the integration testing. Before entering integrationtesting, it may be ensur
ed that code review and unit testing have beenperformed on the individual softwa
re modules. I conducted the unit testing for finding errors and the results of t
he unit testing are recorded and action initiated for rectification of the error
s/defects. VALIDATION Almost every field in the database which is sensitive i.e.
responsible for some important changes are validated. Basically we validated th
e field as such is numeric and the length in case of the primary keys and also u
sed the Data base to complete most of the details once entered at the data entry
time, So that while performing the transaction at faster rate also the user is
not going to face any problems or can make any sort of blunders in the fine, sta
tus, book no that can be issued, and other important fields. Mostly the validati
on is carried out in the lost focus, click, change and other similar events wher

e the entered value is compared with the one stored in the database and if there
is duplication to occur or no match with the database then the entry is to be r
emoved and user is prompt to reenter it.
24. Implementation & consequently maintenance was notincluded as part of our pro
ject. Testing Process
25. APPENDIX5.1. References Books: System Analysis & Design Elias M.Awad (Galgot
ia Publication) Microsoft Access (e-book) System Analusis & Design James A. Senn
Mastering VB (e-book) Websites: http://www.intranic.in http://www.google.com
Recommended
Classroom Management Fundamentals
Classroom Management Fundamentals
Flipping the Classroom
Flipping the Classroom
iBooks Author for Teachers: Fundamentals
iBooks Author for Teachers: Fundamentals
Bank Management System
Bank Management System
Vinoth Rethnam
documentation on bank management system
documentation on bank management system
Unsa Jawaid
Banking system ppt
Banking system ppt
Lohith Lohi
54024405 project-report-banking-management-system
54024405 project-report-banking-management-system
nancs
Banking ppt
Banking ppt
Rahul Mailcontractor
java Project report online banking system
java Project report online banking system
VishNu KuNtal
BANKING SYSTEM
BANKING SYSTEM
Ashok Basnet
English Espanol Portugues Franais Deutsche
About Dev & API Blog Terms Privacy Copyright Support
LinkedIn Corporation 2015