Aditi Banking of Management Report
Aditi Banking of Management Report
Aditi Banking of Management Report
PROJECT REPORT
ON
BANKING
MANAGEMENT
SYSTEM
Submitted in the partial fulfillment of the requirement of
Submitted By:
ADITI GIRDHAR
Roll No. 11091309
ACKNOWLEDGEMENT
I take this opportunity to express my profound sense gratitude and respect to all those
who helped us throughout this endeavor. I owe my regards to MR.SANJAY KUMAR for
his cooperation and valuable support and for giving me the opportunity to undertake this
project work and necessary infrastructure.
Certificate
Introduction to Project
Problem selection
Project monitoring
Introduction to java
System study
Documentation
Project Coding
Design
Conclusion of the project
Scope of the project
Bibliography
INTRODUCTION TO PROJECT
This documentation is meant to capture the requirements of the project as given by the
client and understood by the project representative. This also acts as a reference for other
phases in the lifecycle like design; coding, testing etc. It also helps as a future reference
for any enhancements/ modifications to the requirement specification/ system.
The objective of this phase is to obtain a system definition which will than be
implemented if accepted in the subsequent analysis and design phases.
7. Prepare details of requirements user data elements, volumes, response time etc.
Project monitoring system means monitor or evaluate the system regularly. It includes the
following functions:
6. Documenting.
7. Periodic evaluating.
8. Contingency planning.
SYSTEM STUDY
The term system refers to the concept by which we can able to understand the system
according to the basic concepts of system.
It is derived from the Greek word System which means an organized relationship
between functioning units or components.
It is designed to achieve more than one objective. The study of system has three basic
implications:
3. The objectives of the organization as a whole have a higher priority that the
objectives of its subsystems.
SYSTEM ANALYSIS
At the heart of system analysis is a detailed understanding of all important faces of the
business areas under investigation. The key questions are:
1. What is being done?
To answer the above questions system analyst discuss with different category
of persons to collect the facts about the business process and their opinion of why things
happen as they do and their views for changing the existing process. During analysis data
are collected on the available files, decision points and transactions handled by the
present system.
SYSTEM DESIGN
System design is a solution, a “how to” approach the creation of a new system.
This important phase is composed of several steps. It provides the understanding and
procedural details necessary for implementing the recommended in the feasibility study.
Emphasis is on translating the performance requirements into design specification.
Design goes through logical and physical stages of development.
Logical design reviews the present physical system, prepares input and output
specifications, makes edit, security and Control specification, details the implementation,
and prepares a logical design walkthrough. The physical design maps out the details of
the physical system, plans the systematic implementation, devises a test and
implementation plan, and specifies any new hardware and software.
SYSTEM TESTING
The objective of testing is to verify that the program function as it should, that it
confirms with its specification and solves the right problem in the real world.
The aim of debugging on the other hand is to remove program errors and does not
necessarily have the same result as testing. Testing may through errors which have to be
corrected; debugging in the sense of dealing with errors as they become evident but
otherwise “leaving well alone” , may leave at any stage some section of programs
untested.
Ideally, the program should be tested without possible combinations of inputs and
its output for each case checked against precalculated correct results. Testing must be
focused on the validation of small, separate parts of the program which do have
generalarity. The testing, takes overall constructions, proceeds from the top to the
downwards. Testing of a modular program starts with the main module in an environment
where all other module is simulated.
As each module is validated it can be added to the structure and its subordinate
modules can be investigated. After the test short, the program output must be compared
with the precalculated results, and if the program is at fault then the error must be found
and tested. Program testing ends when the program has been successively through all of
its logical paths.
SYSTEM IMPLEMENTATION
Operational systems are quickly taken for granted. Every system requires periodic
evaluation after implementation. A post implementation review measures the system’s
performance against predefined requirements.
Unlike system testing, which determine where the system fails so that the
necessary adjustments can be made, a post implementation review determines how well
the system continues to meet performance specification. It is after the design and
conversions are complete. It also provides information to determine whether major
redesign is necessary.
DOCUMENTATION
REQUIREMENTS:
1) HARDWARE:
Processor : Pentium IV
RAM : 128 MB
Graphics Card : Intel(R) 82845G/PE/GV Graphic Controller.
CD ROM : CD ROM 48X/52X
Floppy Drive : 1.44 MB.
Monitor : Colored screen
2) SOFTWARE:
❖ Turbo C++
CODING
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.sql.*;
class global
{
Connection con;
ResultSet rs;
Statement stmt;
public Connection getconnection()
{
return(con);
}
global()
{
try {
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection("jdbc:odbc:xyz");
stmt = con.createStatement();
}
catch(Exception e)
{
System.out.println(e.getMessage());
}
}
ResultSet execute(String s) throws Exception
{
rs = stmt.executeQuery(s);
return(rs);
}
void update(String s) throws Exception
{
stmt.executeUpdate(s);
}
}
class mytest
{
public static void main(String s[ ])
{
myframe f1 = new myframe(" USER AUTHENTICATION");
f1.setVisible(true);
int i;
int x=1;
for(i=2;i<=300;i+=4,x+=6)
{
f1.setLocation((400-((i+x)/2) ),300-(i/2));
f1.setSize(i+x,i);
}
}
}
class myframe extends JFrame implements ActionListener
{
JPasswordField t1;
JTextField t2;
JButton b1,b2;
myframe(String s)
{
super(s);
Container con=getContentPane();
con.setLayout(new FlowLayout());
t1 = new JPasswordField(10);
t2 = new JTextField(10);
b1= new JButton(" OK ");
b2= new JButton(" CANCEL");
ImageIcon c1 = new ImageIcon("login.png");
JLabel m1 = new JLabel(c1);
con.add(m1);
con.add(new JLabel("User Name "));
con.add(t2);
con.add(new JLabel("Password "));
con.add(t1);
con.add(b1);
con.add(b2);
b1.addActionListener(this);
b2.addActionListener(this);
}
public void actionPerformed(ActionEvent ae)
{
if(ae.getSource() == b1)
{
global g1 = new global();
ResultSet rs=null;
try {
String ss="select * from login where username='"+ t2.getText()+"' and password
='"+t1.getText()+"' ";
System.out.println(ss);
rs = g1.execute(ss);
rs.next();
int n= rs.getRow();
if(n>0)
{
bank b1 = new bank();
b1.setSize(400,400);
b1.setVisible(true);
this.setVisible(false);
}
else
JOptionPane.showMessageDialog(null, "I N V A L I D username or password");
}catch(Exception e)
{
t2.setText(e.getMessage());
}
}
}
}
if(msg.equals("Loan Request"))
{
loan b1 = new loan();
b1.setSize(450,150);
b1.setVisible(true);
b1.setLocation(200,200);
}
if(msg.equals("New Account"))
{
banknew b1 = new banknew();
b1.setSize(450,150);
b1.setVisible(true);
b1.setLocation(200,200);
}
if(msg.equals("Deposit"))
{
bankdep b1 = new bankdep();
b1.setSize(300,300);
b1.setVisible(true);
}
if(msg.equals("Withdraw"))
{
bankwt b1 = new bankwt();
b1.setSize(300,300);
b1.setVisible(true);
}
if(msg.equals("List"))
{
banklst b1 = new banklst();
b1.setSize(300,300);
b1.setVisible(true);
}
}
}
class banknew extends JFrame implements ActionListener
{
JTextField t1,t2,t3;
JLabel l1,l2,l3;
JButton b1,b2;
banknew()
{
super(" New Customer Account ");
t1 = new JTextField(20);
t2 = new JTextField(20);
t3 = new JTextField(20);
l1 = new JLabel(" Customer Accno");
l2 = new JLabel(" Customer Name");
l3 = new JLabel(" Customer Balance");
b1 = new JButton("Add");
b2= new JButton("Save");
getContentPane().setLayout(new FlowLayout());
getContentPane().add(l1);
getContentPane().add(t1);
getContentPane().add(l2);
getContentPane().add(t2);
getContentPane().add(l3);
getContentPane().add(t3);
getContentPane().add(b1);
getContentPane().add(b2);
b1.addActionListener(this);
b2.addActionListener(this);
}
public void actionPerformed(ActionEvent ae)
{
if(ae.getSource() == b1)
{
t1.setText("");
t2.setText("");
t3.setText("");
}
else
{
try
{
global g1 = new global();
String qry = "insert into bank values("+t1.getText()+",' "+ t2.getText()+" ' , "+
t3.getText() +" ) ";
g1.update(qry);
JOptionPane.showMessageDialog(null," Record is saved");
}catch(Exception e) { t1.setText(""+e);}
}
}
}
getContentPane().add(jsp,BorderLayout.CENTER);
}
catch(Exception e) {System.out.println(e); }
}
}
USER AUTHENTICATION
BANK SYSTEM
ACCOUNT SYSTEM
CONCLUSION OF THE PROJECT
system is as follow:
Provide Maintenance Of Records.
Easy to maintain.
DISADVANTAGES OF THE
PROPOSED SYSTEM
evaluate the system after a certain period to find out how well the system
is meeting the objectives originally set forth. This would lead to wastage
Increase accuracy.