7 Banking Management System
7 Banking Management System
SESSION: 2024-25
: PROJECT TITLE :
Submitted By:
Submitted to:
NAME ____________ Mr. SANJAY KR. SEN
CLASS : ______ (PGT COMP. SC.)
1
CERTIFICATE
SIGNATURE OF EXAMINER
2
D E C L A R AT I O N
3
ACKNOWLEDGEMEN
T
I would like to express a deep sense of thanks &
gratitude to my Project guide Mr. Sanjay Kr. Sen for
guiding me immensely through the course of the
project. He always evinced keen interest in my work. His
constructive advice & constant motivation have been
responsible for the successful completion of this project.
4
CONTENTS
Index
Certificate
Declaration
Acknowledgement
Database
Coding
Output
Bibliography
5
INTRODUCTION
transactions one can view the details as and when required in no time. This project
holders in the bank, by making digital system one can generate daily reports,
monthly reports and annual reports which can enhance the system.
The objective of this project is to let the students apply the programming
knowledge into a real- world situation/problem and exposed the students how
programming skills helps in developing a good software.
6
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really
wants to stand against today’s merciless competition where not to wise saying “to
err is human” no longer valid, it’s outdated to rationalize your mistake. So, to keep
pace with time, to bring about the best result without malfunctioning and greater
One has to use the data management software. Software has been an ascent
markets, which have helped in making the organizations work easier and efficiently.
Data management initially hadto maintain a lot of ledgers and a lot of paperwork has
to be done but now software producton this organization has made their work
fasterand easier. Now only this software has to beloaded on the computer and work
can be done.
This prevents a lot of time and money. Thework becomes fully automated and
any information regarding the organization can beobtained by clicking the button.
7
Source code
TABLE.PY
MENU.PY
conn.autocommit = True
8
cur.execute(V_SQLInsert)
print('Account Created Succesfully!!!!!')
conn.commit()
if n == 2:
acct_no=int(input('Enter Your Account Number='))
cur.execute('select * from customer_details where
acct_no='+str (acct_no) )
data=cur.fetchall()
count=cur.rowcount
conn.commit()
if count == 0:
print('Account Number Invalid Sorry Try Again
Later’)
else:
print('1.WITHDRAW AMOUNT')
print('2.ADD AMOUNT')
x=int(input('Enter your CHOICE='))
if x == 1:
amt=int(input('Enter withdrawl amount='))
cur.execute('update customer_details set
cr_amt=cr_amt-'+str(amt) + ' where acct_no='
+str(acct_no) )
conn.commit()
print('Account Updated Succesfully!!!!!')
if x== 2:
amt=int(input('Enter amount to be added='))
cur.execute('update customer_details set
cr_amt=cr_amt+'+str(amt) + ' where acct_no='
+str(acct_no) )
conn.commit()
print('Account Updated Succesfully!!!!!')
if n == 3:
acct_no=int(input('Enter your account number=')
cur.execute('select * from customer_details where
acct_no='+str(acct_no) )
ifcur.fetchone() is None:
print('Invalid Account number')
else:
cur.execute('select * from customer_details where
acct_no='+str(acct_no) )
data=cur.fetchall()
for row in data:
9
print('ACCOUNT NO=',acct_no)
print('ACCOUNT NAME=',row[1])
print(' PHONE NUMBER=',row[2])
print('ADDRESS=',row[3])
print('cr_amt=',row[4])
if n== 4:
acct_no=int(input('Enter your account number='))
print()
cur.execute('select * from customer_details
where acct_no='+str(acct_no) )
ifcur.fetchone() is None:
print()
print('Invalid Account number')
else:
cur.execute('select * from transactions where
acct_no='+str(acct_no) )
data=cur.fetchall()
for row in data:
print('ACCOUNT NO=',acct_no)
print()
print('DATE=',row[1])
print()
print(' WITHDRAWAL AMOUNT=',row[2])
print()
print('AMOUNT ADDED=',row[3])
print()
if n == 5:
print('DELETE YOUR ACCOUNT')
acct_no=int(input('Enter your account number='))
if n == 6:
quit()
MAIN.PY
OUTPUT
MAIN PAGE
11
MENU PAGE
12
-
13
CUSTOMER DETAILS
14
TRANSCATION
15
TRANSACTION DETAILS
16
17
TESTING
TESTING METHODS
Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of view that
a test engineer takes when designing test cases.
SPECIFICATION-BASED TESTING
18
the output value (or behaviour), either "is" or "is not" the same as the expected value
specified in the test case. Specification-based testing is necessary, but it is
insufficient to guard against certain risks
The black box tester has no "bonds" with the code, and a tester's perception
is very simple: a code must have bugs. Using the principle, "Ask and you shall
receive," black box testers find bugs where programmers don't. But, on the other
hand, black box testing has been said to be "like a walk in a dark labyrinth without a
flashlight," because the tester doesn't know how the software being tested was
actually constructed.
That's why there are situations when (1) a black box tester writes many test
cases to check something that can be tested by only one test case, and/or (2) some
parts of the back end are not tested at all. Therefore, black box testing has the
advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of
"blind exploring," on the other.
White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that implement
these)
19
CODE COMPLETENESS EVALUATION
White box testing methods can also be used to evaluate the completeness of
a test suite that was created with black box testing methods. This allows the software
team to examine parts of a system that are rarely tested and ensures that the most
important function points have been tested.
20
HARDWARE AND SOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
21
INSTALLATION PROCEDURE
22
BIBLIOGRAPHY
***
23